Atoll

RF Planning & Optimisation Software

User Manual

v e r s i o n 2.8.2

AT282_UM_E0

Contact Information
Forsk (Head Office) 7 rue des Briquetiers 31700 Blagnac France www.forsk.com sales@forsk.com helpdesk@forsk.com +33 (0) 562 74 72 10 +33 (0) 562 74 72 25 +33 (0) 562 74 72 11 sales_us@forsk.com support_us@forsk.com +1 312 674 4846 +1 888 GoAtoll (+1 888 462 8655) +1 312 674 4847 www.forsk.com.cn enquiries@forsk.com.cn +86 20 8553 8938 +86 20 8553 8285 +86 10 6513 4559 Web Sales and pricing information Technical support General Technical support Fax Sales and pricing information Technical support General Technical support Fax Web Information and enquiries Telephone Fax (Guangzhou) Fax (Beijing)

Forsk (USA Office) 200 South Wacker Drive Suite 3100 Chicago, IL 60606 USA

Forsk (China Office) Suite 302, 3/F, West Tower, Jiadu Commercial Building, No.66 Jianzhong Road, Tianhe Hi-Tech Industrial Zone, Guangzhou, 510665, Peoples Republic of China

Atoll 2.8.2 User Manual Release AT282_UM_E0 Copyright 1997 - 2010 by Forsk The software described in this document is provided under a license agreement and may only be used or copied under the terms and conditions of the license agreement. No part of this document may be copied or reproduced in any form without prior authorisation from Forsk. The product or brand names mentioned in this document are trademarks or registered trademarks of their respective registering parties.

About the Atoll User Documentation

The Atoll user documentation is a guide and reference for users working with Atoll. Atoll is easy to use and offers a clear, self-explanatory user interface. The user documentation helps the user make effective and efficient use of all the features that Atoll offers. The user documentation aims to familiarise the user with the working environment of Atoll and enable him to use all of Atolls features and functions. The Atoll user documentation is technology-specific. For each Atoll radio technology, the Atoll user manual contains instructions and information specific to that technology as well as chapters describing the Atoll working environment and the tools available.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

Atoll User Manual

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Table of Contents

Table of Contents

1
1.1
1.1.1 1.1.2

The Working Environment .................................................................................................... 25

The Atoll Work Area .................................................................................................................... 25
Working with Document Windows .................................................................................................... 26 Docking or Floating an Atoll Window................................................................................................ 26 The Explorer Window ................................................................................................................. 27 Working with the Explorer Window Tabs.......................................................................................... 27 Navigating in the Explorer Window .................................................................................................. 28 Displaying or Hiding Objects on the Map Using the Explorer........................................................... 28 Working with Layers Using the Explorer .......................................................................................... 28 Working with Objects .................................................................................................................. 29 Using the Object Context Menu ....................................................................................................... 29 Renaming an Object ................................................................................................................... 29 Deleting an Object ...................................................................................................................... 29 Displaying the Properties of an Object ....................................................................................... 30 Modifying Sites and Transmitters Directly on the Map ..................................................................... 30 Selecting One of Several Transmitters ....................................................................................... 31 Moving a Site Using the Mouse .................................................................................................. 31 Moving a Site to a Higher Location............................................................................................. 31 Changing the Azimuth of the Antenna Using the Mouse ............................................................ 31 Changing the Antenna Position Relative to the Site Using the Mouse ....................................... 32 Display Properties of Objects ........................................................................................................... 32 Defining the Display Properties of Objects ................................................................................. 33 Examples of Using the Display Properties of Objects ................................................................ 37 Working with Maps....................................................................................................................... 38 Changing the Map Scale .................................................................................................................. 38 Zooming In and Out .................................................................................................................... 38 Zooming In on a Specific Area.................................................................................................... 39 Choosing a Scale........................................................................................................................ 39 Changing Between Previous Zoom Levels................................................................................. 39 Moving the Map in the Document Window....................................................................................... 39 Using the Panoramic Window .......................................................................................................... 39 Centring the Map Window on an Object........................................................................................... 40 Measuring Distances on the Map ..................................................................................................... 40 Displaying Rulers Around the Map ................................................................................................... 40 Displaying the Map Legend .............................................................................................................. 41 Using Zones in the Map Window...................................................................................................... 41 Using a Filtering Zone................................................................................................................. 41 Using a Computation Zone ......................................................................................................... 42 Using a Focus Zone or Hot Spot Zones ..................................................................................... 43 Using Polygon Zone Editing Tools.............................................................................................. 44 Using a Printing Zone ................................................................................................................. 45 Using a Geographic Export Zone ............................................................................................... 46 Editing Polygons, Lines, and Points ................................................................................................. 46 Adding a Vector Layer ................................................................................................................ 47 Creating Polygons, Lines, and Points......................................................................................... 47 Editing the Shape of Polygons and Lines ................................................................................... 47 Combining or Cropping Polygons Using the Toolbar.................................................................. 48 Editing a Point............................................................................................................................. 49 Editing Contours, Lines, and Points Using the Context Menu .................................................... 49 Exporting Coverage Prediction Results............................................................................................ 49 Exporting an Individual Coverage Prediction in Vector Format .................................................. 50 Exporting an Individual Coverage Prediction in Raster Format .................................................. 50 Exporting Multiple Coverage Predictions.................................................................................... 51 Saving a Map as a Graphic Image ................................................................................................... 51 Copying a Map to Another Application ............................................................................................. 52 Map Window Pointers ...................................................................................................................... 52 Working with Data Tables ........................................................................................................ 53 Opening a Data Table ...................................................................................................................... 54

1.2
1.2.1 1.2.2 1.2.3 1.2.4

1.3
1.3.1 1.3.1.1 1.3.1.2 1.3.1.3 1.3.2 1.3.2.1 1.3.2.2 1.3.2.3 1.3.2.4 1.3.2.5 1.3.3 1.3.3.1 1.3.3.2

1.4
1.4.1 1.4.1.1 1.4.1.2 1.4.1.3 1.4.1.4 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6 1.4.7 1.4.8 1.4.8.1 1.4.8.2 1.4.8.3 1.4.8.4 1.4.8.5 1.4.8.6 1.4.9 1.4.9.1 1.4.9.2 1.4.9.3 1.4.9.4 1.4.9.5 1.4.9.6 1.4.10 1.4.10.1 1.4.10.2 1.4.10.3 1.4.11 1.4.12 1.4.13

1.5
1.5.1

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

Atoll User Manual

1.5.2 1.5.2.1 1.5.2.2 1.5.2.3 1.5.3 1.5.4 1.5.5 1.5.6 1.5.6.1 1.5.6.2 1.5.7 1.5.8 1.5.9 1.5.10 1.5.11

1.6
1.6.1 1.6.2 1.6.2.1 1.6.2.2 1.6.2.3 1.6.3 1.6.4 1.6.5

1.7
1.7.1 1.7.1.1 1.7.1.2 1.7.1.3 1.7.1.4 1.7.2 1.7.2.1 1.7.2.2 1.7.3 1.7.3.1 1.7.3.2 1.7.3.3 1.7.3.4 1.7.4 1.7.4.1 1.7.4.2 1.7.5 1.7.5.1 1.7.5.2 1.7.5.3 1.7.5.4 1.7.5.5 1.7.5.6 1.7.6 1.7.6.1 1.7.6.2 1.7.6.3 1.7.6.4 1.7.6.5 1.7.6.6 1.7.7 1.7.8

1.8
1.8.1 1.8.2 1.8.3 1.8.3.1 1.8.3.2 1.8.3.3 1.8.4 1.8.5 1.8.6

Adding, Deleting, and Editing Data Table Fields...............................................................................54 Accessing an Object Types Table Fields ...................................................................................54 Adding a Field to an Object Types Data Table ...........................................................................54 Deleting a Field from an Object Types Data Table.....................................................................55 Editing the Contents of a Table.........................................................................................................55 Opening an Objects Record Properties Dialogue from a Table .......................................................56 Defining the Table Format.................................................................................................................56 Copying and Pasting in Tables .........................................................................................................59 Copying and Pasting a Table Element ........................................................................................59 Pasting the Same Data into Several Cells ..................................................................................59 Viewing a Statistical Analysis of Table Contents ..............................................................................61 Exporting Tables to Text Files...........................................................................................................61 Importing Tables from Text Files.......................................................................................................63 Exporting Tables to XML Files ..........................................................................................................64 Importing Tables from XML Files ......................................................................................................64 Printing in Atoll ................................................................................................................................64 Printing Data Tables and Reports .....................................................................................................64 Printing a Map ...................................................................................................................................65 Printing Recommendations .........................................................................................................65 Defining the Printing Zone ...........................................................................................................65 Defining the Print Layout .............................................................................................................66 Previewing Your Printing...................................................................................................................68 Printing a Docking Window ...............................................................................................................68 Printing Antenna Patterns .................................................................................................................68 Grouping, Sorting, and Filtering Data..................................................................................69 Grouping Data Objects......................................................................................................................69 Grouping Data Objects by a Selected Property ..........................................................................69 Configuring the Group By Submenu ...........................................................................................69 Advanced Grouping.....................................................................................................................70 Examples of Grouping .................................................................................................................71 Sorting Data ......................................................................................................................................73 Sorting Data in Tables.................................................................................................................73 Advanced Sorting ........................................................................................................................73 Filtering Data.....................................................................................................................................74 Filtering in Data Tables by Selection...........................................................................................74 Advanced Data Filtering ..............................................................................................................75 Restoring All Records..................................................................................................................76 Advanced Filtering: Examples .....................................................................................................76 User Configurations ..........................................................................................................................78 Exporting a User Configuration ...................................................................................................79 Importing a User Configuration ...................................................................................................79 Site and Transmitter Lists .................................................................................................................79 Creating a Site or Transmitter List...............................................................................................80 Adding a Site or Transmitter to a List from the Explorer Window................................................80 Adding a Site or Transmitter to a List from the Map Window ......................................................80 Adding Sites or Transmitters to a List Using a Zone ...................................................................81 Editing a Site or Transmitter List .................................................................................................81 Filtering on a Site or Transmitter List ..........................................................................................81 Folder Configurations........................................................................................................................82 Creating a Folder Configuration ..................................................................................................82 Applying a Saved Folder Configuration .......................................................................................82 Reapplying the Current Folder Configuration ..............................................................................82 Exporting a Folder Configuration.................................................................................................83 Importing a Folder Configuration.................................................................................................83 Deleting a Folder Configuration...................................................................................................83 Creating and Comparing Subfolders.................................................................................................83 Filtering Data Using a Filtering Zone.................................................................................................84 Tips and Tricks ...............................................................................................................................84 Undoing and Redoing .......................................................................................................................84 Refreshing Maps and Folders ...........................................................................................................85 Searching for Objects on the Map.....................................................................................................85 Searching for a Map Object by Its Name ....................................................................................85 Searching for a Map Object using Any Text Property .................................................................85 Searching for a Point on the Map ................................................................................................86 Using the Status Bar to Get Information ...........................................................................................86 Saving Information Displayed in the Event Viewer ...........................................................................86 Using Icons from the Toolbar ............................................................................................................86

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Table of Contents

1.8.7

Using Shortcuts in Atoll .................................................................................................................... 88

2
2.1 2.2
2.2.1 2.2.1.1 2.2.1.2 2.2.1.3 2.2.2 2.2.2.1 2.2.2.2 2.2.2.3 2.2.2.4 2.2.2.5

Starting an Atoll Project .......................................................................................................... 93

Before Starting a Radio-Planning Project ......................................................................... 93 Creating an Atoll Document .................................................................................................... 93
Creating a New Atoll Document from a Template ............................................................................ 93 Templates Available ................................................................................................................... 93 Creating a New Atoll Document from a Template ...................................................................... 94 Defining a New Atoll Document .................................................................................................. 95 Working in a Multi-User Environment ............................................................................................... 97 The Atoll Multi-User Environment ............................................................................................... 98 Creating a New Atoll Document from a Database ...................................................................... 99 Working With a Document on a Database................................................................................ 100 Refreshing an Atoll Document from the Database ................................................................... 101 Archiving the Modifications of an Atoll Document in the Database .......................................... 102 Making a Backup of Your Document ................................................................................ 105 Configuring Automatic Backup ....................................................................................................... 105 Recovering a Backup ..................................................................................................................... 106 Making and Sharing Portable Atoll Projects .................................................................. 106

2.3
2.3.1 2.3.2

2.4

3
3.1 3.2 3.3
3.3.1 3.3.2 3.3.3 3.3.3.1 3.3.3.2 3.3.4 3.3.5 3.3.6 3.3.7

Managing Geographic Data .............................................................................................. 111

Geographic Data Types .......................................................................................................... 111 Supported Geographic Data Formats .............................................................................. 112 Importing Geo Data Files ........................................................................................................ 113
Importing a Raster-format Geo Data File ....................................................................................... 113 Importing a Vector-format Geo Data File ....................................................................................... 114 Importing MSI Planet Geo Data................................................................................................... 115 Importing One MSI Planet Geo Data Type ............................................................................ 116 Importing a MSI Planet Geo Database .................................................................................. 116 Importing a WMS Raster-format Geo Data File ............................................................................. 117 Grouping Geo Data Files in Folders............................................................................................... 118 Embedding Geographic Data ......................................................................................................... 119 Repairing a Broken Link to a Geo Data File................................................................................... 119 Digital Terrain Models .............................................................................................................. 120

3.4 3.5
3.5.1 3.5.2 3.5.3 3.5.4 3.5.5

Clutter Classes............................................................................................................................. 120

Assigning Names to Clutter Classes .............................................................................................. 120 Defining Clutter Class Properties ................................................................................................... 121 Adding a Clutter Class.................................................................................................................... 122 Refreshing the List of Clutter Classes ............................................................................................ 123 Displaying Total Surface Area per Clutter Class ............................................................................ 123 Clutter Heights ............................................................................................................................. 123

3.6 3.7
3.7.1 3.7.2 3.7.3

Contours, Lines, and Points .................................................................................................. 123

Managing the Display of a Vector Layer ........................................................................................ 124 Managing the Properties of the Vector Layer................................................................................. 124 Moving a Vector Layer to the Data Tab.......................................................................................... 125 Scanned Images ......................................................................................................................... 125 Importing Several Scanned Images ............................................................................................... 125 Defining the Display Properties of Scanned Images ...................................................................... 125 Population Maps ......................................................................................................................... 126 Managing the Display of Population Data ...................................................................................... 126 Displaying Population Statistics ..................................................................................................... 126 Custom Geo Data Maps.......................................................................................................... 127 Creating a Custom Geo Data Map ................................................................................................. 127 Adding a File to a Custom Geo Data Map...................................................................................... 128 Managing the Properties of a Custom Geo Data Map ................................................................... 128 Displaying Statistics on Custom Geo Data..................................................................................... 129 Integrable Versus Non Integrable Data .......................................................................................... 129 Setting the Priority of Geo Data........................................................................................... 129 Setting the Display Priority of Geo Data ......................................................................................... 129 Setting the Priority of Geo Data in Calculations ............................................................................. 130 Example 1: Two DTM Maps Representing Different Areas ...................................................... 131 Example 2: Clutter Classes and DTM Maps Representing the Same Area ............................. 131 Example 3: Two Clutter Class Maps Representing a Common Area ....................................... 132

3.8
3.8.1 3.8.2

3.9
3.9.1 3.9.2

3.10
3.10.1 3.10.2 3.10.3 3.10.4 3.10.5

3.11
3.11.1 3.11.2 3.11.2.1 3.11.2.2 3.11.2.3

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

Atoll User Manual

3.12 3.13
3.13.1 3.13.2

Displaying Information About Geo Data...........................................................................132 Geographic Data Sets...............................................................................................................132

Exporting a Geo Data Set ...............................................................................................................133 Importing a Geo Data Set ...............................................................................................................133 Editing Geographic Data .........................................................................................................133 Editing Clutter Class Maps..............................................................................................................134 Creating a Clutter Polygon ........................................................................................................134 Editing Clutter Polygons ............................................................................................................134 Displaying the Coordinates of Clutter Polygons ........................................................................135 Deleting Clutter Polygons..........................................................................................................135 Editing Population or Custom Data Maps .......................................................................................135 Saving Geographic Data .........................................................................................................136 Saving Modifications to an External File .........................................................................................136 Exporting an Edited Clutter Class Map in a Raster-Format File................................................136 Exporting an Edited Vector Layer in Vector-Format File ...........................................................137 Updating the Source File.................................................................................................................138 Combining Several Files into One File............................................................................................138 Exporting an Embedded File...........................................................................................................138 Creating a New File from a Larger File ...........................................................................................139

3.14
3.14.1 3.14.1.1 3.14.1.2 3.14.1.3 3.14.1.4 3.14.2

3.15
3.15.1 3.15.1.1 3.15.1.2 3.15.2 3.15.3 3.15.4 3.15.5

4
4.1
4.1.1 4.1.2 4.1.3 4.1.4 4.1.5

Antennas and Equipment.....................................................................................................143

Working With Antennas............................................................................................................143
Creating an Antenna .......................................................................................................................143 Importing Planet-Format Antennas .................................................................................................144 Importing 3-D Antenna Patterns......................................................................................................145 Smoothing an Antenna Pattern .......................................................................................................146 Printing an Antenna Pattern ............................................................................................................147 Working With Equipment .........................................................................................................147 Defining TMA Equipment ................................................................................................................147 Defining Feeder Cables ..................................................................................................................147 Defining BTS Equipment.................................................................................................................148 Updating the Values for Total Losses and the BTS Noise Figure for Transmitters.........................148

4.2
4.2.1 4.2.2 4.2.3 4.2.4

5
5.1
5.1.1 5.1.2 5.1.2.1 5.1.2.2 5.1.2.3 5.1.2.4 5.1.2.5 5.1.2.6 5.1.3 5.1.3.1 5.1.3.2 5.1.3.3 5.1.4 5.1.4.1 5.1.4.2 5.1.4.3 5.1.5 5.1.5.1 5.1.5.2 5.1.5.3 5.1.6 5.1.7 5.1.7.1 5.1.7.2 5.1.7.3 5.1.8 5.1.9 5.1.10 5.1.11 5.1.12

Managing Calculations in Atoll ........................................................................................153

Working with Propagation Models ......................................................................................153
Propagation Model Characteristics: Overview ................................................................................153 The Standard Propagation Model ...................................................................................................154 Recommendations for Working with the Standard Propagation Model .....................................154 Calculating Diffraction With the SPM ........................................................................................155 Sample Values for SPM Formulas ............................................................................................156 Calculating f(clutter) with the Standard Propagation Model ......................................................156 Modelling Fixed Receivers ........................................................................................................157 Defining the Parameters of the Standard Propagation Model ...................................................157 The Okumura-Hata Propagation Model ..........................................................................................160 Defining General Settings (Okumura-Hata) ..............................................................................160 Selecting an Environment Formula (Okumura-Hata) ................................................................160 Creating or Modifying Environment Formulas (Okumura-Hata) ................................................161 The Cost-Hata Propagation Model..................................................................................................161 Defining General Settings (Cost-Hata) ......................................................................................161 Selecting an Environment Formula (Cost-Hata)........................................................................162 Creating or Modifying Environment Formulas (Cost-Hata) .......................................................162 The ITU 529-3 Propagation Model..................................................................................................162 Defining General Settings (ITU 529-3) ......................................................................................163 Selecting an Environment Formula (ITU 529-3) ........................................................................163 Creating or Modifying Environment Formulas (ITU 529-3)........................................................163 The ITU 370-7 Propagation Model..................................................................................................164 The Erceg-Greenstein Propagation Model......................................................................................164 Defining General Settings (Erceg-Greenstein (SUI)) ................................................................164 Selecting an Environment Formula (Erceg-Greenstein (SUI)) ..................................................165 Creating or Modifying Environment Formulas (Erceg-Greenstein (SUI)) ..................................165 The ITU 526-5 Propagation Model..................................................................................................165 The WLL Propagation Model ..........................................................................................................165 The Longley-Rice Propagation Model.............................................................................................166 The ITU 1546 Propagation Model ...................................................................................................166 The Sakagami Extended Propagation Model..................................................................................167

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Table of Contents

5.1.13

Managing Propagation Models....................................................................................................... 167

5.2
5.2.1 5.2.2 5.2.3 5.2.4 5.2.5

Defining Calculation Parameters ........................................................................................ 168

Defining Calculation Parameters for One Transmitter.................................................................... 168 Defining the Same Calculation Parameters for a Group of Transmitters ....................................... 169 Defining the Same Calculation Parameters for All Transmitters .................................................... 169 Defining a Default Propagation Model............................................................................................ 170 Defining a Default Resolution ......................................................................................................... 170 Managing Path Loss Matrices .............................................................................................. 170 Calculating Path Loss Matrices ...................................................................................................... 171 Stopping Path Loss Matrix Calculation........................................................................................... 171 Setting the Storage Location of Path Loss Matrices ...................................................................... 171 Using Centralised Path Loss Matrices ........................................................................................... 172 Checking the Validity of Path Loss Matrices .................................................................................. 172 Tuning Path Loss Matrices Using Measurement Data ................................................................... 173 Defining the Area to be Tuned.................................................................................................. 173 Defining Maximum Corrections and Thresholds on Path Loss Tuning..................................... 174 Tuning Path Loss Matrices Using CW Measurements ............................................................. 175 Tuning Path Loss Matrices Using Drive Test Data ................................................................... 176 Managing the Path Loss Tuning Points .................................................................................... 177 Exporting Path Loss Matrices......................................................................................................... 179 Predictions Available in Atoll ................................................................................................. 179 Making Point Predictions ................................................................................................................ 179 Starting a Point Analysis........................................................................................................... 180 The Tabs of the Point Analysis Tool Window ........................................................................... 180 Moving the Receiver on the Map .............................................................................................. 181 Taking Indoor Losses into Account........................................................................................... 181 Taking Shadowing into Account in Point Analyses................................................................... 181 Making Coverage Predictions ........................................................................................................ 182 Creating Coverage Predictions................................................................................................. 183 Defining the Storage Location of Coverage Prediction Results................................................ 184 Calculating Coverage Predictions............................................................................................. 184 Saving Defined Coverage Predictions ...................................................................................... 186 Calculating Indoor Coverage .................................................................................................... 187 Taking Shadowing into Account ............................................................................................... 187

5.3
5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.6.1 5.3.6.2 5.3.6.3 5.3.6.4 5.3.6.5 5.3.7

5.4
5.4.1 5.4.1.1 5.4.1.2 5.4.1.3 5.4.1.4 5.4.1.5 5.4.2 5.4.2.1 5.4.2.2 5.4.2.3 5.4.2.4 5.4.2.5 5.4.2.6

6
6.1 6.2
6.2.1 6.2.1.1 6.2.1.2 6.2.1.3 6.2.1.4 6.2.1.5 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 6.2.6.1 6.2.6.2 6.2.6.3 6.2.6.4 6.2.6.5 6.2.7 6.2.7.1 6.2.7.2 6.2.7.3 6.2.7.4 6.2.8 6.2.9 6.2.9.1 6.2.9.2 6.2.10 6.2.10.1 6.2.10.2

GSM/GPRS/EDGE Networks .......................................................................................... 191

Designing a GSM/GPRS/EDGE Network ....................................................................... 191 Planning and Optimising GSM/GPRS/EDGE Base Stations ................................ 192
Creating a GSM/GPRS/EDGE Base Station .................................................................................. 192 Definition of a Base Station ...................................................................................................... 193 Creating or Modifying a Base Station Element ......................................................................... 201 Placing a New Station Using a Station Template ..................................................................... 203 Managing Station Templates .................................................................................................... 204 Duplicating an Existing Base Station ........................................................................................ 207 Creating a Group of Base Stations................................................................................................. 208 Modifying Sites and Transmitters Directly on the Map ................................................................... 209 Display Tips for Base Stations ....................................................................................................... 209 Modelling Packet-switched Transmitters ........................................................................................ 209 Creating a Repeater ....................................................................................................................... 210 Creating and Modifying Repeater Equipment........................................................................... 210 Placing a Repeater on the Map Using the Mouse .................................................................... 210 Creating Several Repeaters ..................................................................................................... 211 Defining the Properties of a Repeater ...................................................................................... 211 Tips for Updating Repeater Parameters ................................................................................... 212 Creating a Remote Antenna ........................................................................................................... 212 Placing a Remote Antenna on the Map Using the Mouse ........................................................ 213 Creating Several Remote Antennas ......................................................................................... 213 Defining the Properties of a Remote Antenna .......................................................................... 213 Tips for Updating Remote Antenna Parameters....................................................................... 214 Setting the Working Area of an Atoll Document ............................................................................. 214 Studying a Single Base Station ...................................................................................................... 215 Making a Point Analysis to Study the Profile ............................................................................ 215 Studying Signal Level Coverage............................................................................................... 216 Studying Base Stations .................................................................................................................. 218 Path Loss Matrices ................................................................................................................... 219 Assigning a Propagation Model ................................................................................................ 221

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

Atoll User Manual

6.2.10.3 6.2.10.4 6.2.10.5 6.2.10.6 6.2.10.7 6.2.10.8 6.2.11 6.2.11.1 6.2.11.2 6.2.11.3 6.2.11.4 6.2.11.5 6.2.11.6 6.2.11.7 6.2.11.8 6.2.11.9

6.3
6.3.1 6.3.2 6.3.3 6.3.4 6.3.4.1 6.3.4.2 6.3.4.3 6.3.4.4 6.3.4.5 6.3.5 6.3.6 6.3.6.1 6.3.6.2 6.3.6.3 6.3.6.4 6.3.6.5 6.3.7 6.3.7.1 6.3.7.2

6.4
6.4.1 6.4.2 6.4.2.1 6.4.2.2 6.4.2.3 6.4.3 6.4.3.1 6.4.3.2 6.4.3.3 6.4.3.4 6.4.4 6.4.4.1 6.4.4.2 6.4.4.3 6.4.4.4 6.4.5 6.4.5.1 6.4.5.2 6.4.5.3 6.4.5.4 6.4.5.5 6.4.5.6 6.4.5.7 6.4.5.8

6.5
6.5.1 6.5.2 6.5.2.1 6.5.2.2 6.5.2.3

The Calculation Process ...........................................................................................................223 Creating a Computation Zone ...................................................................................................223 Setting Transmitters as Active...................................................................................................224 Signal Level Coverage Predictions ...........................................................................................225 Analysing a Coverage Prediction ..............................................................................................233 Printing and Exporting Coverage Prediction Results ................................................................241 Planning Neighbours.......................................................................................................................241 Importing Neighbours ................................................................................................................242 Defining Exceptional Pairs ........................................................................................................242 Configuring Importance Factors for Neighbours .......................................................................242 Allocating Neighbours Automatically .........................................................................................243 Checking Automatic Allocation Results .....................................................................................245 Allocating and Deleting Neighbours per Transmitter .................................................................248 Calculating the Importance of Existing Neighbours...................................................................250 Checking the Consistency of the Neighbour Plan .....................................................................251 Exporting Neighbours................................................................................................................252 Studying Network Capacity ....................................................................................................253 Importing OMC traffic data into the subcell traffic view ...................................................................253 Using Subcell Data in Network Capacity Analysis ..........................................................................253 Defining Multi-service Traffic Data ..................................................................................................254 Creating a Traffic Map.....................................................................................................................254 Creating a Sector Traffic Map ...................................................................................................254 Creating a User Profile Traffic Map ...........................................................................................256 Creating User Density Traffic Maps (No. Users/km2) ...............................................................260 Converting 2G Network Traffic ..................................................................................................261 Exporting Cumulated Traffic ......................................................................................................261 Exporting a Traffic Map ...................................................................................................................262 Calculating and Displaying a Traffic Capture ..................................................................................262 Prerequisites for a Traffic Capture ............................................................................................263 Creating a Traffic Capture .........................................................................................................263 GSM/GPRS/EDGE Traffic Capture Results ..............................................................................264 Estimating a Traffic Increase .....................................................................................................265 Modifying a GSM/GPRS/EDGE Traffic Capture........................................................................265 Dimensioning a GSM/GPRS/EDGE Network..................................................................................266 Defining a GSM/GPRS/EDGE Dimensioning Model .................................................................266 Dimensioning a GSM/GPRS/EDGE Network ............................................................................267 Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs ....................................270 Definition of the Resource Allocation Process ................................................................................270 Defining Resource Ranges .............................................................................................................271 Defining Frequency Bands, Domains, and Groups ...................................................................271 Defining BSIC Domains and Groups.........................................................................................272 Defining HSN Domains and Groups..........................................................................................273 Allocating Frequencies and BSICs Manually ..................................................................................274 Assigning BSIC Domains to Transmitters .................................................................................274 Assigning BSICs to Transmitters Manually ...............................................................................275 Defining Frequency Domains for Transmitters ..........................................................................275 Assigning Frequencies to Subcells ...........................................................................................276 AFP Prerequisites (IM, Separations, Traffic, etc.)...........................................................................279 Interference Matrices.................................................................................................................280 Defining Required Channel Separations ...................................................................................290 Traffic ........................................................................................................................................295 Network and Transmitter Settings .............................................................................................298 Automatic Resource Allocation Using an AFP Module ...................................................................299 The Scope of the AFP and the Scope of the Interference Matrix ..............................................299 The Network Validation Process ...............................................................................................301 The AFP's Target Calculation Time...........................................................................................302 Running an Automatic Frequency Allocation ............................................................................302 The AFP Progress Dialogue......................................................................................................306 The Results of the Automatic Frequency Allocation..................................................................307 Interactive Frequency Allocation ...............................................................................................314 Allocating Frequencies Interactively ..........................................................................................315 Analysing Network Quality ......................................................................................................317 Evaluating the Quality of a Frequency Plan ....................................................................................317 Interference Coverage Predictions..................................................................................................320 Making Quality Studies Based on CI or C(I+N)........................................................................320 Studying Interference Areas ......................................................................................................323 Analysing Interference Areas Using a Point Analysis ...............................................................325

10

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Table of Contents

6.5.2.4 6.5.3 6.5.3.1 6.5.3.2 6.5.3.3 6.5.4 6.5.5 6.5.6 6.5.7 6.5.8 6.5.8.1 6.5.8.2 6.5.8.3 6.5.8.4 6.5.9

6.6
6.6.1 6.6.1.1 6.6.1.2 6.6.1.3 6.6.1.4 6.6.2 6.6.2.1 6.6.2.2 6.6.2.3 6.6.3 6.6.3.1 6.6.3.2 6.6.4 6.6.5 6.6.6 6.6.6.1 6.6.6.2 6.6.6.3

6.7
6.7.1 6.7.2 6.7.3 6.7.4 6.7.4.1 6.7.4.2 6.7.4.3 6.7.4.4 6.7.4.5 6.7.5 6.7.6 6.7.7 6.7.8

6.8
6.8.1 6.8.2 6.8.3 6.8.3.1 6.8.3.2 6.8.3.3 6.8.4 6.8.4.1 6.8.5 6.8.5.1 6.8.5.2 6.8.5.3 6.8.5.4 6.8.5.5 6.8.6 6.8.6.1 6.8.6.2 6.8.6.3

Example of Analysing Interference Using a Point Analysis ...................................................... 326 Packet-Specific Coverage Predictions ........................................................................................... 328 Making a Coverage Prediction by GPRS/EDGE Coding Schemes .......................................... 328 Making a Coverage Prediction by Packet Throughput ............................................................. 330 Making a BLER Coverage Prediction ....................................................................................... 333 Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction............................... 335 Studying Interference Between Transmitters ................................................................................. 337 Auditing a GSM/GPRS/EDGE Frequency Plan.............................................................................. 338 Checking Consistency Between Transmitters and Subcells .......................................................... 340 Displaying the Frequency Allocation .............................................................................................. 341 Using the Search Tool to Display Channel Reuse.................................................................... 341 Displaying the Frequency Allocation Using Transmitter Display Settings ................................ 342 Grouping Transmitters by Frequencies .................................................................................... 343 Displaying the Channel Allocation Histogram........................................................................... 343 Calculating Key Performance Indicators of a GSM/GPRS/EDGE Network ................................... 344 Optimising Network Parameters Using the ACP......................................................... 346 The ACP Module and Atoll ............................................................................................................. 347 Using Zones with ACP.............................................................................................................. 347 Using Traffic Maps with ACP .................................................................................................... 348 Shadowing Margin and Indoor Coverage ................................................................................. 348 ACP and Antenna Masking....................................................................................................... 348 Configuring the ACP Module .......................................................................................................... 350 Configuring the Default Settings ............................................................................................... 350 Defining the Antenna Masking Method..................................................................................... 351 Saving Settings to a User Configuration File ............................................................................ 352 Optimising Cell Planning with the ACP .......................................................................................... 353 Creating an Optimisation Setup................................................................................................ 353 Defining Optimisation Parameters ............................................................................................ 354 Running an Optimisation Setup...................................................................................................... 373 Working with Optimisations in the Explorer Window ...................................................................... 374 Viewing Optimisation Results......................................................................................................... 375 Viewing Optimisation Results in the Properties Dialogue......................................................... 376 Viewing Optimisation Results in the Map Window.................................................................... 382 Viewing Optimisation Results Using the Histogram.................................................................. 388 Verifying Network Capacity ................................................................................................... 389 Importing a Drive Test Data Path ................................................................................................... 389 Displaying Drive Test Data ............................................................................................................. 391 Defining the Display of a Drive Test Data Path .............................................................................. 392 Network Verification ....................................................................................................................... 392 Filtering Incompatible Points Along Drive Test Data Paths ...................................................... 392 Creating Coverage Predictions from Drive Test Data Paths .................................................... 394 Displaying Statistics Over a Drive Test Data Path.................................................................... 395 Extracting a Field From a Drive Test Data Path for a Transmitter............................................ 396 Analysing Data Variations Along the Path ................................................................................ 396 Exporting a Drive Test Data Path................................................................................................... 398 Extracting CW Measurements from Drive Test Data ..................................................................... 398 Generating Interference Matrices from a Drive Test Data Path ..................................................... 399 Printing and Exporting the Drive Test Data Window ...................................................................... 399 Advanced Configuration .......................................................................................................... 399 Setting HCS Layers ........................................................................................................................ 400 Comparing Service Areas in Calculations ...................................................................................... 400 Cell Types ...................................................................................................................................... 404 TRX Types................................................................................................................................ 404 Creating a Cell Type ................................................................................................................. 404 Examples of Cell Types ............................................................................................................ 406 TRX Configuration.......................................................................................................................... 407 Creating or Importing TRX Configuration ................................................................................. 408 Codec Configuration....................................................................................................................... 408 Opening the Codec Mode Table............................................................................................... 408 Creating or Modifying Codec Configuration.............................................................................. 409 Setting Codec Mode Adaptation Thresholds ............................................................................ 409 Setting Codec Mode Quality Thresholds .................................................................................. 410 Using Codec Configurations in Transmitters and Terminals .................................................... 410 Coding Scheme Configuration ....................................................................................................... 411 Opening the Coding Schemes Table........................................................................................ 411 Creating or Modifying a Coding Scheme Configuration............................................................ 412 Using Coding Scheme Configuration in Transmitters and Terminals ....................................... 413

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

11

Atoll User Manual

6.8.6.4 6.8.6.5 6.8.7 6.8.7.1 6.8.8 6.8.8.1 6.8.8.2 6.8.9 6.8.9.1 6.8.9.2 6.8.9.3 6.8.10 6.8.11 6.8.12 6.8.13 6.8.13.1 6.8.14 6.8.15 6.8.15.1

6.9
6.9.1 6.9.1.1 6.9.1.2 6.9.1.3 6.9.2 6.9.2.1 6.9.2.2 6.9.2.3 6.9.2.4 6.9.2.5 6.9.3 6.9.3.1 6.9.3.2 6.9.3.3 6.9.3.4 6.9.3.5

Adapting Coding Scheme Thresholds for a Maximum BLER....................................................413 Displaying Coding Scheme Throughput Graphs .......................................................................413 Timeslot Configurations ..................................................................................................................414 Creating or Modifying a Timeslot Configuration ........................................................................414 Advanced Transmitter Configuration Options .................................................................................415 Defining Extended Cells ............................................................................................................415 Advanced Modelling of Multi-Band Transmitters .......................................................................415 GSM/GPRS/EDGE Multi-Service Traffic Data ................................................................................418 Modelling GSM/GPRS/EDGE Services.....................................................................................418 Modelling GSM/GPRS/EDGE Mobility Types ...........................................................................419 Modelling GSM/GPRS/EDGE Terminals...................................................................................419 Defining the Interferer Reception Threshold ...................................................................................421 Advanced Modelling of Hopping Gain in Studies ............................................................................421 Taking Intermodulation Interference into Consideration in Calculations .........................................422 Modelling Shadowing ......................................................................................................................422 Displaying the Shadowing Margins per Clutter Class ...............................................................423 Modelling the Co-existence of Networks.........................................................................................423 Modelling Inter-Technology Interference.........................................................................................424 Defining Inter-Technology IRFs.................................................................................................424 The Atoll AFP Module ...............................................................................................................425 Basic Atoll AFP Use ........................................................................................................................425 Using the Atoll AFP in a simple way..........................................................................................425 The Atoll AFP Cost Definition....................................................................................................426 The Atoll AFP Algorithm ............................................................................................................427 Using the Atoll AFP .........................................................................................................................427 An Overview of the AFP Cost Function .....................................................................................427 Setting the Parameters of the Atoll AFP Module .......................................................................432 Frequency Hopping Overview ...................................................................................................443 Azimuth Oriented Assignments (Pattern Allocation, 1/1 1/3 1/x ) ..........................................444 BSIC Allocation .........................................................................................................................445 Advanced AFP usage .....................................................................................................................445 Optimizing the Number of Required TRXs ................................................................................445 Interference Matrix combination according to max likelihood....................................................453 The Storage of a frequency plan in Atoll ...................................................................................457 Various tips and tricks ...............................................................................................................459 The role of the AFP administrator .............................................................................................461

7
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.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.7 7.2.7.1 7.2.7.2 7.2.7.3 7.2.7.4 7.2.8 7.2.9 7.2.9.1 7.2.9.2 7.2.10 7.2.10.1

UMTS HSPA Networks ..........................................................................................................465

Designing a UMTS Network...................................................................................................465 Planning and Optimising UMTS Base Stations ............................................................466
Creating a UMTS Base Station .......................................................................................................467 Definition of a Base Station .......................................................................................................467 Creating or Modifying a Base Station Element..........................................................................473 Placing a New Station Using a Station Template ......................................................................475 Managing Station Templates.....................................................................................................476 Duplicating an Existing Base Station.........................................................................................481 Creating a Group of Base Stations .................................................................................................481 Modifying Sites and Transmitters Directly on the Map....................................................................482 Display Tips for Base Stations ........................................................................................................482 Creating a Dual-Band UMTS Network ............................................................................................483 Creating a Repeater........................................................................................................................483 Creating and Modifying Repeater Equipment ...........................................................................483 Placing a Repeater on the Map Using the Mouse .....................................................................484 Creating Several Repeaters ......................................................................................................484 Defining the Properties of a Repeater .......................................................................................484 Tips for Updating Repeater Parameters....................................................................................485 Creating a Remote Antenna............................................................................................................486 Placing a Remote Antenna on the Map Using the Mouse.........................................................486 Creating Several Remote Antennas..........................................................................................486 Defining the Properties of a Remote Antenna ...........................................................................487 Tips for Updating Remote Antenna Parameters .......................................................................487 Setting the Working Area of an Atoll Document..............................................................................488 Studying a Single Base Station.......................................................................................................488 Making a Point Analysis to Study the Profile .............................................................................488 Studying Signal Level Coverage ...............................................................................................490 Studying Base Stations ...................................................................................................................492 Path Loss Matrices....................................................................................................................493
Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

12

Table of Contents

7.2.10.2 7.2.10.3 7.2.10.4 7.2.10.5 7.2.10.6 7.2.10.7 7.2.10.8 7.2.10.9 7.2.10.10 7.2.10.11 7.2.11 7.2.11.1 7.2.11.2 7.2.11.3 7.2.11.4 7.2.11.5 7.2.11.6 7.2.11.7 7.2.11.8 7.2.11.9 7.2.12 7.2.12.1 7.2.12.2 7.2.12.3 7.2.12.4 7.2.12.5 7.2.12.6

7.3
7.3.1 7.3.2 7.3.2.1 7.3.2.2 7.3.2.3 7.3.2.4 7.3.2.5 7.3.3 7.3.4 7.3.4.1 7.3.4.2 7.3.4.3 7.3.4.4 7.3.4.5 7.3.4.6 7.3.4.7 7.3.4.8 7.3.4.9 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.1.4 7.4.2 7.4.2.1 7.4.2.2 7.4.2.3 7.4.3 7.4.3.1 7.4.3.2 7.4.3.3 7.4.4 7.4.5 7.4.6 7.4.6.1

Assigning a Propagation Model ................................................................................................ 494 The Calculation Process........................................................................................................... 496 Creating a Computation Zone................................................................................................... 496 Setting Transmitters or Cells as Active..................................................................................... 497 Signal Level Coverage Predictions........................................................................................... 498 Analysing a Coverage Prediction.............................................................................................. 501 UMTS-Specific Studies............................................................................................................. 509 HSDPA Coverage Prediction.................................................................................................... 525 HSUPA Coverage Prediction.................................................................................................... 527 Printing and Exporting Coverage Prediction Results................................................................ 528 Planning Neighbours ...................................................................................................................... 528 Importing Neighbours ............................................................................................................... 529 Defining Exceptional Pairs........................................................................................................ 529 Configuring Importance Factors for Neighbours....................................................................... 529 Allocating Neighbours Automatically ........................................................................................ 530 Checking Automatic Allocation Results .................................................................................... 533 Allocating and Deleting Neighbours per Cell ............................................................................ 536 Calculating the Importance of Existing Neighbours .................................................................. 538 Checking the Consistency of the Neighbour Plan .................................................................... 540 Exporting Neighbours ............................................................................................................... 541 Planning Scrambling Codes ........................................................................................................... 541 Defining the Scrambling Code Format...................................................................................... 542 Creating Scrambling Code Domains and Groups..................................................................... 542 Defining Exceptional Pairs for Scrambling Code Allocation ..................................................... 542 Allocating Scrambling Codes.................................................................................................... 543 Checking the Consistency of the Scrambling Code Plan ......................................................... 545 Displaying the Allocation of Scrambling Codes ........................................................................ 546 Studying Network Capacity ................................................................................................... 549 Defining Multi-service Traffic Data ................................................................................................. 549 Creating a Traffic Map.................................................................................................................... 550 Creating a Sector Traffic Map................................................................................................... 550 Creating a User Profile Traffic Map .......................................................................................... 551 Creating User Density Traffic Maps (No. Users/km2)............................................................... 556 Converting 2G Network Traffic ................................................................................................. 558 Exporting Cumulated Traffic ..................................................................................................... 558 Exporting a Traffic Map .................................................................................................................. 558 Calculating and Displaying Traffic Simulations .............................................................................. 559 The Power Control Simulation Algorithm.................................................................................. 559 Creating Simulations................................................................................................................. 563 Displaying the Traffic Distribution on the Map .......................................................................... 565 Displaying the User Active Set on the Map .............................................................................. 566 Displaying the Results of a Single Simulation .......................................................................... 567 Displaying the Average Results of a Group of Simulations ...................................................... 572 Updating Cell Values With Simulation Results ......................................................................... 575 Adding New Simulations to an Atoll Document ........................................................................ 576 Estimating a Traffic Increase .................................................................................................... 577 Analysing the Results of a Simulation ............................................................................................ 578 Making an AS Analysis of Simulation Results .......................................................................... 578 Making Coverage Predictions Using Simulation Results.......................................................... 578 Optimising Network Parameters Using the ACP......................................................... 579 The ACP Module and Atoll ............................................................................................................. 579 Using Zones with ACP.............................................................................................................. 580 Using Traffic Maps with ACP .................................................................................................... 580 Shadowing Margin and Indoor Coverage ................................................................................. 581 ACP and Antenna Masking....................................................................................................... 581 Configuring the ACP Module .......................................................................................................... 583 Configuring the Default Settings ............................................................................................... 583 Defining the Antenna Masking Method..................................................................................... 584 Saving Settings to a User Configuration File ............................................................................ 585 Optimising Cell Planning with the ACP .......................................................................................... 586 Creating an Optimisation Setup................................................................................................ 586 Defining Optimisation Parameters ............................................................................................ 587 Defining Site Selection Parameters .......................................................................................... 600 Running an Optimisation Setup...................................................................................................... 609 Working with Optimisations in the Explorer Window ...................................................................... 610 Viewing Optimisation Results......................................................................................................... 611 Viewing Optimisation Results in the Properties Dialogue......................................................... 612

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

13

Atoll User Manual

7.4.6.2 7.4.6.3

7.5
7.5.1 7.5.2 7.5.3 7.5.4 7.5.4.1 7.5.4.2 7.5.4.3 7.5.4.4 7.5.4.5 7.5.5 7.5.6 7.5.7

7.6
7.6.1 7.6.2 7.6.2.1 7.6.2.2 7.6.3 7.6.3.1 7.6.3.2 7.6.3.3 7.6.3.4 7.6.3.5 7.6.3.6 7.6.3.7 7.6.4 7.6.5 7.6.5.1 7.6.5.2 7.6.6

7.7
7.7.1 7.7.2 7.7.3 7.7.3.1 7.7.3.2 7.7.4 7.7.4.1 7.7.4.2 7.7.4.3 7.7.5 7.7.5.1 7.7.5.2 7.7.5.3 7.7.6 7.7.6.1 7.7.6.2 7.7.6.3 7.7.6.4 7.7.7 7.7.8 7.7.9 7.7.9.1 7.7.10 7.7.10.1

Viewing Optimisation Results in the Map Window ....................................................................618 Viewing Optimisation Results Using the Histogram ..................................................................624 Verifying Network Capacity ....................................................................................................625 Importing a Drive Test Data Path....................................................................................................625 Displaying Drive Test Data..............................................................................................................627 Defining the Display of a Drive Test Data Path...............................................................................628 Network Verification ........................................................................................................................628 Filtering Incompatible Points Along Drive Test Data Paths .......................................................628 Creating Coverage Predictions from Drive Test Data Paths .....................................................630 Displaying Statistics Over a Drive Test Data Path ....................................................................631 Extracting a Field From a Drive Test Data Path for a Transmitter ............................................631 Analysing Data Variations Along the Path.................................................................................632 Exporting a Drive Test Data Path....................................................................................................633 Extracting CW Measurements from Drive Test Data ......................................................................633 Printing and Exporting the Drive Test Data Window .......................................................................634 Co-planning UMTS Networks with Other Networks ...................................................634 Switching to Co-planning Mode ......................................................................................................635 Working with Coverage Predictions in a Co-Planning Project ........................................................636 Updating Coverage Predictions.................................................................................................636 Analysing Coverage Predictions ...............................................................................................637 Performing Inter-Technology Neighbour Allocation ........................................................................640 Setting Inter-Technology Exceptional Pairs ..............................................................................640 Configuring Importance Factors for Inter-Technology Neighbours ...........................................642 Allocating Inter-Technology Neighbours Automatically .............................................................642 Displaying Inter-Technology Neighbours on the Map ...............................................................644 Allocating and Deleting Inter-Technology Neighbours per Cell .................................................645 Calculating the Importance of Existing Inter-technology Neighbours ........................................647 Checking the Consistency of the Inter-technology Neighbour Plan ..........................................649 Creating a UMTS Sector From a Sector in the Other Network .......................................................650 Using ACP in a Co-planning Project ...............................................................................................650 Creating a New Co-planning Optimisation Setup......................................................................651 Importing the Other Network into the Setup ..............................................................................651 Ending Co-planning Mode...............................................................................................................652 Advanced Configuration...........................................................................................................652 Modelling Inter-Carrier Interference ................................................................................................652 Defining Frequency Bands..............................................................................................................652 The Global Transmitter Parameters................................................................................................653 The Options on the Global Parameters Tab..............................................................................653 Modifying Global Transmitter Parameters.................................................................................654 Radio Bearers .................................................................................................................................654 Defining R99 Radio Bearers......................................................................................................654 Defining HSDPA Radio Bearers ................................................................................................655 Defining HSUPA Radio Bearers ................................................................................................655 Site Equipment................................................................................................................................656 Creating Site Equipment ...........................................................................................................656 Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer ...............657 Defining Resource Consumption per UMTS Site Equipment and HSUPA Radio Bearer .........657 Receiver Equipment........................................................................................................................657 Setting Receiver Height.............................................................................................................657 Creating or Modifying Reception Equipment .............................................................................657 HSDPA UE Categories..............................................................................................................659 HSUPA UE Categories..............................................................................................................659 Multiple Input Multiple Output Systems...........................................................................................660 Conditions for Entering the Active Set ............................................................................................661 Modelling Shadowing ......................................................................................................................661 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class ......................661 Modelling Inter-Technology Interference.........................................................................................662 Defining Inter-Technology IRFs.................................................................................................663

8
8.1
8.1.1 8.1.1.1 8.1.1.2 8.1.1.3 8.1.1.4

CDMA2000 Networks..............................................................................................................667
Planning and Optimising CDMA Base Stations ...........................................................667
Creating a CDMA Base Station.......................................................................................................668 Definition of a Base Station .......................................................................................................668 Creating or Modifying a Base Station Element..........................................................................673 Placing a New Station Using a Station Template ......................................................................674 Managing Station Templates.....................................................................................................676

14

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Table of Contents

8.1.1.5 8.1.2 8.1.3 8.1.4 8.1.5 8.1.6 8.1.6.1 8.1.6.2 8.1.6.3 8.1.6.4 8.1.6.5 8.1.7 8.1.7.1 8.1.7.2 8.1.7.3 8.1.7.4 8.1.8 8.1.9 8.1.9.1 8.1.9.2 8.1.10 8.1.10.1 8.1.10.2 8.1.10.3 8.1.10.4 8.1.10.5 8.1.10.6 8.1.10.7 8.1.10.8 8.1.10.9 8.1.11 8.1.11.1 8.1.11.2 8.1.11.3 8.1.11.4 8.1.11.5 8.1.11.6 8.1.11.7 8.1.11.8 8.1.11.9 8.1.12 8.1.12.1 8.1.12.2 8.1.12.3 8.1.12.4

8.2
8.2.1 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.3 8.2.4 8.2.4.1 8.2.4.2 8.2.4.3 8.2.4.4 8.2.4.5 8.2.4.6 8.2.4.7 8.2.4.8 8.2.4.9 8.2.5 8.2.5.1 8.2.5.2

Duplicating of an Existing Base Station .................................................................................... 680 Creating a Group of Base Stations................................................................................................. 680 Modifying Sites and Transmitters Directly on the Map ................................................................... 681 Display Tips for Base Stations ....................................................................................................... 681 Creating a Dual-Band CDMA Network ........................................................................................... 682 Creating a Repeater ....................................................................................................................... 682 Creating and Modifying Repeater Equipment........................................................................... 682 Placing a Repeater on the Map Using the Mouse .................................................................... 683 Creating Several Repeaters ..................................................................................................... 683 Defining the Properties of a Repeater ...................................................................................... 683 Tips for Updating Repeater Parameters ................................................................................... 685 Creating a Remote Antenna ........................................................................................................... 685 Placing a Remote Antenna on the Map Using the Mouse ........................................................ 685 Creating Several Remote Antennas ......................................................................................... 686 Defining the Properties of a Remote Antenna .......................................................................... 686 Tips for Updating Remote Antenna Parameters....................................................................... 687 Setting the Working Area of an Atoll Document ............................................................................. 687 Studying a Single Base Station ...................................................................................................... 687 Making a Point Analysis to Study the Profile ............................................................................ 688 Studying Signal Level Coverage............................................................................................... 689 Studying Base Stations .................................................................................................................. 691 Path Loss Matrices ................................................................................................................... 692 Assigning a Propagation Model ................................................................................................ 693 The Calculation Process........................................................................................................... 695 Creating a Computation Zone................................................................................................... 696 Setting Transmitters or Cells as Active..................................................................................... 696 Signal Level Coverage Predictions........................................................................................... 697 Analysing a Coverage Prediction.............................................................................................. 701 CDMA-Specific Coverage Predictions ...................................................................................... 709 Printing and Exporting Coverage Prediction Results................................................................ 727 Planning Neighbours ...................................................................................................................... 727 Importing Neighbours ............................................................................................................... 727 Defining Exceptional Pairs........................................................................................................ 728 Configuring Importance Factors for Neighbours....................................................................... 728 Allocating Neighbours Automatically ........................................................................................ 728 Checking Automatic Allocation Results .................................................................................... 732 Allocating and Deleting Neighbours per Cell ............................................................................ 734 Calculating the Importance of Existing Neighbours .................................................................. 736 Checking the Consistency of the Neighbour Plan .................................................................... 738 Exporting Neighbours ............................................................................................................... 739 Planning PN Offsets ....................................................................................................................... 739 Defining Exceptional Pairs for PN Offset Allocation ................................................................. 739 Allocating PN Offsets................................................................................................................ 740 Checking the Consistency of the PN Offset Plan ..................................................................... 742 Displaying the Allocation of PN Offsets .................................................................................... 743 Studying Network Capacity ................................................................................................... 746 Defining Multi-service Traffic Data ................................................................................................. 746 Creating a Traffic Map.................................................................................................................... 747 Creating a Sector Traffic Map................................................................................................... 747 Creating a User Profile Traffic Map .......................................................................................... 748 Creating User Density Traffic Maps (No. Users/km2)............................................................... 753 Converting 2G Network Traffic ................................................................................................. 755 Exporting Cumulated Traffic ..................................................................................................... 755 Exporting a Traffic Map .................................................................................................................. 756 Calculating and Displaying Traffic Simulations .............................................................................. 756 The Power Control Simulation Algorithm.................................................................................. 756 Creating Simulations................................................................................................................. 758 Displaying the Traffic Distribution on the Map .......................................................................... 760 Displaying the User Active Set on the Map .............................................................................. 762 Displaying the Results of a Single Simulation .......................................................................... 762 Displaying the Average Results of a Group of Simulations ...................................................... 767 Updating Cell Values With Simulation Results ......................................................................... 768 Adding New Simulations to an Atoll Document ........................................................................ 769 Estimating a Traffic Increase .................................................................................................... 771 Analysing the Results of a Simulation ............................................................................................ 771 Making an AS Analysis of Simulation Results .......................................................................... 771 Making Coverage Predictions Using Simulation Results.......................................................... 772

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

15

Atoll User Manual

8.3
8.3.1 8.3.2 8.3.3 8.3.4 8.3.4.1 8.3.4.2 8.3.4.3 8.3.4.4 8.3.4.5 8.3.4.6 8.3.5 8.3.6 8.3.7

Verifying Network Quality ........................................................................................................772

Importing a Drive Test Data Path....................................................................................................773 Displaying Drive Test Data..............................................................................................................775 Defining the Display of a Drive Test Data Path...............................................................................775 Network Verification ........................................................................................................................776 Filtering Incompatible Points Along Drive Test Data Paths .......................................................776 Creating Coverage Predictions from Drive Test Data Paths .....................................................777 Displaying Statistics Over a Drive Test Data Path ....................................................................778 Extracting a Field From a Drive Test Data Path for a Transmitter ............................................779 Extracting a Field From a Drive Test Data Path for a Transmitter ............................................779 Analysing Data Variations Along the Path.................................................................................779 Exporting a Drive Test Data Path....................................................................................................781 Extracting CW Measurements from Drive Test Data ......................................................................781 Printing and Exporting the Drive Test Data Window .......................................................................782 Co-planning CDMA Networks with Other Networks...................................................782 Switching to Co-planning Mode ......................................................................................................782 Working with Coverage Predictions in a Co-Planning Project ........................................................784 Updating Coverage Predictions.................................................................................................784 Analysing Coverage Predictions ...............................................................................................785 Performing Inter-Technology Neighbour Allocation ........................................................................787 Setting Inter-Technology Exceptional Pairs ..............................................................................787 Configuring Importance Factors for Inter-Technology Neighbours ...........................................789 Allocating Inter-Technology Neighbours Automatically .............................................................789 Displaying Inter-Technology Neighbours on the Map ...............................................................791 Allocating and Deleting Inter-Technology Neighbours per Cell .................................................792 Calculating the Importance of Existing Inter-technology Neighbours ........................................794 Checking the Consistency of the Inter-technology Neighbour Plan ..........................................796 Creating a CDMA Sector From a Sector in the Other Network.......................................................797 Ending Co-planning Mode...............................................................................................................797 Advanced Configuration...........................................................................................................798 Defining Inter-Carrier Interference ..................................................................................................798 Defining Frequency Bands..............................................................................................................798 The Global Transmitter Parameters................................................................................................799 The Options on the Global Parameters Tab..............................................................................799 Modifying Global Transmitter Parameters.................................................................................799 Data Rates Available for Services in CDMA ...................................................................................800 The 1xEV-DO Rev. A Radio Bearers ..............................................................................................801 Defining the Forward Link 1xEV-DO Rev. A Radio Bearer .......................................................801 Defining the Reverse Link 1xEV-DO Rev. A Radio Bearer .......................................................801 Site Equipment................................................................................................................................801 Creating Site Equipment ...........................................................................................................801 Defining Channel Element Consumption per CDMA Site Equipment and Radio Configuration802 Receiver Equipment........................................................................................................................802 Setting Receiver Height.............................................................................................................802 Creating or Modifying Reception Equipment .............................................................................803 Conditions for Entering the Active Set ............................................................................................803 Modelling Shadowing ......................................................................................................................804 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class ......................804 Creating PN Offset Domains and Groups for PN Offset Allocation.................................................805 Modelling Inter-Technology Interference.........................................................................................806 Defining Inter-Technology IRFs.................................................................................................807

8.4
8.4.1 8.4.2 8.4.2.1 8.4.2.2 8.4.3 8.4.3.1 8.4.3.2 8.4.3.3 8.4.3.4 8.4.3.5 8.4.3.6 8.4.3.7 8.4.4 8.4.5

8.5
8.5.1 8.5.2 8.5.3 8.5.3.1 8.5.3.2 8.5.4 8.5.5 8.5.5.1 8.5.5.2 8.5.6 8.5.6.1 8.5.6.2 8.5.7 8.5.7.1 8.5.7.2 8.5.8 8.5.9 8.5.9.1 8.5.10 8.5.11 8.5.11.1

9
9.1 9.2
9.2.1 9.2.1.1 9.2.1.2 9.2.1.3 9.2.1.4 9.2.1.5 9.2.2 9.2.3 9.2.4 9.2.5 9.2.6

TD-SCDMA Networks .............................................................................................................811

Designing a TD-SCDMA Network .......................................................................................811 Planning and Optimising TD-SCDMA Base Stations ................................................812
Creating a TD-SCDMA Base Station ..............................................................................................812 Definition of a Base Station .......................................................................................................813 Creating or Modifying a Base Station Element..........................................................................819 Placing a New Base Station Using a Station Template.............................................................820 Managing Station Templates.....................................................................................................822 Duplicating of an Existing Base Station.....................................................................................826 Creating a Group of Base Stations .................................................................................................827 Modifying Sites and Transmitters Directly on the Map....................................................................828 Display Tips for Base Stations ........................................................................................................828 Creating a Dual-Band TD-SCDMA Network ...................................................................................828 Creating a Repeater........................................................................................................................828

16

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Table of Contents

9.2.6.1 9.2.6.2 9.2.6.3 9.2.6.4 9.2.6.5 9.2.7 9.2.7.1 9.2.7.2 9.2.7.3 9.2.7.4 9.2.8 9.2.9 9.2.9.1 9.2.9.2 9.2.10 9.2.10.1 9.2.10.2 9.2.10.3 9.2.10.4 9.2.10.5 9.2.10.6 9.2.10.7 9.2.10.8 9.2.10.9 9.2.10.10 9.2.11 9.2.11.1 9.2.11.2 9.2.11.3 9.2.11.4 9.2.11.5 9.2.12 9.2.12.1 9.2.12.2 9.2.12.3 9.2.12.4 9.2.12.5 9.2.12.6 9.2.12.7 9.2.12.8 9.2.12.9 9.2.13 9.2.13.1 9.2.13.2 9.2.13.3 9.2.13.4 9.2.13.5 9.2.13.6 9.2.13.7

9.3
9.3.1 9.3.1.1 9.3.1.2 9.3.2 9.3.3 9.3.3.1 9.3.3.2 9.3.3.3 9.3.3.4 9.3.3.5 9.3.4 9.3.5 9.3.5.1 9.3.5.2 9.3.5.3 9.3.5.4 9.3.5.5 9.3.5.6
Forsk 2010

Creating and Modifying Repeater Equipment........................................................................... 829 Placing a Repeater on the Map Using the Mouse .................................................................... 829 Creating Several Repeaters ..................................................................................................... 830 Defining the Properties of a Repeater ...................................................................................... 830 Tips for Updating Repeater Parameters ................................................................................... 831 Creating a Remote Antenna ........................................................................................................... 831 Placing a Remote Antenna on the Map Using the Mouse ........................................................ 832 Creating Several Remote Antennas ......................................................................................... 832 Defining the Properties of a Remote Antenna .......................................................................... 832 Tips for Updating Remote Antenna Parameters....................................................................... 833 Setting the Working Area of an Atoll Document ............................................................................. 833 Studying a Single Base Station ...................................................................................................... 834 Making a Point Analysis to Study the Profile ............................................................................ 834 Studying Signal Level Coverage............................................................................................... 835 Studying Base Stations .................................................................................................................. 837 Path Loss Matrices ................................................................................................................... 838 Assigning a Propagation Model ................................................................................................ 840 The Calculation Process........................................................................................................... 842 Creating a Computation Zone................................................................................................... 842 Setting Transmitters or Cells as Active..................................................................................... 842 Signal Level Coverage Predictions........................................................................................... 843 Analysing a Coverage Prediction.............................................................................................. 851 Signal Quality Coverage Predictions ........................................................................................ 858 HSDPA Coverage Prediction.................................................................................................... 877 Printing and Exporting Coverage Prediction Results................................................................ 879 Planning Frequencies..................................................................................................................... 879 Setting up N-Frequency Mode.................................................................................................. 880 Allocating Frequencies Automatically ....................................................................................... 880 Checking Automatic Allocation Results .................................................................................... 880 Allocating Carrier Types per Transmitter .................................................................................. 881 Checking the Consistency of the Frequency Allocation Plan ................................................... 881 Planning Neighbours ...................................................................................................................... 882 Defining Exceptional Pairs........................................................................................................ 882 Configuring Importance Factors for Neighbours....................................................................... 883 Allocating Neighbours Automatically ........................................................................................ 883 Checking Automatic Allocation Results .................................................................................... 885 Importing Neighbours ............................................................................................................... 887 Allocating and Deleting Neighbours per Cell ............................................................................ 887 Calculating the Importance of Existing Neighbours .................................................................. 890 Checking the Consistency of the Neighbour Plan .................................................................... 891 Exporting Neighbours ............................................................................................................... 892 Planning Scrambling Codes ........................................................................................................... 892 Defining the Scrambling Code Format...................................................................................... 892 Creating Scrambling Code Domains and Groups..................................................................... 893 Defining Exceptional Pairs for Scrambling Code Allocation ..................................................... 893 Defining Scrambling Code Relativity Clusters .......................................................................... 893 Allocating Scrambling Codes.................................................................................................... 894 Checking the Consistency of the Scrambling Code Plan ......................................................... 897 Displaying the Allocation of Scrambling Codes ........................................................................ 897 Studying Network Capacity ................................................................................................... 900 TD-SCDMA Network Capacity ....................................................................................................... 901 Calculating Available Network Capacity ................................................................................... 901 Calculating Required Network Capacity ................................................................................... 902 Defining Multi-service Traffic Data ................................................................................................. 905 Creating a Traffic Map.................................................................................................................... 905 Creating a Sector Traffic Map................................................................................................... 906 Creating a User Profile Traffic Map .......................................................................................... 907 Creating User Density Traffic Maps (No. Users/km2)............................................................... 911 Converting 2G Network Traffic ................................................................................................. 913 Exporting Cumulated Traffic ..................................................................................................... 913 Exporting a Traffic Map .................................................................................................................. 914 Calculating and Displaying Traffic Simulations .............................................................................. 914 The Monte Carlo Simulation Algorithm ..................................................................................... 914 Creating Simulations................................................................................................................. 917 Displaying the Traffic Distribution on the Map .......................................................................... 918 Displaying the User Best Server on the Map............................................................................ 920 Displaying the Results of a Single Simulation .......................................................................... 920 Displaying the Average Results of a Group of Simulations ...................................................... 924
Unauthorized reproduction or distribution of this document is prohibited

17

Atoll User Manual

9.3.5.7 9.3.5.8 9.3.5.9 9.3.6

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.5 9.4.6 9.4.7

9.5
9.5.1 9.5.2 9.5.2.1 9.5.2.2 9.5.3 9.5.3.1 9.5.3.2 9.5.3.3 9.5.3.4 9.5.3.5 9.5.3.6 9.5.3.7 9.5.4 9.5.5

9.6
9.6.1 9.6.2 9.6.3 9.6.3.1 9.6.3.2 9.6.4 9.6.4.1 9.6.4.2 9.6.5 9.6.5.1 9.6.5.2 9.6.6 9.6.7 9.6.7.1 9.6.7.2 9.6.7.3 9.6.8 9.6.8.1 9.6.9

Updating Cell and Timeslot Values With Simulation Results ....................................................926 Adding New Simulations to an Atoll Document .........................................................................926 Estimating a Traffic Increase .....................................................................................................928 Making Coverage Predictions Using Simulation Results ................................................................928 Verifying Network Capacity ....................................................................................................929 Importing a Drive Test Data Path....................................................................................................929 Displaying Drive Test Data..............................................................................................................931 Defining the Display of a Drive Test Data Path...............................................................................932 Network Verification ........................................................................................................................932 Filtering Incompatible Points Along Drive Test Data Paths .......................................................932 Displaying Statistics Over a Drive Test Data Path ....................................................................934 Extracting a Field From a Drive Test Data Path for a Transmitter ............................................934 Analysing Data Variations Along the Path.................................................................................935 Exporting a Drive Test Data Path....................................................................................................936 Extracting CW Measurements from Drive Test Data ......................................................................936 Printing and Exporting the Drive Test Data Window .......................................................................937 Co-planning TD-SCDMA Networks with Other Networks .......................................937 Switching to Co-planning Mode ......................................................................................................937 Working with Coverage Predictions in a Co-Planning Project ........................................................939 Updating Coverage Predictions.................................................................................................939 Analysing Coverage Predictions ...............................................................................................940 Performing Inter-Technology Neighbour Allocation ........................................................................942 Setting Inter-Technology Exceptional Pairs ..............................................................................942 Configuring Importance Factors for Inter-Technology Neighbours ...........................................944 Allocating Inter-Technology Neighbours Automatically .............................................................944 Displaying Inter-Technology Neighbours on the Map ...............................................................946 Allocating and Deleting Inter-Technology Neighbours per Cell .................................................947 Calculating the Importance of Existing Inter-technology Neighbours ........................................949 Checking the Consistency of the Inter-technology Neighbour Plan ..........................................951 Creating a TD-SCDMA Sector From a Sector in the Other Network ..............................................952 Ending Co-planning Mode...............................................................................................................952 Advanced Configuration...........................................................................................................952 Defining Inter-Carrier Interference ..................................................................................................953 Defining Frequency Bands..............................................................................................................953 The Global Transmitter Parameters................................................................................................953 The Options on the Global Parameters Tab..............................................................................953 Modifying Global Transmitter Parameters.................................................................................955 Smart Antenna Modelling................................................................................................................955 Types of Smart Antenna Modelling ...........................................................................................955 Smart Antenna Equipment ........................................................................................................958 Radio Bearers .................................................................................................................................960 Defining R99 Radio Bearers......................................................................................................960 Defining HSDPA Radio Bearers ................................................................................................961 Creating Site Equipment .................................................................................................................961 Receiver Equipment........................................................................................................................962 Setting Receiver Height.............................................................................................................962 Creating or Modifying Reception Equipment .............................................................................962 Creating or Modifying HSDPA User Equipment Categories......................................................963 Modelling Shadowing ......................................................................................................................963 Displaying the Shadowing Margins ...........................................................................................963 Maximum System Range ................................................................................................................964

10
10.1 10.2
10.2.1 10.2.1.1 10.2.1.2 10.2.1.3 10.2.1.4 10.2.1.5 10.2.2 10.2.3 10.2.4 10.2.5 10.2.6

WiMAX BWA Networks..........................................................................................................967

Designing a WiMAX Network ................................................................................................967 Planning and Optimising WiMAX Base Stations .........................................................968
Creating a WiMAX Base Station .....................................................................................................969 Definition of a Base Station .......................................................................................................969 Creating or Modifying a Base Station Element..........................................................................975 Placing a New Base Station Using a Station Template.............................................................976 Managing Station Templates.....................................................................................................977 Duplicates of an Existing Base Station......................................................................................981 Creating a Group of Base Stations .................................................................................................982 Modifying Sites and Transmitters Directly on the Map....................................................................983 Display Tips for Base Stations ........................................................................................................983 Creating a Multi-Band WiMAX Network ..........................................................................................983 Setting the Working Area of an Atoll Document..............................................................................983

18

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Table of Contents

10.2.7 10.2.7.1 10.2.7.2 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.8.8 10.2.8.9 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.9.6 10.2.9.7 10.2.9.8 10.2.9.9 10.2.10 10.2.10.1 10.2.10.2 10.2.11 10.2.11.1 10.2.11.2 10.2.11.3

10.3
10.3.1 10.3.2 10.3.2.1 10.3.2.2 10.3.2.3 10.3.2.4 10.3.2.5 10.3.3 10.3.4 10.3.4.1 10.3.4.2 10.3.5 10.3.5.1 10.3.5.2 10.3.5.3 10.3.5.4 10.3.5.5 10.3.5.6 10.3.5.7 10.3.6

10.4
10.4.1 10.4.1.1 10.4.1.2 10.4.1.3 10.4.1.4 10.4.2 10.4.2.1 10.4.2.2 10.4.2.3 10.4.3 10.4.3.1 10.4.3.2 10.4.4 10.4.5 10.4.6

Studying a Single Base Station ...................................................................................................... 984 Making a Point Analysis to Study the Profile ............................................................................ 984 Studying Signal Level Coverage............................................................................................... 985 Studying Base Stations .................................................................................................................. 987 Path Loss Matrices ................................................................................................................... 988 Assigning a Propagation Model ................................................................................................ 990 The Calculation Process........................................................................................................... 992 Creating a Computation Zone................................................................................................... 992 Setting Transmitters or Cells as Active..................................................................................... 993 Signal Level Coverage Predictions........................................................................................... 993 Analysing a Coverage Prediction.............................................................................................. 997 WiMAX Coverage Predictions ................................................................................................ 1006 Printing and Exporting Coverage Prediction Results.............................................................. 1022 Planning Neighbours .................................................................................................................... 1022 Importing Neighbours ............................................................................................................. 1022 Defining Exceptional Pairs...................................................................................................... 1023 Configuring Importance Factors for Neighbours..................................................................... 1023 Allocating Neighbours Automatically ...................................................................................... 1023 Checking Automatic Allocation Results .................................................................................. 1026 Allocating and Deleting Neighbours per Cell .......................................................................... 1029 Calculating the Importance of Existing Neighbours ................................................................ 1031 Checking the Consistency of the Neighbour Plan .................................................................. 1032 Exporting Neighbours ............................................................................................................. 1033 Planning Frequencies................................................................................................................... 1033 Allocating Frequencies ........................................................................................................... 1033 Displaying the Frequency Allocation....................................................................................... 1035 Planning Preamble Indexes ......................................................................................................... 1037 Allocating Preamble Indexes .................................................................................................. 1037 Checking the Consistency of the Preamble Index Plan.......................................................... 1039 Displaying the Allocation of Preamble Indexes....................................................................... 1039 Studying Network Capacity ................................................................................................. 1041 Defining Multi-service Traffic Data ............................................................................................... 1041 Creating a Traffic Map.................................................................................................................. 1042 Creating a Sector Traffic Map................................................................................................. 1042 Creating a User Profile Traffic Map ........................................................................................ 1043 Creating User Density Traffic Maps (No. Users/km2)............................................................. 1048 Converting 2G Network Traffic ............................................................................................... 1050 Exporting Cumulated Traffic ................................................................................................... 1050 Exporting a Traffic Map ................................................................................................................ 1050 Working with a Subscriber Database ........................................................................................... 1051 Creating a Subscriber List ...................................................................................................... 1051 Performing Calculations on Subscriber lists ........................................................................... 1054 Calculating and Displaying Traffic Simulations ............................................................................ 1054 WiMAX Traffic Simulation Algorithm....................................................................................... 1055 Creating Simulations............................................................................................................... 1056 Displaying the Traffic Distribution on the Map ........................................................................ 1057 Displaying the Results of a Single Simulation ........................................................................ 1061 Displaying the Average Results of a Group of Simulations .................................................... 1065 Updating Cell Load Values With Simulation Results .............................................................. 1067 Estimating a Traffic Increase .................................................................................................. 1068 Making Coverage Predictions Using Simulation Results ............................................................. 1068 Optimising Network Parameters Using the ACP....................................................... 1068 The ACP Module and Atoll ........................................................................................................... 1068 Using Zones with ACP............................................................................................................ 1069 Using Traffic Maps with ACP .................................................................................................. 1069 Shadowing Margin and Indoor Coverage ............................................................................... 1070 ACP and Antenna Masking..................................................................................................... 1070 Configuring the ACP Module ........................................................................................................ 1072 Configuring the Default Settings ............................................................................................. 1072 Defining the Antenna Masking Method................................................................................... 1073 Saving Settings to a User Configuration File .......................................................................... 1074 Optimising Cell Planning with the ACP ........................................................................................ 1075 Creating an Optimisation Setup.............................................................................................. 1075 Defining Optimisation Parameters .......................................................................................... 1076 Running an Optimisation Setup.................................................................................................... 1098 Working with Optimisations in the Explorer Window .................................................................... 1099 Viewing Optimisation Results....................................................................................................... 1100

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

19

Atoll User Manual

10.4.6.1 10.4.6.2 10.4.6.3

10.5
10.5.1 10.5.2 10.5.3 10.5.4 10.5.4.1 10.5.4.2 10.5.4.3 10.5.4.4 10.5.4.5 10.5.5 10.5.6 10.5.7

10.6
10.6.1 10.6.2 10.6.2.1 10.6.2.2 10.6.3 10.6.3.1 10.6.3.2 10.6.3.3 10.6.3.4 10.6.3.5 10.6.3.6 10.6.3.7 10.6.4 10.6.5 10.6.5.1 10.6.5.2 10.6.6

10.7
10.7.1 10.7.2 10.7.2.1 10.7.2.2 10.7.3 10.7.4 10.7.5 10.7.6 10.7.7 10.7.8 10.7.8.1 10.7.8.2 10.7.8.3 10.7.9 10.7.10 10.7.11 10.7.11.1 10.7.12 10.7.12.1

10.8 10.9

Viewing Optimisation Results in the Properties Dialogue .......................................................1101 Viewing Optimisation Results in the Map Window ..................................................................1107 Viewing Optimisation Results Using the Histogram ................................................................1113 Verifying Network Capacity ..................................................................................................1114 Importing a Drive Test Data Path..................................................................................................1114 Displaying Drive Test Data............................................................................................................1116 Defining the Display of a Drive Test Data Path.............................................................................1117 Network Verification ......................................................................................................................1117 Filtering Incompatible Points Along Drive Test Data Paths .....................................................1117 Creating Coverage Predictions from Drive Test Data Paths ...................................................1119 Displaying Statistics Over a Drive Test Data Path ..................................................................1119 Extracting a Field From a Drive Test Data Path for a Transmitter ..........................................1120 Analysing Data Variations Along the Path...............................................................................1120 Exporting a Drive Test Data Path..................................................................................................1122 Extracting CW Measurements from Drive Test Data ....................................................................1122 Printing and Exporting the Drive Test Data Window .....................................................................1122 Co-planning WiMAX Networks with Other Networks ...............................................1123 Switching to Co-planning Mode ....................................................................................................1123 Working with Coverage Predictions in a Co-Planning Project ......................................................1124 Updating Coverage Predictions...............................................................................................1125 Analysing Coverage Predictions .............................................................................................1125 Performing Inter-Technology Neighbour Allocation ......................................................................1128 Setting Inter-Technology Exceptional Pairs ............................................................................1128 Configuring Importance Factors for Inter-Technology Neighbours .........................................1130 Allocating Inter-Technology Neighbours Automatically ...........................................................1130 Displaying Inter-Technology Neighbours on the Map .............................................................1131 Allocating and Deleting Inter-Technology Neighbours per Cell ...............................................1132 Calculating the Importance of Existing Inter-technology Neighbours ......................................1135 Checking the Consistency of the Inter-technology Neighbour Plan ........................................1136 Creating a WiMAX Sector From a Sector in the Other Network ...................................................1137 Using ACP in a Co-planning Project .............................................................................................1137 Creating a New Co-planning Optimisation Setup....................................................................1138 Importing the Other Network into the Setup ............................................................................1138 Ending Co-planning Mode.............................................................................................................1139 Advanced Configuration.........................................................................................................1139 Defining Frequency Bands............................................................................................................1139 The Global Transmitter Parameters..............................................................................................1140 The Options on the Global Parameters Tab............................................................................1140 Modifying Global Transmitter Parameters ...............................................................................1142 Defining Frame Configurations .....................................................................................................1143 Defining WiMAX Radio Bearers ....................................................................................................1145 Defining WiMAX Quality Indicators ...............................................................................................1145 Defining WiMAX Equipment..........................................................................................................1146 Defining WiMAX Schedulers .........................................................................................................1148 Smart Antenna Systems ...............................................................................................................1151 Optimum Beamformer .............................................................................................................1151 Conventional Beamformer.......................................................................................................1151 Defining Smart Antenna Equipment ........................................................................................1152 Multiple Input Multiple Output Systems.........................................................................................1153 Defining the Minimum Signal to Thermal Noise Threshold ...........................................................1154 Modelling Shadowing ....................................................................................................................1154 Displaying the Shadowing Margins per Clutter Class .............................................................1155 Modelling Inter-Technology Interference.......................................................................................1155 Defining Inter-Technology IRFs...............................................................................................1156 Tips and Tricks ...........................................................................................................................1157

Glossary of WiMAX Terms ...................................................................................................1166

11
11.1 11.2
11.2.1 11.2.1.1 11.2.1.2 11.2.1.3 11.2.1.4 11.2.1.5

LTE Networks ..............................................................................................................................1171

Designing an LTE Network ...................................................................................................1171 Planning and Optimising LTE Base Stations ...............................................................1172
Creating an LTE Base Station.......................................................................................................1173 Definition of a Base Station .....................................................................................................1173 Creating or Modifying a Base Station Element........................................................................1178 Placing a New Base Station Using a Station Template...........................................................1180 Managing Station Templates...................................................................................................1181 Duplicates of an Existing Base Station....................................................................................1184
Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

20

Table of Contents

11.2.2 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.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.8.7 11.2.8.8 11.2.8.9 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.9.6 11.2.9.7 11.2.9.8 11.2.9.9 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.3
11.3.1 11.3.2 11.3.2.1 11.3.2.2 11.3.2.3 11.3.2.4 11.3.2.5 11.3.3 11.3.4 11.3.4.1 11.3.4.2 11.3.5 11.3.5.1 11.3.5.2 11.3.5.3 11.3.5.4 11.3.5.5 11.3.5.6 11.3.5.7 11.3.6

11.4
11.4.1 11.4.1.1 11.4.1.2 11.4.1.3 11.4.1.4 11.4.2 11.4.2.1 11.4.2.2 11.4.2.3 11.4.3

Creating a Group of Base Stations............................................................................................... 1185 Modifying Sites and Transmitters Directly on the Map ................................................................. 1186 Display Tips for Base Stations ..................................................................................................... 1186 Creating a Multi-Band LTE Network ............................................................................................. 1186 Setting the Working Area of an Atoll Document ........................................................................... 1187 Studying a Single Base Station .................................................................................................... 1187 Making a Point Analysis to Study the Profile .......................................................................... 1187 Studying Signal Level Coverage............................................................................................. 1189 Studying Base Stations ................................................................................................................ 1190 Path Loss Matrices ................................................................................................................. 1191 Assigning a Propagation Model .............................................................................................. 1193 The Calculation Process......................................................................................................... 1195 Creating a Computation Zone................................................................................................. 1195 Setting Transmitters or Cells as Active................................................................................... 1196 Signal Level Coverage Predictions......................................................................................... 1196 Analysing a Coverage Prediction............................................................................................ 1200 LTE Coverage Predictions...................................................................................................... 1209 Printing and Exporting Coverage Prediction Results.............................................................. 1225 Planning Neighbours .................................................................................................................... 1225 Importing Neighbours ............................................................................................................. 1225 Defining Exceptional Pairs...................................................................................................... 1225 Configuring Importance Factors for Neighbours..................................................................... 1226 Allocating Neighbours Automatically ...................................................................................... 1226 Checking Automatic Allocation Results .................................................................................. 1228 Allocating and Deleting Neighbours per Cell .......................................................................... 1231 Calculating the Importance of Existing Neighbours ................................................................ 1233 Checking the Consistency of the Neighbour Plan .................................................................. 1234 Exporting Neighbours ............................................................................................................. 1235 Planning Frequencies................................................................................................................... 1235 Allocating Frequencies ........................................................................................................... 1236 Displaying the Frequency Allocation....................................................................................... 1237 Planning Physical Cell IDs ........................................................................................................... 1239 Allocating Physical Cell IDs .................................................................................................... 1239 Checking the Consistency of the Physical Cell ID Plan.......................................................... 1241 Displaying the Allocation of Physical Cell IDs......................................................................... 1241 Studying Network Capacity ................................................................................................. 1243 Defining Multi-service Traffic Data ............................................................................................... 1243 Creating a Traffic Map.................................................................................................................. 1244 Creating a Sector Traffic Map................................................................................................. 1244 Creating a User Profile Traffic Map ........................................................................................ 1245 Creating User Density Traffic Maps (No. Users/km2)............................................................. 1250 Converting 2G Network Traffic ............................................................................................... 1252 Exporting Cumulated Traffic ................................................................................................... 1252 Exporting a Traffic Map ................................................................................................................ 1252 Working with a Subscriber Database ........................................................................................... 1253 Creating a Subscriber List ...................................................................................................... 1253 Performing Calculations on Subscriber lists ........................................................................... 1256 Calculating and Displaying Traffic Simulations ............................................................................ 1256 LTE Traffic Simulation Algorithm ............................................................................................ 1257 Creating Simulations............................................................................................................... 1258 Displaying the Traffic Distribution on the Map ........................................................................ 1259 Displaying the Results of a Single Simulation ........................................................................ 1263 Displaying the Average Results of a Group of Simulations .................................................... 1266 Updating Cell Load Values With Simulation Results .............................................................. 1268 Estimating a Traffic Increase .................................................................................................. 1269 Making Coverage Predictions Using Simulation Results ............................................................. 1269 Optimising Network Parameters Using the ACP....................................................... 1270 The ACP Module and Atoll ........................................................................................................... 1270 Using Zones with ACP............................................................................................................ 1270 Using Traffic Maps with ACP .................................................................................................. 1271 Shadowing Margin and Indoor Coverage ............................................................................... 1271 ACP and Antenna Masking..................................................................................................... 1271 Configuring the ACP Module ........................................................................................................ 1273 Configuring the Default Settings ............................................................................................. 1273 Defining the Antenna Masking Method................................................................................... 1275 Saving Settings to a User Configuration File .......................................................................... 1275 Optimising Cell Planning with the ACP ........................................................................................ 1276

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

21

Atoll User Manual

11.4.3.1 11.4.3.2 11.4.4 11.4.5 11.4.6 11.4.6.1 11.4.6.2 11.4.6.3

11.5
11.5.1 11.5.2 11.5.3 11.5.4 11.5.4.1 11.5.4.2 11.5.4.3 11.5.4.4 11.5.4.5 11.5.5 11.5.6 11.5.7

11.6
11.6.1 11.6.2 11.6.2.1 11.6.2.2 11.6.3 11.6.3.1 11.6.3.2 11.6.3.3 11.6.3.4 11.6.3.5 11.6.3.6 11.6.3.7 11.6.4 11.6.5 11.6.5.1 11.6.5.2 11.6.6

11.7
11.7.1 11.7.2 11.7.2.1 11.7.2.2 11.7.3 11.7.4 11.7.5 11.7.6 11.7.7 11.7.8 11.7.9 11.7.9.1 11.7.10 11.7.11

11.8 11.9

Creating an Optimisation Setup ..............................................................................................1276 Defining Optimisation Parameters...........................................................................................1277 Running an Optimisation Setup ....................................................................................................1299 Working with Optimisations in the Explorer Window.....................................................................1300 Viewing Optimisation Results........................................................................................................1301 Viewing Optimisation Results in the Properties Dialogue .......................................................1302 Viewing Optimisation Results in the Map Window ..................................................................1308 Viewing Optimisation Results Using the Histogram ................................................................1314 Verifying Network Capacity ..................................................................................................1315 Importing a Drive Test Data Path..................................................................................................1315 Displaying Drive Test Data............................................................................................................1317 Defining the Display of a Drive Test Data Path.............................................................................1317 Network Verification ......................................................................................................................1318 Filtering Incompatible Points Along Drive Test Data Paths .....................................................1318 Creating Coverage Predictions from Drive Test Data Paths ...................................................1320 Displaying Statistics Over a Drive Test Data Path ..................................................................1320 Extracting a Field From a Drive Test Data Path for a Transmitter ..........................................1320 Analysing Data Variations Along the Path...............................................................................1321 Exporting a Drive Test Data Path..................................................................................................1322 Extracting CW Measurements from Drive Test Data ....................................................................1322 Printing and Exporting the Drive Test Data Window .....................................................................1323 Co-planning LTE Networks with Other Networks ......................................................1323 Switching to Co-planning Mode ....................................................................................................1324 Working with Coverage Predictions in an Co-Planning Project ....................................................1325 Updating Coverage Predictions...............................................................................................1325 Analysing Coverage Predictions .............................................................................................1326 Performing Inter-Technology Neighbour Allocation ......................................................................1328 Setting Inter-Technology Exceptional Pairs ............................................................................1328 Configuring Importance Factors for Inter-Technology Neighbours .........................................1330 Allocating Inter-Technology Neighbours Automatically ...........................................................1330 Displaying Inter-Technology Neighbours on the Map .............................................................1333 Allocating and Deleting Inter-Technology Neighbours per Cell ...............................................1333 Calculating the Importance of Existing Inter-technology Neighbours ......................................1336 Checking the Consistency of the Inter-technology Neighbour Plan ........................................1338 Creating an LTE Sector From a Sector in the Other Network.......................................................1339 Using ACP in a Co-planning Project .............................................................................................1339 Creating a New Co-planning Optimisation Setup....................................................................1339 Importing the Other Network into the Setup ............................................................................1340 Ending Co-planning Mode.............................................................................................................1341 Advanced Configuration.........................................................................................................1341 Defining Frequency Bands............................................................................................................1341 The Global Transmitter Parameters..............................................................................................1342 The Options on the Global Parameters Tab............................................................................1342 Modifying Global Transmitter Parameters ...............................................................................1343 Defining LTE Radio Bearers .........................................................................................................1344 Defining LTE Quality Indicators.....................................................................................................1344 Defining LTE Equipment ...............................................................................................................1345 Defining LTE Schedulers ..............................................................................................................1347 Multiple Input Multiple Output Systems.........................................................................................1349 Defining the Minimum Signal to Thermal Noise Threshold ...........................................................1350 Modelling Shadowing ....................................................................................................................1350 Displaying the Shadowing Margins per Clutter Class .............................................................1351 Modelling Inter-Technology Interference.......................................................................................1351 Listing LTE Frame Details.............................................................................................................1352 Tips and Tricks ...........................................................................................................................1353

Glossary of LTE Terms ..........................................................................................................1357

Index ................................................................................................................................................... 1361

22

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1
The Working Environment

RF Planning & Optimisation Software

Atoll

Chapter 1: The Working Environment

The Working Environment

The Atoll working environment provides a comprehensive and integrated set of tools and features that allow you to create and define your radio-planning project in a single application. You can save the entire project as a single file, or you can link your project to external files. Atoll uses standard Windows interface elements, with the ability to have several document windows open at the same time, support for drag-and-drop, context menus, and support for standard Windows shortcuts, for example, for cutting and pasting. Atoll also allows you to undo recent changes to your document. Atoll offers the standard Windows Print functionality, with added functionality allowing you to print either the entire map window, parts of it, or only certain objects. Atoll also provides other tools, such as a search tool to locate either a site, a point on the map, or a vector. The Explorer window plays a central role in Atoll. The Explorer window contains most of the objects in a document arranged in folders. Using the Explorer window, you can manage all objects in the Atoll document: sites, transmitters, calculations, etc., as well as geographic data such as the Digital Terrain Model (DTM), traffic maps, and clutter classes. You can, for example, define various studies or configure the parameters or display of data objects. The content of the folders in the Explorer window can be displayed in tables, allowing you to manage large amounts of data. You can sort and filter the data in a table, or change how the data is displayed. You can also use the table feature to enter large amounts of information by cutting and pasting the information from any Windows spreadsheet into the table. The map is the working area for your document and Atoll provides many features for working with the map. You can change the view by moving or zooming in or out and you can choose which objects are displayed and how they are displayed. You can also export the current display definition, or configuration, to use it in other documents. This chapter explains the following topics: "The Atoll Work Area" on page 25 "The Explorer Window" on page 27 "Working with Objects" on page 29 "Printing in Atoll" on page 64 "Working with Maps" on page 38 "Working with Data Tables" on page 53 "Grouping, Sorting, and Filtering Data" on page 69 "Tips and Tricks" on page 84.

1.1

The Atoll Work Area

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

25

Atoll User Manual

Toolbar

Document window (map)

Workspace Explorer window (docked)

Panoramic window (floating)

Point Analysis window (docked) Figure 1.1: Atoll user interface

1.1.1

Working with Document Windows

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

To cascade document windows: Select Window > Cascade.

1.1.2

Docking or Floating an Atoll Window

Only document windows are part of an individual Atoll document. Other windows and tools, such as the Explorer window, display the content of the active document. They are not part of the individual Atoll document, but part of the working environment and, when you switch to a different document, they will display the content of the active document. You can change how these windows and tools are displayed. You can also choose to remove them from their position and float them over the Atoll working environment. To display a window: On the View menu, select the name of the window.

To close a window: Click the Hide button ( ) in the corner of the window. Depending on the position of the docking window, this button can be in the upper-left or upper-right corner.

You can change how much room a window takes if it shares a docking area with other windows by maximising or minimising the window. To maximise a window in its docking area: Click the Maximise button ( ) near the corner of the window. Depending on the position of the window, this button can be in the upper-left or upper-right corner.

To minimise a window in its docking area: Click the Minimise button ( ) near the corner of the window. Depending on the position of the window, this button can be in the upper-left or upper-right corner.

You can leave a window in its docking area, or you can have it float over the working environment, allowing you to maximise the amount of area for document windows or other windows.

26

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment To float a window: Double-click the docking window title bar. The docking window leaves the docking area and floats over the working environment. Note: You can move the docking window by clicking the title bar and dragging it. To prevent the window from docking as you move it, press CTRL as you drag the docking window.

To dock a window: To return the window to its previous docked location, double-click the docking window title bar. Or Click the title bar of the docking window and drag the window to a different docking area. Note: The window positions for docking windows are not associated with the current document; they remain the same no matter which document you open.

1.2

The Explorer Window

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

1.2.1

Working with the Explorer Window Tabs

The Explorer window has three tabs: The Data tab: The Data tab allows you to manage radio data and calculations. Depending on the modules installed with Atoll, the Data tab has the following folders: Sites Antennas Transmitters Predictions UMTS Parameters, CDMA2000 Parameters, GSM/GPRS Parameters, WiMAX 802.16d Parameters, WiMAX 802.16e Parameters, or LTE Parameters UMTS Simulations, CDMA2000 Simulations , WiMAX 802.16d Simulations, WiMAX 802.16e simulations, or LTE Simulations Traffic analysis (GSM/GPRS/EDGE projects only) Hexagonal design Microwave links CW Measurements and Drive test data

The Geo tab: The Geo tab allows you to manage geographic data. The number of folders depends on the number and types of geographical data types (vector data, scanned images, etc.) you import or create: Clutter classes Clutter heights Digital Terrain Model Population data Any other geo data map Traffic (GSM/GPRS/EDGE/TDMA, UMTS HSPA, CDMA2000)

The Modules tab: The Modules tab allows you to manage the propagation models and additional modules. It contains: A Propagation Models folder with the following propagation models: Longley-Rice Okumura-Hata Cost-Hata Standard Propagation Model ITU 526-5 ITU 370-7 (Vienna 93)

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

27

Atoll User Manual ITU 1546 WLL Microwave Propagation Model Erceg-Greenstein (SUI)

The AFP models available in your Atoll installation. Any additional module created using the API.

1.2.2

Navigating in the Explorer Window

The Explorer window has three tabs; each tab has objects and folders containing objects. To move from one tab to another: Click the tab at the top of the Explorer window.

A folder on a tab can be opened to allow you to view its contents. Each folder containing at least one object has an Expand ( ) or Contract button ( ) to the left of its name. To expand a folder to display its contents: Click the Expand button ( ) to the left of its name.

1.2.3

Displaying or Hiding Objects on the Map Using the Explorer

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

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

1.2.4

Working with Layers Using the Explorer

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

28

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

Figure 1.2: Moving a layer Note: Before you print a map, you should pay attention to the arrangement of the layers. For more information, see "Printing Recommendations" on page 65.

1.3

Working with Objects

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

1.3.1

Using the Object Context Menu

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

1.3.1.1

Renaming an Object
You can change the name of an object in Atoll. To rename an object: 1. Right-click the object either in the Explorer window or on the map. The context menu appears. 2. Select Rename from the context menu. 3. Enter the new name and press ENTER to change the name. Note: In Atoll, objects such as sites or transmitters are named with default prefixes. Individual objects are distinguished from each other by the number added automatically to the default prefix. You can change the default prefix for sites, transmitters, and cells by editing the atoll.ini file. For more information, see the Administrator Manual.

1.3.1.2

Deleting an Object
You can delete objects from either the Explorer window or from the map. To delete an object: 1. Right-click the object either in the Explorer window or on the map. The context menu appears. 2. Select Delete from the context menu. The selected object is deleted.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

29

Atoll User Manual

1.3.1.3

Displaying the Properties of an Object

You can modify the properties of an object in the Properties dialogue. To open the Properties dialogue of a data object: 1. Right-click the object either in the Explorer window or on the map. The context menu appears.

Tip:

When you are selecting data objects on the map, it can be difficult to ensure that the correct object has been selected. When a site is selected, the site (and its name) is surrounded by a black frame ( ). When a transmitter is selected, both ends of its icon have a green point ( ). When there is more than one transmitter with with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter you want (see "Selecting One of Several Transmitters" on page 31).

2. Select Properties from the context menu. The Properties dialogue appears.

Switching Between Property Dialogues

You can switch between the Properties dialogues of items (transmitters, antennas, sites, services, user profiles, etc.) in the same folder or subfolder in the Explorer window by using the browse buttons ( corner of each Properties dialogue: : jump to the first item in the list : jump to the previous item in the list : jump to the next item in the list : jump to the last item in the list ) in the lower-left

If you have made any changes to the properties of an item, Atoll prompts you to confirm these changes before switching to the next Properties dialogue. You can use this feature, for example, to access the properties of co-site transmitters without closing and reopening the Properties dialogue. Switching is performed within the lowest subfolder in the hierarchy. For example: If transmitters are grouped by site, you can switch only within one site (co-site transmitters). If transmitters are grouped by a flag, you can switch only within this group. If transmitters are grouped by activity and by a flag, you can switch only within transmitters having the same activity and the same flag.

The browse buttons are not available: When creating a new item. When opening the an items Properties dialogue by double-clicking its record in a table. For repeater properties. For propagation model properties.

The Display tab of the Properties dialogue is explained in the following section.

1.3.2

Modifying Sites and Transmitters Directly on the Map

In a complex radio-planning project, it can be difficult to find the data object in the Data tab, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sitesand transmitters directly from the map. You can also change the position of a site by dragging it, or by letting Atoll find a higher location for it. In this section, the following are explained: "Selecting One of Several Transmitters" on page 31 "Moving a Site Using the Mouse" on page 31 "Moving a Site to a Higher Location" on page 31 "Changing the Azimuth of the Antenna Using the Mouse" on page 31 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32.

30

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.3.2.1

Selecting One of Several Transmitters

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

Figure 1.3: Selecting one transmitter 2. Select the transmitter from the context menu. When you select a transmitter, it appears with a green point at both ends of the icon ( ).

1.3.2.2

Moving a Site Using the Mouse

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

Tip:

While this method allows you to place a site quickly, you can adjust the location more precisely by editing the coordinates on the General tab of the Site Properties dialogue.

1.3.2.3

Moving a Site to a Higher Location

If you want to improve the location of a site, in terms of reception and transmission, Atoll can find a higher location within a specified radius from the current location of the site. To have Atoll move a site to a higher location: 1. Right-click the site in the map window. The context menu appears. 2. Select Move to a Higher Location. 3. In the Move to a Higher Location dialogue, enter the radius of the area in which Atoll should search and click OK. Atoll moves the site to the highest point within the specified radius.

1.3.2.4

Changing the Azimuth of the Antenna Using the Mouse

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

To modify the azimuth of the antenna using the mouse: 1. On the map, click the antenna whose azimuth you want to modify. 2. Move the pointer to the end of the antenna with a green circle ( ). An arc with an arrow appears under the pointer.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

31

Atoll User Manual 3. Click the green circle and drag it to change the antennas azimuth. The current azimuth of the antenna is displayed in the far left of the status bar. 4. Release the mouse when you have set the azimuth to the desired angle. The antennas azimuth is modified on the Transmitter tab of the Transmitter Properties dialogue. You can also modify the azimuth on the map for all the antennas on a base station using the mouse. To modify the azimuth of all the antennas on a base station using the mouse: 1. On the map, click one of the antennas whose azimuth you want to modify. 2. Move the pointer to the end of the antenna with a green circle ( ). An arc with an arrow appears under the pointer. 3. Hold CTRL and, on the map, click the green circle and drag it to change the antennas azimuth. The current azimuth of the antenna is displayed in the far left of the status bar. 4. Release the mouse when you have set the azimuth of the selected antenna to the desired angle. The azimuth of the selected antenna is modified on the Transmitter tab of the Transmitter Properties dialogue. The azimuth of the other antennas on the base station is offset by the same amount as the azimuth of the selected antenna. Note: 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 to undo the changes made. in the toolbar)

1.3.2.5

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

1.3.3

Display Properties of Objects

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

32

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.3.3.1

Defining the Display Properties of Objects

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

Figure 1.5: The Display tab for an individual site To define the display properties of an object type: 1. Right-click the object type folder in the Explorer window. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Select the Display tab. Depending on the object type, the following options are available: "Defining the Display Type" on page 33 "Defining the Transparency of Objects and Object Types" on page 35 "Defining the Visibility Scale" on page 35 "Defining the Object Type Label" on page 35 "Defining the Object Type Tip Text" on page 36 "Adding an Object Type to the Legend" on page 36

4. Set the display parameters. 5. Click OK.

Defining the Display Type

Depending on the object selected, you can choose from the following display types: unique, discrete values, value intervals, or automatic. To change the display type: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 32. 2. Select the display type from the Display Type list:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

33

Atoll User Manual Unique: defines the same symbol for all objects of this type. By defining a unique symbol for an object type, objects of different types, for example, sites or transmitters, are immediately identifiable. i. To modify the appearance of the symbol, click the symbol in the table below. The Symbol Style dialogue appears.

ii. Modify the symbol as desired. iii. Click OK to close the Symbol Style dialogue. Discrete values: defines the display of each object according to the value of a selected field. This display type can be used to distinguish objects of the same type by one characteristic. For example, you could use this display type to distinguish transmitter by antenna type, or to distinguish inactive from active sites. i. Select the name of the Field by which you want to display the objects.

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

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

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

Using the Actions Button

The Actions button on the Display tab of the Properties dialogue allows you to modify the display type as defined in "Defining the Display Type" on page 33. To access the Actions menu: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 32. 2. Click the Actions button. The Actions menu gives you access to the following commands: Select all: Atoll selects all the values in the table. Delete: Atoll removes selected value from the table. Insert before: When the selected display type is value intervals, Atoll inserts a new threshold in the table before the threshold selected in the table. Insert after: When the selected display type is value intervals, Atoll inserts a new threshold in the table after the threshold selected in the table. Properties: Atoll opens the Display dialogue where you may change the colour and style. Shading: Atoll opens the Shading dialogue. When "Value Intervals" is the selected display type, you select Shading to define the number of value intervals and configure their colour. Enter the upper and lower limits of the value in the First Break and Last Break boxes respectively, and enter a value in the Interval box. Define the colour shading by choosing a Start Colour and an End Colour. The value intervals will be determined by the set values and coloured by a shade going from the set start colour to the set end colour. When "Discrete Values" is the selected display type, you select Shading to choose a Start Colour and an End Colour.

34

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment Configuration: Select Import if you want to import an existing display configuration. Select Export if you want to export the display settings of the current object to a configuration file, so that you can share them with other users or use them in other documents.

Defining the Transparency of Objects and Object Types

You can change the transparency of some objects, such as predictions, and some object types, such as clutter classes, to allow objects on lower layers to be visible on the map. To change the transparency: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 32. 2. Move the Transparency slider to the right to make the object or object type more transparent or to the left to make it less transparent.

Defining the Visibility Scale

You can define a visibility range for object types. An object is visible only if the scale, as displayed on the Map toolbar, is within this range. This can be used to, for example, prevent the map from being cluttered with symbols when you are at a certain scale. Visibility ranges are taken into account for screen display, and for printing and previewing printing. They do not affect which objects are considered during calculations. To define an object visibility range: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 32. 2. Enter a Visibility Scale minimum in the between 1: text box. 3. Enter a Visibility Scale maximum in the and 1: text box.

Defining the Object Type Label

For most object types, such as sites and transmitters, you can display information about each object in the form of a label that is displayed with the object. You can display information from every field in that object types data table, including from fields that you add. To define a label for an object type: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 32. 2. Click the Browse button ( ) beside the Label box. The Field Selection dialogue appears (see Figure 1.6).

Figure 1.6: Defining a label 3. Select the fields which you want to display in the label: a. To select a field to be displayed in the label for the object type, select the field in the Available Fields list and click to move it to the Selected Fields list.

b. To remove a field from the list of Group these fields in this order, select the field in the Selected Fields list and click to remove it.

c. To change the order of the fields, select a field and click or to move it up or down in the list. The objects will be grouped in the order of the fields in the Selected Fields list, from top to bottom. 4. Click OK to close the Field Selection dialogue and click OK to close the Properties dialogue.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

35

Atoll User Manual

Note:

For most object types, you can also display object information in the form of a tool tip 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 tool tips, see "Defining the Object Type Tip Text" on page 36.

Defining the Object Type Tip Text

For most object types, such as sites and transmitters, you can display information about each object in the form of a tool tip that is only visible when you move the pointer over the object. You can display information from every field in that object types data table, including from fields that you add. In the Explorer window, the tool tip displays the total and filtered numbers of elements present in the Sites and Transmitters folders, and their subfolders. To define tip text for an object type: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 32. 2. Click the Browse button ( ) beside the Tip Text box. The Field Selection dialogue appears (see Figure 1.6).

3. Select the fields which you want to display in the tool tip: a. To select a field to be displayed in the tool tip for the object type, select the field in the Available Fields list and click to move it to the Selected Fields list.

b. To remove a field from the list of Group these fields in this order, select the field in the Selected Fields list and click Note: to remove it. For most object types, you can also display object information in the form of a label that is displayed with the object. This option has the advantage of keep object-related information permanently visible. For more information on tool tips, see "Defining the Object Type Label" on page 35.

Once you have defined the tool tips, you must activate the tool tip function before they appear. To activate the tool tip function: Click the Display Tips button ( ) on the toolbar. Tool tips will now appear when the pointer is over the object.

If you have more than one coverage prediction displayed on the map, the tool tips display the tip text for all the coverage predictions available on a pixel up to a maximum of 30 lines. You can change this default maximum using an option in the atoll.ini file. For more information, see the Administrator Manual.

Adding an Object Type to the Legend

You can display the information defined by the display type (see "Defining the Display Type" on page 33) in your Atoll documents legend. Only visible objects appear in the Legend window. For information on displaying or hiding objects, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In Figure 1.7, on the Display tab of a signal level prediction, the intervals defined are: Signal level >= -65 red -65 > Signal level >= -105 shading from red to blue (9 intervals) Signal level < -105 not shown in the coverage.

The entries in the Legend column will appear in the Legend window.

Figure 1.7: Defined thresholds as they will appear in the Legend With value intervals, you can enter information in the Legend column to be displayed on the legend. If there is no information entered in this column, the maximum and minimum values are displayed instead. 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 32. 2. Check the Add to legend box. The defined display will appear on the legend.

36

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment To display the Legend window: Select View > Legend. The Legend window appears.

You can also display the comments defined in the properties of a coverage prediction in the Legend window by setting an option in the atoll.ini file. For more information about setting options in the atoll.ini file, see the Administrator Manual.

1.3.3.2

Examples of Using the Display Properties of Objects

In this section are the following examples of how display properties of objects can be used: "Automatic Display Type - Server Coverage Studies" on page 37 "Shading - Signal Level Study" on page 37.

Automatic Display Type - Server Coverage Studies

When doing a best server prediction, Atoll calculates, for each pixel on the map, which server is best received. If the selected display type for transmitters is "Automatic," Atoll colours each pixel on the map according to the colour of the transmitter that is best received on that pixel. This way, you can identify immediately which transmitter is best received on each pixel. The following two figures show the results of the same best server area and handover margin study. In Figure 1.8, the transmitter display type is "Discrete Values," with the site name as the chosen value. The difference in colour is insufficient to make clear which transmitter is best received on each pixel. In Figure 1.9, the transmitter display type is "Automatic." Because Atoll ensures that each transmitter has a different colour than the transmitters surrounding it, the study results are also immediately visible.

Figure 1.8: Value interval display type

Figure 1.9: Automatic display type

To display the results of a server coverage study with the transmitters set to the Automatic display type: 1. Right-click the Transmitters folder in the Explorer window. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Select the Display tab. 4. Select "Automatic" as the Display Type. 5. Click OK. 6. Click the Refresh button ( ) to update the display of the study results.

Shading - Signal Level Study

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

37

Atoll User Manual

Figure 1.10: Shading from -60 dBm to -105 dBm To change how the results of a signal level study are displayed:

Figure 1.11: Shading from -80 dBm to -105 dBm

1. Expand the Predictions folder in the Explorer window and right-click the signal level study. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Select the Display tab. 4. Click Actions to display the menu and select Shading. The Shading dialogue appears. 5. Change the value of the First Break to "-80". Leave the value of the Last Break at "-105." 6. Click OK to close the Shading dialogue. 7. Click OK to close the Properties dialogue and apply your changes.

1.4

Working with Maps

Atoll has the following functions to help you work with maps: "Changing the Map Scale" on page 38 "Moving the Map in the Document Window" on page 39 "Using the Panoramic Window" on page 39 "Centring the Map Window on an Object" on page 40 "Measuring Distances on the Map" on page 40 "Displaying Rulers Around the Map" on page 40 "Displaying the Map Legend" on page 41 "Using Zones in the Map Window" on page 41 "Editing Polygons, Lines, and Points" on page 46 "Saving a Map as a Graphic Image" on page 51 "Copying a Map to Another Application" on page 52. "Map Window Pointers" on page 52.

1.4.1

Changing the Map Scale

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

1.4.1.1

Zooming In and Out

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

2. Click the map where you want to zoom in. Note: You can also zoom in by pressing CTRL++, by selecting Zoom In from the View menu, or by holding down the CTRL key and rotating the mouse wheel button forward.

38

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment To zoom out on the map: 1. Click the Zoom icon ( ) on the Map toolbar (or press CTRL+Q).

2. Right-click the map where you want to zoom out. Note: You can also zoom out by pressing CTRL+, by selecting Zoom Out from the View menu, or holding down the CTRL key and rotating the mouse wheel button backward.

1.4.1.2

Zooming In on a Specific Area

To zoom in on a specific area of the map: 1. Click the Zoom Area icon ( ) on the Map toolbar (or press CTRL+W).

2. Click in the map on one of the four corners of the area you want to select. 3. Drag to the opposite corner. When you release the mouse button, Atoll zooms in on the selected area.

1.4.1.3

Choosing a Scale
To choose a scale: 1. Click the arrow next to the scale box ( 2. Select the scale from the list. If the scale value you want is not in the list: 1. Click in the scale box ( 2. Enter the desired scale. 3. Press ENTER. Atoll zooms the map to the entered scale. ) on the Map toolbar. ) on the Map toolbar.

1.4.1.4

Changing Between Previous Zoom Levels

Atoll saves the last five zoom levels, allowing you to move quickly between previous zoom levels and zoomed areas. To move between zoom levels: Click the Previous Zoom button ( ) to return to a zoom level you have already used (or press ALT +

).

Once you have returned to a previous zoom level, click the Next Zoom button ( level (or press ALT +

).

) to return to the latest zoom

1.4.2

Moving the Map in the Document Window

You can move the map in the document window using the mouse. To move the map in the document window: 1. Click the Move Map Window button ( ) on the Map toolbar (or press CTRL + D).

2. Move the pointer over the map and drag the map in the desired direction.

1.4.3

Using the Panoramic Window

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

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

39

Atoll User Manual To move around the map: 1. Click in the Panoramic window in the zoom area (i.e., the dark rectangle). 2. Drag the rectangle to its new position.

1.4.4

Centring the Map Window on an Object

You can centre the map on any selected object, for example, a transmitter, a site, or on any zone in the Zones folder on the Geo tab of the Explorer window. When centring the map window on an object the current scale is kept. You can select the object in the map window or in the Explorer window. To the map window on a selected object: 1. Right-click the object in the map window or in the Explorer window. 2. Select Centre in the Map Window from the context menu.

Tip:

If you want to quickly find an object, such as a site, on the map, you can select it in the Explorer window and then select the Centre in the Map Window command.

1.4.5

Measuring Distances on the Map

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

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

To measure the total distance on the map on a line over a series of points: 1. Click the Distance Measurement button ( ) on the toolbar.

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

Total distance between Azimuth between secondfirst and last point last and last point Distance between secondlast and last point Figure 1.12: Measurement data in the status bar

1.4.6

Displaying Rulers Around the Map

You can display rulers around the map in the document window. To display rulers: 1. Select Tools > Options. 2. In the Options dialogue, click the Coordinates tab.

40

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment 3. Under Display rulers, select where you want the rulers to be displayed in the map window. 4. Click OK.

1.4.7

Displaying the Map Legend

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

1.4.8

Using Zones in the Map Window

On the Geo tab of the Explorer window, Atoll provides you with a set of tools known as zones. The zones are a type of polygons, which can be created and modified in the same way as contours, lines, or points. Zones can be used to define areas of the map for the following purposes: Filtering Zone: The filtering zone is a graphical filter that restricts the objects displayed on the map and on the Data tab of the Explorer window to the objects inside the filtering zone. It also restricts which objects are used in calculations such as coverage predictions, etc. Computation Zone: The computation zone is used to define which base stations are to be taken into consideration in calculations and the area where Atoll calculates path loss matrices, coverage studies, etc. Focus Zone and Hot Spot Zones: With the focus zone and hot spot zones, 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. Important: Zones are taken into account whether or not they are visible. In other words, if you have drawn a zone, it will be taken into account whether or not its visibility check box in the Zones folder of the Geo tab in the Explorer window is selected. For example, if you have filtered the sites using a filtering zone, the sites outside the filtering zone will not be taken into consideration in coverage predictions, even if you have cleared the filtering zones visibility check box. You will have to delete the zone if you no longer want to select sites using a filtering zone. In this section, the following are explained: "Using a Filtering Zone" on page 41 "Using a Computation Zone" on page 42 "Using a Focus Zone or Hot Spot Zones" on page 43 "Using Polygon Zone Editing Tools" on page 44 "Using a Printing Zone" on page 45 "Using a Geographic Export Zone" on page 46.

1.4.8.1

Using a Filtering Zone

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

1.4.8.1.1

Creating a Filtering Zone

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

3. Right-click the Filtering Zone folder. 4. Select Draw from the context menu. 5. Draw the filtering zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

41

Atoll User Manual The filtering zone is delimited by a blue line. The data objects outside of the selected zone are filtered out. On the Data tab of the Explorer window, any folder whose content is affected by the filtering zone appears with a special icon ( ), to indicate that the folder contents have been filtered.

You can also create a filtering zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the filtering zone. Existing polygon: You can use any existing polygon on the map as a filtering zone by right-clicking it and selecting Use as > Filtering Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a filtering zone. You can import it by right-clicking the Filtering Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a filtering zone the size of the map window by selecting Fit to Map Window from the context menu.

Once you have created a filtering zone, you can use Atolls polygon editing tools to edit it. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44. Note: You can export the filtering zone as a polygon, so that you can use it in a different Atoll document, by right-clicking the Filtering Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

1.4.8.2

Using a Computation Zone

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

1.4.8.2.1

Creating a Computation Zone

To create a computation zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Computation Zone folder. The context menu appears. 4. Select Draw from the context menu. 5. Draw the computation zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. The computation zone is delimited by a red line. You can also create a computation zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and selecting Use as > Computation Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a computation zone the size of the map window by selecting Fit to Map Window from the context menu.

Once you have created a computation zone, you can use Atolls polygon editing tools to edit it. For more information on the polygon editing tools, see"Using Polygon Zone Editing Tools" on page 44.

42

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

Note:

You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: Saving the computation zone in the user configuration: For information on exporting the computation zone in the user configuration, see "Exporting a User Configuration" on page 79. Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

1.4.8.3

Using a Focus Zone or Hot Spot Zones

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

1.4.8.3.1

Drawing a Focus Zone or Hot Spot Zones

To define a focus zone or hot spot zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. Select Draw from the context menu. 5. Draw the focus or hot spot zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot zone in one of the following ways: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the focus or hot spot zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot zone by right-clicking it and selecting Use as > Focus Zone or Use as > New Hot Spot from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot spot zones, you can import the name (in text format) given to each zone as well. Additionally, because you can have several hot spot zones, you can import more than one polygon into the Hot Spot folder, with each as a separate hot spot zone. Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map Window from the context menu. Note: You can save the focus zone or hot spot zones, so that you can use it in a different Atoll document, in the following ways: Saving the focus zone in the user configuration: For information on exporting the focus zone in the user configuration, see "Exporting a User Configuration" on page 79. Exporting the focus zone or hot spot zones: You can export the focus zone or hot spot zones by right-clicking the Focus Zone or the Hot Spot Zones folder on the Data tab of the Explorer window and selecting Export from the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

43

Atoll User Manual

1.4.8.4

Using Polygon Zone Editing Tools

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

1.4.8.4.1

Editing Polygon Zones

You can edit polygon zones in several ways. Before you can edit a polygon zone, you must first put it in editing mode. To put the polygon zone in editing mode: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder.

3. Right-click the folder containing the polygon zone you want to edit. 4. Select Edit from the context menu. The vector tools on the Vector Edition toolbar are activated.

Tip:

You can also activate the vector tools by selecting the polygon zone to edit from the Vector Edition toolbar list.

You can now edit the polygon zone as explained in the following sections: "Editing the Points of a Polygon Zone" on page 44 "Editing Polygon Zones Using the Toolbar" on page 44 "Editing Polygon Zones Using the Context Menu" on page 45.

Editing the Points of a Polygon Zone

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

ii. Drag the point to its new position. Adding a point to the polygon zone: i. Position the pointer over the polygon zone border where you want to add a point. The pointer changes ( ).

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

ii. Right-click and select Delete Point from the context menu. The point is deleted.

Editing Polygon Zones Using the Toolbar

In Atoll, you can create complex polygon zones by using the tools on the Vector Edition toolbar. The filtering, computation, and focus zone polygons can contain holes. The holes within polygonal areas are differentiated from overlaying polygons by the order of the coordinates of their vertices. The coordinates of the vertices of polygonal areas are in clockwise order, whereas the coordinates of the vertices of holes within polygonal areas are in counter-clockwise order. To edit a polygon zone using the icons on the Vector Edition toolbar: 1. Put the polygon zone in editing mode as explained in "Editing Polygon Zones" on page 44. 2. Click the contour to edit. The Vector Edition toolbar has the following buttons: i. : To combine several polygon zones: In the Vector Edition toolbar, click the Combine button ( ).

ii. Click once on the map where you want to begin drawing the new polygon zone. iii. Click each time you change angles on the border defining the outside of the polygon zone.

44

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment 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. i. : To delete part of the selected polygon zone: In the Vector Edition toolbar, click the Delete button ( ).

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

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

ii. Click once on the map where you want to begin drawing the polygon that will split the selected one. iii. Click each time you change angles on the border defining the outside of the polygon. iv. Double-click to close the polygon. Atoll separates the area covered by the polygon from the selected polygon and creates a new polygon.

Editing Polygon Zones Using the Context Menu

When you are editing polygon zones, you can access certain commands using the context menu. To edit a polygon zone using the context menu: 1. Click the polygon zone you want to edit. 2. Right-click the polygon zone to display the context menu and select one of the following: Properties: Select Properties to open the Properties dialogue of the selected polygon zone. The Properties dialogue gives the coordinates of each point that defines the position and shape of the polygon zone. Insert Point: Select Insert Point to add a point to the border of the contour at the position of the pointer. Move: i. Select Move from the context menu to move the contour, line, or point on the map.

ii. Move the contour, line, or point. iii. Click to place the contour, line, or point. Quit edition: Select Quit Edition to exit editing mode. Delete: Select Delete to remove the selected contour, line, or point from the map.

1.4.8.4.2

Removing a Polygon Zone

When you no longer need a polygon zone, you can remove the zone and redisplay all data objects. To remove a polygon zone: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder.

3. Right-click the folder containing the zone you want to remove. 4. From the context menu, select Delete Zone. The polygon zone is removed and all document data are now displayed.

Tip:

You can also delete it by right-clicking its border on the map and selecting Delete from the context menu.

1.4.8.5

Using a Printing Zone

The printing zone allows you to define the area to be printed. For information on using the printing zone, see "Defining the Printing Zone" on page 65.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

45

Atoll User Manual

1.4.8.6

Using a Geographic Export Zone

If you want to export part of the map as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, Atoll offers you the option of exporting only the area covered by the zone if you export the map as a raster image. To define a geographic export zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Geographic Export Zone folder. The context menu appears. 4. Select Draw from the context menu. 5. Draw the geographic export zone: a. Click the point on the map that will be one corner of the rectangle that will define the geographic export zone. b. Drag to the opposite corner of the rectangle that will define the geographic export zone. When you release the mouse, the geographic export zone will be created from the rectangle defined by the two corners. The geographic export zone is delimited by a light purple line . If you clear the geographic export zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a geographic export zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the geogaphic export zone. Existing polygon: You can use any existing polygon on the map as a geographic export zone by right-clicking it and selecting Use as > Geographic Export Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, you can import it and use it as a geographic export zone. You can import it by right-clicking the Geographic Export Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a geographic export zone the size of the map window by selecting Fit to Map Window from the context menu.

Once you have created a geographic export zone, you can use Atolls polygon editing tools to edit it. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44. Note: You can export the geographic export zone as a polygon, so that you can use it in a different Atoll document, by right-clicking the Geographic Export Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

Important: The geographic export zone can only export in raster format. You can not export in raster format if the coverage prediction was made per transmitter (for example, coverage predictions with the display type set by transmitter, by a transmitter attribute, by signal level, by path loss, or by total losses). Only the coverage area of a single transmitter can be exported in raster format.

1.4.9

Editing Polygons, Lines, and Points

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

46

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.4.9.1

Adding a Vector Layer

You can add vector objects such as polygons, lines or points to geographical map information in a project by first creating a vector layer. You can also modify certain geographic data maps, for example, population maps, and custom data, by adding a vector layer to them and afterwards adding polygons, lines and points. For information on modifying certain geographic data maps by adding a vector layer, see "Editing Population or Custom Data Maps" on page 135. To add a vector layer to the Geo tab: Click the New Vector Layer button ( ) ) on the Vector Edition toolbar.

Atoll creates a folder called "Vectors" on the Geo tab of the Explorer window. For information on adding vector objects such as contours, lines, and points to the vector layer, see "Creating Polygons, Lines, and Points" on page 47.

1.4.9.2

Creating Polygons, Lines, and Points

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

Tip:

You can also make the vector tools available by selecting the vector layer to edit from the Vector Edition toolbar list. Because Atoll names all new vector layers "Vectors" by default, it might be difficult to know which Vectors folder you are selecting. By renaming each vectors folder, you can ensure that you select the correct folder. For information on renaming objects, see "Renaming an Object" on page 29.

If the Vector Edition toolbar is not visible, select View > Vector Edition Toolbar. 3. Click one of the following buttons on the Vector Edition toolbar: New Polygon: a. Click once on the map where you want to begin drawing the contour. b. Click each time you change angles on the border defining the outside of the contour. c. Double-click to close the contour. New Rectangle: a. Click the point on the map that will be one corner of the rectangle. b. Drag to the opposite corner of the rectangle. c. Release the mouse to create the rectangle defined by the two corners. Note: If the polygon or rectangle is on the vector layer of a population map, or custom data, you must define the value the polygon or rectangle represents and map the vector layer. For more information, see "Editing Population or Custom Data Maps" on page 135.

New Line: a. Click once on the map where you want to begin the line. b. Click each time you change angles on the line. c. Double-click to end the line. New Point: Click once on the map where you want to place the point. 4. Press ESC to deselect the currently selected button on the Vector Edition toolbar.

1.4.9.3

Editing the Shape of Polygons and Lines

You can edit the shape of polygons and lines on the vector layer. To edit the shape of polygons and lines: 1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Edit from the context menu. The vector tools on the Vector Edition toolbar are activated.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

47

Atoll User Manual

Tip:

You can also activate the vector tools by selecting the vector layer to edit from the Vector Edition toolbar list.

3. Select the contour or line. You can now edit by: Moving a point: i. Position the pointer over the point you want to move. The pointer changes ( ).

ii. Drag the point to its new position. Adding a point to a contour or a line: i. Position the pointer over the contour border or line where you want to add a point. The pointer changes ( ).

ii. Right-click and select Insert Point from the context menu. A point is added to the contour border or line at the position of the pointer. Deleting a point from a contour or a line: 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.

1.4.9.4

Combining or Cropping Polygons Using the Toolbar

In Atoll, you can create complex contours by using the tools on the Vector Edition toolbar. To edit a vector object using the icons on the Vector Edition toolbar: 1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Edit from the context menu. The vector tools on the Vector Edition toolbar are activated.

Tip:

You can also activate the vector tools by selecting the vector layer to edit from the Vector Edition toolbar list.

3. Click the contour to edit. The Vector Edition toolbar has the following buttons: i. : To combine several contours: In the Vector Edition toolbar, click the Combine button ( ).

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

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

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

ii. Click once on the map where you want to begin drawing the contour that will split the selected one. iii. Click each time you change angles on the border defining the outside of the contour.

48

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment iv. Double-click to close the contour. Atoll separates the area covered by the contour from the selected contour and creates a new contour.

1.4.9.5

Editing a Point
To edit a point: 1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Edit from the context menu. The vector tools on the Vector Edition toolbar are activated.

Tip:

You can also activate the vector tools by selecting the vector layer to edit from the Vector Edition toolbar list.

3. Select the point. You can now edit by: Moving: i. Click the point you want to move. The pointer changes ( ).

ii. Drag the point to its new position. Deleting a point: i. Click the point you want to delete. The pointer changes ( ).

ii. Right-click and select Delete from the context menu. The point is deleted.

1.4.9.6

Editing Contours, Lines, and Points Using the Context Menu

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

ii. Move the contour, line, or point. iii. Click to place the contour, line, or point. Quit edition: Select Quit Edition to exit editing mode. Properties: Select Properties to open the Properties dialogue of the selected contour, line, or point. The Properties dialogue has two tabs: General: The General tab gives the name of the vector Layer, the Surface of the object, and any Properties of the contour, line, or point. Geometry: This tab gives the coordinates of each point that defines the position and shape of the contour, line, or point. Only the commands relevant to the selected contour, line, or point are displayed in the context menu.

Note:

1.4.10

Exporting Coverage Prediction Results

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

49

Atoll User Manual You can export coverage predictions separately or you can export several coverage predictions at the same time. When you export more than one coverage prediction, Atoll suggests the formats that can be used for all the coverage predictions to be exported. In this section, the following are explained: "Exporting an Individual Coverage Prediction in Vector Format" on page 50 "Exporting an Individual Coverage Prediction in Raster Format" on page 50 "Exporting Multiple Coverage Predictions" on page 51.

1.4.10.1

Exporting an Individual Coverage Prediction in Vector Format

To export a coverage prediction in vector format: 1. Select the Data tab in the Explorer window. 2. Click the Expand button ( Note: ) to expand the Predictions folder.

The coverage prediction must be displayed in the map window before it can be exported. For information on displaying objects in the map window, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.

3. Select Export the Coverage from the context menu. The Save As dialogue appears. 4. In the Save As dialogue, enter the File name and select the vector format from the Save as type list. If you have chosen to export the prediction coverage in a vector format other than in AGD format: a. If desired, under Coordinate Systems, change the reference coordinate system for the file being exported. b. If desired, change the Resolution of the exported coverage. The default resolution is the resolution of the coverage prediction results (as set in the coverage prediction Properties dialogue). c. If desired, move the Smoothing slider, or enter the percentage in the text box, to define how much Atoll smooths the exported coverage. 5. Click Save to export the coverage prediction results.

1.4.10.2

Exporting an Individual Coverage Prediction in Raster Format

To export a coverage prediction in raster format 1. Select the Data tab in the Explorer window. 2. Click the Expand button ( Note: ) to expand the Predictions folder.

The coverage prediction must be displayed in the map window before it can be exported. For information on displaying objects in the map window, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.

3. You can export the entire coverage prediction, the geographic export zone, or part of the coverage prediction. To export the entire coverage prediction: Right-click the coverage prediction you want to export.

To export the geographic export zone, define the geographic export zone: a. Click the Geo tab in the Explorer window. b. Click the Expand button ( ) to expand the Zones folder.

c. Right-click the Geographic Export Zone folder. The context menu appears. d. Select Draw from the context menu. e. Draw the geographic export zone by clicking the point on the map that will be one corner of the rectangle that will define the geographic export zone and dragging to the opposite corner of the rectangle that will define the geographic export zone. When you release the mouse, the geographic export zone will be created from the rectangle defined by the two corners. The geographic export zone is delimited by a light purple line. If you clear the geographic export zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. f. Right-click the coverage prediction you want to export.

To export part of the coverage prediction: a. Click the Expand button ( ) to expand the coverage prediction.

b. Right-click the part of the coverage prediction you want to export. 4. Select Export the Coverage from the context menu. The Save As dialogue appears.

50

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment 5. In the Save As dialogue, enter the File name and select the raster format from the Save as type list. 6. Enter the file name and select the type and the path of the file to be exported. 7. Click Save to export the coverage prediction results. The Raster Export dialogue appears. a. Under Region, select the area to export: The Coverage Area of the Prediction Study to export a rectangle containing only the area covered by the study, The Computation Zone to export a rectangle containing the entire computation zone, or The Geographic Export Zone to export the rectangle defined by the geographic export zone.

b. If desired, move the Smoothing slider, or enter the percentage in the text box, to define how much Atoll smooths the exported coverage. c. Click OK to finish exporting the coverage prediction results. Notes When selecting a coordinate system different than the one initially defined in Atoll, the file is converted using the selected coordinate system. You can not export in raster format if the coverage prediction was made per transmitter (for example, coverage predictions with the display type set by transmitter, by a transmitter attribute, by signal level, by path loss, or by total losses). Only the coverage area of a single transmitter can be exported in raster format.

1.4.10.3

Exporting Multiple Coverage Predictions

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

6. Click Export to export the selected coverage predictions. The selected coverage predictions are saved in the selected folder. Note: When you export several coverage predictions at the same time, Atoll does not take the geographic export zone into consideration. The geographic export zone is only taken into consideration for raster file formats.

1.4.11

Saving a Map as a Graphic Image

You can save a map as a graphic image. To save a map as a graphic image: 1. Click the Select an area button ( 2. Define the area to save: a. Click in the map on one of the four corners of the area you want to select. b. Drag to the opposite corner. 3. Select File > Save Image As. The Map Export dialogue appears. 4. In the Map Export dialogue, select the zone that you wish to save as an image. You can select: Selection: The area on the map selected in step 1. Geographic Export Zone Printing Zone ) in the Map toolbar.

5. Click Export. The Save As dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

51

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

1.4.12

Copying a Map to Another Application

You can copy a selected area of the map into a document created using another application. To copy a selected area of the map into a document created using another application: 1. Click the Select an area button ( 2. Define the area to copy: a. Click in the map on one of the four corners of the area you want to select. b. Drag to the opposite corner. 3. Select Edit > Copy Image. The Copy Image dialogue appears. 4. Define the resolution of the image in one of the following ways: Select Use Screen Resolution Select Use Custom Resolution and enter a resolution in metres. ) in the Map toolbar.

5. Click OK. 6. Open the application into which you want to paste the image. 7. In the new application, select Edit > Paste Special. 8. In the Paste Special dialogue, select Picture (Enhanced Metafile). Note: You can also select Bitmap to paste the selection without rulers, or Text to paste the upper left and lower right coordinates of the selection.

9. Click OK. The area of the map, including the rulers, is pasted as an image into the new document.

1.4.13

Map Window Pointers

In Atoll, the pointer appears in different forms according to its function. Each pointer is described below:

Appearance

Description Selection arrow

Meaning
The zone selection pointer indicates that, on the map, you can define a zone to print or copy and, in the Panoramic window, you can define the zone to be displayed on the map. To define a zone, click and drag diagonally. The polygon drawing pointer indicates you can draw a zone to filter either sites or transmitters, draw computation/focus/hot spot/filtering/printing/ eographic

Polygon drawing export zones, or draw vector or raster polygons on the map. To draw a polygon, pointer click once to start, and each time you change angles on the border defining the
outside of the polygon. Close the polygon by clicking twice. The rectangle drawing pointer indicates you can draw computation/focus/hot spot/filtering/printing/geographic export zones, or draw vector or raster rectangles on the map. To define a zone, click and drag diagonally. The hand pointer indicates you can move the visible part of the displayed map.

Rectangle drawing pointer Hand

52

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

Appearance

Description Zoom tool

Meaning
The zoom pointer indicates you can click to zoom in and right-click to zoom out at the location of the mouse pointer The zoom area pointer indicates you can zoom in on an area of the by clicking and dragging to define the area. The transmitter pointer indicates you can place a transmitter on the map where you click. You can place more than one station by pressing CTRL as you click on the map. The point analysis pointer indicates that you have selected the Point Analysis tool and have not yet chosen the first point. The point placed pointer indicates the position of the receiver on the map that is used for the point-to-point analysis. The results are displayed in the CW Measurements or Point Analysis window. The pencil pointer indicates you can create a polygonal clutter zone, by clicking once to start the polygon, once to create each corner, and by double-clicking to close the polygon. The deletion pointer indicates that you can delete a newly created polygonal clutter zone by clicking its border. The position indicator pointer indicates you can select the border of a polygon. Right-clicking the polygon border opens a context menu allowing you to add a point, delete the polygon, or centre the map on the polygon. The select/create points pointer indicates you can modify the polygon in the map window. You can add a new point and modify the polygon contour by clicking on one of the edges and dragging. You can move an existing point by clicking and dragging an existing point. You can right-click to open a context menu to delete a point, delete the polygon, or centre the map on the polygon. The first CW measurement point pointer indicates you can click a point on the map to create the first point of a CW measurement path.

Zoom area

New transmitter

Point analysis Point placed (Receiver) Pencil

Deletion Position indicator

Select/create points Placing a CW measurement point

Placing points in The next CW measurement point pointer indicates the first CW measurement a CW point has been set and you can now click other points on the map. Double-click measurement to end the CW measurement path. path Measurements on the map
The measurement pointer indicates you can click on the map to set the start point of your measurement. As you move the pointer, the distance between the first point and the pointer is displayed in the status bar. The terrain section pointer indicates that you can create a terrain section by clicking once on the map to create the first point and once more to create the second point. The terrain profile between the two points is displayed in the Point Analysis window and stored under Terrain Sections in the Geo tab.

Terrain section

1.5

Working with Data Tables

Atoll stores object data (sites, transmitters, repeaters, antennas, UMTS or CDMA2000 cells, UMTS or CDMA2000 parameters, etc.) in the form of tables, containing all their parameters and characteristics. The data contained in prediction reports are also stored in the form of tables. You can add columns to the data table and you can delete certain columns. When you create a new column, you can create a default value for a field you create. You can also create a list of options (for text fields) from which the user can choose when filling in the field. You can filter, sort, and group the data contained in these tables, and view a statistical analysis of the data. You can also export the data or import data into the Atoll data tables. In this section, the following are explained: "Opening a Data Table" on page 54 "Adding, Deleting, and Editing Data Table Fields" on page 54 "Editing the Contents of a Table" on page 55 "Opening an Objects Record Properties Dialogue from a Table" on page 56 "Defining the Table Format" on page 56 "Copying and Pasting in Tables" on page 59 "Viewing a Statistical Analysis of Table Contents" on page 61

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

53

Atoll User Manual "Exporting Tables to Text Files" on page 61 "Importing Tables from Text Files" on page 63 "Exporting Tables to XML Files" on page 64 "Importing Tables from XML Files" on page 64.

1.5.1

Opening a Data Table

To open a data table: 1. Click the Data tab in the Explorer window. 2. Right-click the data folder of which you want to display the data table. 3. Select Open Table from the context menu.

1.5.2

Adding, Deleting, and Editing Data Table Fields

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

1.5.2.1

Accessing an Object Types Table Fields

The fields contained in an object types table are defined in a dialogue. To access an object types table fields: 1. In the Explorer window, open the data table as described in "Opening a Data Table" on page 54. 2. Right-click the table in the map window. The context menu appears. 3. Select Table Fields from the context menu. A dialogue appears where you can view the existing fields and add or delete new ones. The dialogue displays the following information for each type of data (see Figure 1.13): The Name of the field in the database (Name). The Name of the field in the ATL file (Legend). The Type of the field. The maximum Size of the field. The Default value of the field. The Group to which the field belongs. When opening an Atoll document from a database, you can select a group of custom fields to be loaded from the database, instead of loading all custom fields.

Figure 1.13: The Table tab

1.5.2.2

Adding a Field to an Object Types Data Table

You can add a custom field to any object types data table. To add a custom field to an object types data table: 1. Access the object types table fields as explained in "Accessing an Object Types Table Fields" on page 54. 2. Click Add. The Field Definition dialogue appears (see Figure 1.14).

54

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment 3. The Field Definition dialogue has the following text boxes: Name: Enter the Name for the field that will appear in the database Group: If desired, you can define a Group that this custom field will belong to. When you open an Atoll document from a database, you can then select a specific group of custom fields to be loaded from the database, instead of loading all custom fields. Legend: Enter the name for the field that will appear in the Atoll document. Type: Select a type for the field (text, short integer, long integer, single, double, true/false, date/time, or currency) Size: The Size field is only available if you have selected "text" as the Type. Enter a size in characters. Default Value: If you want, enter a default value that will appear each time you create a new record of this object type. Choice List: The Choice List field is only available if you have selected "text" as the Type. You can create a choice list by entering the list items in the Choice List text box, separating each list item with a hard return.

4. Click OK to return to the object type table. Note: User or custom fields are for information only and are not taken into account in any calculation. You can find these fields in the Other Properties tab of an object types Properties dialogue.

Figure 1.14: The Field Definition dialogue

1.5.2.3

Deleting a Field from an Object Types Data Table

You can delete custom fields from an object types data table. Custom fields are the fields that the user adds to an object types data table, as explained in "Adding a Field to an Object Types Data Table" on page 54. To delete a custom field from an object types data table: Caution: All data stored in the field will be lost when you delete the field itself. Make sure that you are not deleting important information.

1. Access the object types table fields as explained in "Accessing an Object Types Table Fields" on page 54. 2. Select the custom field that you want to delete.

Tip:

Some fields can not be deleted. If you select a field and the Delete button remains unavailable, the selected field is not a custom field and can not be deleted.

3. Click Delete. The field is deleted from the object types data table.

1.5.3

Editing the Contents of a Table

To edit the contents of a table: 1. Click the Data tab in the Explorer window. 2. Right-click the data folder of which you want to display the data table. 3. Select Open Table from the context menu. 4. Edit the content of the table by entering the value directly in the field (see Figure 1.15). 5. Click elsewhere in the table when you have finished to update the table. Your changes are automatically saved.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

55

Atoll User Manual

Tip:

If a list of options has been defined for a field, you can select a value from the list (see Figure 1.16) or enter a new value.

Figure 1.15: Editing data in the transmitters data tables

Figure 1.16: Choosing data in the transmitters data tables

1.5.4

Opening an Objects Record Properties Dialogue from a Table

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

1.5.5

Defining the Table Format

Atoll lets you format the data tables so that the data presented is more legible or better presented. You can change the format of the data table by: "Formatting the Column Headers" on page 57 "Formatting Table Columns" on page 57 "Changing Column Width or Row Height" on page 57

56

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment "Displaying or Hiding a Column" on page 58 "Freezing or Unfreezing a Column" on page 58 "Moving Columns" on page 58

Formatting the Column Headers

1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Select Format > Header Format. The Format dialogue appears. 3. The Format dialogue has the following tabs: Font: You can select the Font, Outline (the font style), font Size, Effects, and Text Colour. Colour: You can select the background colour (Interior) of the column headers, by selecting a Foreground colour, a Background colour, and a pattern from the list box. You can also select a 3D Effect for the header. Borders: You can select the Border, the Type, and the Colour for each column header. Alignment: You can select both the Horizontal and Vertical alignment of the column header text.

4. Click OK.

Formatting Table Columns

1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Select Format > Column Format. The Format dialogue appears. 3. The Format dialogue has the following tabs: Font: You can select the Font, Outline (the font style), font Size, Effects, and Text Colour. Colour: You can select the background colour (Interior) of the column headers, by selecting a Foreground colour, a Background colour, and a pattern from the list box. You can also select a 3D Effect for the header. Borders: You can select the Border, the Type, and the Colour for each column header. Alignment: You can select both the Horizontal and Vertical alignment of the column header text.

4. Click OK.

Changing Column Width or Row Height

You can change the column width and row height in a data table. When you change the column width, you change the width only for the selected column. When you change the row height, however, you change the row height for every row in the table. To change the column width: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Click the border separating two column headers and drag to change the column width (see Figure 1.17). To change the row height: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Click the border separating two rows and drag to change the row height (see Figure 1.18).

Figure 1.17: Changing column width

Figure 1.18: Changing row height

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

57

Atoll User Manual

Displaying or Hiding a Column

You can choose which columns in data tables to display or hide. To display or hide a column: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Select Format > Display Columns. The Columns to Be Displayed dialogue appears (see Figure 1.19). 3. To display a column, select its check box. 4. To hide a column, clear its check box.

Tip:

You can also hide a column by right-clicking on its header and selecting Hide Columns from the context menu. You can hide more than one column by pressing CTRL while selecting the columns and then selecting Hide Columns from the context menu.

5. Click Close.

Figure 1.19: The Columns to Be Displayed dialogue Note: You can also right-click the data table and select the Display Columns or Hide Columns command from the context menu.

Freezing or Unfreezing a Column

In Atoll, you can freeze one or more columns of a data table so that they always remain visible as you scroll horizontally through the table. For example, while scrolling through the Sites table, you might want to have the Name column always visible. You can keep this column, or any other column visible, by freezing it. To freeze a column: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Select the header of the column you want to freeze. Click and drag over several headers to select more than one column to freeze. Note: You can only freeze adjacent columns.

3. Right-click the selected header or headers and select Freeze columns from the context men. Note: You can not freeze a column in a report table.

To unfreeze columns: Select Format > Unfreeze columns.

Moving Columns
In Atoll, you can change the column order so that you can group similar columns or present data in a determined order. To move a column: 1. Open the data table as explained in "Opening a Data Table" on page 54. 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.

58

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

Note:

You can only move several columns at the same time when they are adjacent.

3. Click again on the selected column and drag to the desired area. As you drag the column, the position the column will occupy is indicated by a red line (see Figure 1.20).

Figure 1.20: Moving columns

Note:

It may be necessary to click Refresh

in the Map toolbar for your changes to appear.

1.5.6

Copying and Pasting in Tables

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

1.5.6.1

Copying and Pasting a Table Element

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

To create a new element by copying and pasting: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Click in the left margin of the table row containing the element to select the entire row. 3. Select Edit > Copy to copy the table row. 4. Click in the left margin of the table row marked with the New Row icon ( ) to select the entire row.

5. Select Edit > Paste to paste the copied data into the new row. Atoll, creates a new element from the copied data. The name of the new element is the same as that of the copied element, preceded by "Copy of." You can edit this name.

1.5.6.2

Pasting the Same Data into Several Cells

You can paste the same data into several cells, using Fill Up or Fill Down. To paste the same data into several cells: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Click on the cell with the data you wish to copy and drag to select the cells into which you wish to copy the data (see Figure 1.21).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

59

Atoll User Manual

Figure 1.21: Selecting the cells 3. Copy into the selected cells: To copy the contents of the top cell of the selection into the other cells, select Edit > Fill > Down (see Figure 1.22).

Figure 1.22: Copying the contents of the top cell To copy the contents of the bottom cell of the selection into the other cells, select Edit > Fill > Up (see Figure 1.23).

Figure 1.23: Copying the contents of the bottom cell

60

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.5.7

Viewing a Statistical Analysis of Table Contents

You can view a statistical analysis of the contents of an entire column in a table or of the contents of a selection of cells. To view a statistical analysis of table contents: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Select the column data you want to analyse: To view a statistical analysis of an entire column: Click the column title. The entire column is selected.

To view a statistical analysis of a selection of cells in one column: Select the cells you want to analyse. You can select contiguous cells by clicking the first cell and dragging to the last cell of the selection you want to analyse, or by clicking the first cell, pressing SHIFT and clicking the last cell. You can select non-contiguous cells by pressing CTRL and clicking each cell in the column separately.

Tip:

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 69.

3. Right-click the selection of cells. The context menu appears. 4. Select Statistics from the context menu. The Statistics dialogue appears (see Figure 1.24).

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

1.5.8

Exporting Tables to Text Files

You can export entire Atoll data tables, or selected columns, to ASCII text files (in text, TXT, and Comma Separated Value, CSV, formats) and to MS Excel files. To export a table: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Right-click the table. The context menu appears. 3. Select Export from the context menu. The Export dialogue appears. You can see how the exported table will appear in the Preview pane (see Figure 1.25).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

61

Atoll User Manual

Figure 1.25: Exporting a data table 4. Select the Header check box if you want to export the names of the columns with the data. 5. Select a Decimal Symbol from the list. 6. Select a Field Separator from the list. 7. Select the fields (displayed as columns in the table) you want to export. You can display all the fields belonging to a table by clicking the Expand button ( ) to the left of the table name. You can select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking each fields separately. a. To select a field to be exported, select the field in the Available Fields box and click to the Exported Fields list. All fields in the Exported Fields list will be exported. to move it

b. To remove a field from the list of Exported Fields, select the field in the Exported Fields list and click to remove it. c. To change the order of the fields, select a field and click or to move it up or down in the list. The fields at the top of the Exported Fields appear at the left of the exported table. Note: You can save the choices you have made in the Export dialogue as a configuration file by clicking the Save button at the top of the dialogue and entering a name for the file in the Save As dialogue that appears. The next time you export a data table, you can click Load in the Export dialogue to open your configuration file with the same settings you used this time.

8. Click Export. The Save As dialogue appears. 9. In the Save As dialogue, enter the File name and select the format from the Save as type list. 10. Click Save to export the table. You can also export the Sites and Transmitters tables to text files by selecting the corresponding folder or subfolder in the Explorer window and pressing CTRL+E. Table export using the keyboard shortcut works in the same manner as explained above, except that all the fields of the table are exported, alongwith the Header, using the Field Separator and Decimal Symbol defined in the Regional Options of the computer. For information on importing data into a data table, see "Importing Tables from Text Files" on page 63.

62

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.5.9

Importing Tables from Text Files

You can import data in the form of ASCII text files (in TXT and CSV formats) into Atoll data tables. To import a table: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Right-click the table. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the ASCII text file you want to open and click Open. The Import dialogue appears (see Figure 1.26).

Figure 1.26: Importing information into a data table 5. Enter the number of the first line of data in the 1st Data Line box. 6. Select a Decimal Symbol from the list. 7. Select a Field Separator from the list. 8. Select the Update Records check box if you want to replace the data of records already existing in the table. Note: Atoll compares the values in the left-most column of the data to be imported with the values in the same column of the data table to see if records already exist. The values of these records are replaced when the Update Records check box is selected. If the Update Records check box is not selected, these records are not imported.

9. Under Field Mapping, there are two header rows: Source: The column headers from the text file you are importing. Destination: The column headers from the Atoll data table.

Align the content of the source file with the content of the destination file by clicking the column header in the Destination row and selecting the corresponding column from the Atoll data file (see Figure 1.26). Select <Ignore> for source file columns that you do not want to import.

Tip:

You can change the width of the columns to make the contents easier to work with. See "Changing Column Width or Row Height" on page 57. You can save the choices you have made in the Import dialogue as a configuration file by clicking the Save button at the top of the dialogue and entering a name for the file in the Save As dialogue that appears. The next time you export a data table, you can click Load in the Import dialogue to open your configuration file with the same settings you used this time.

Note:

10. Click Import. The contents are imported in the current Atoll data table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

63

Atoll User Manual You can also import the Sites and Transmitters tables from text files by selecting the corresponding folder or subfolder in the Explorer window and pressing CTRL+I. For information on exporting the information in a data table into a text file, see "Exporting Tables to Text Files" on page 61.

1.5.10

Exporting Tables to XML Files

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

1.5.11

Importing Tables from XML Files

You can import data tables into your Atoll document from XML files. You can use XML to exchange information between Atoll and the OMC. In order for Atoll to be able to correctly import the data tables from XML files, the XML files and the current Atoll document must use the same system (GSM, UMTS, etc.), the technology (TDMA, CDMA, TD-SCDMA, etc.), and the Atoll version used to create the XML files must be the same as the version used to import the data. For more information about the formats of the XML files, see the Technical Reference Guide. To import data tables into your document from XML files: 1. Select File > Data Exchange > XML File Import. The Browse for Folder dialogue appears. 2. Select the folder where the index.xml file is located. 3. Click OK. The data tables from the XML files listed in the index.xml file are imported in the document . Note: Tables are imported in the same order they appear in the index.xml file. Do not modify the order of tables in the index.xml file because the order in which the data is imported is very important; some data must be imported before other data. For example, antennas used by transmitters must be imported before the transmitters themselves.

During the import procedure, existing data in the tables are overwritten by the data from the XML files. Once the import is complete, Atoll performs a database integrity check, and a duplicate records check to ensure that the import did not create database problems. For information on exporting the data tables in your document to XML files, see "Exporting Tables to XML Files" on page 64.

1.6

Printing in Atoll
In Atoll, you can print any part of your document, including maps, data tables, document reports, and antenna patterns. This section explains the following: "Printing Data Tables and Reports" on page 64 "Printing a Map" on page 65 "Printing a Docking Window" on page 68 "Printing Antenna Patterns" on page 68.

1.6.1

Printing Data Tables and Reports

Data tables and reports are both presented in tabular format in Atoll and can, therefore, both be printed in the same way. If you wish to see how the table will appear once printed, see "Previewing Your Printing" on page 68. To print a table: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. If you want to print an area of the table, select it by clicking in one corner of the area and dragging diagonally to the opposite corner.

64

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment 3. Select File > Print. 4. If you want to print only a selected area, choose Selected in the Print dialogue. 5. Click OK to print.

1.6.2

Printing a Map
You can print a map in Atoll and create a paper copy of studies, predictions, etc. Atoll offers several options allowing you to customise and optimise the printed map. Atoll supports printing to a variety of paper sizes, including A4 and A0. Before you print a map, you have the following options: You can print the entire map, or you can define an area of the map to be printed in one of the following ways: Selecting the print area (see "Defining the Printing Zone" on page 65). Creating a focus zone (see "Drawing a Focus Zone or Hot Spot Zones" on page 43).

You can accept the default layout or you can modify the print layout (see "Defining the Print Layout" on page 66). You can see how the map will appear once printed (see "Previewing Your Printing" on page 68). Important: Printing graphics is a memory-intensive operation and can make heavy demands on your printer. Before printing for the first time, you should review the "Printing Recommendations" on page 65 to avoid any memory-related problems.

To print a map: 1. Select the document window containing the map. 2. You now have the following options before printing the map: You can select a print area ("Defining the Printing Zone" on page 65) or create a focus zone ("Drawing a Focus Zone or Hot Spot Zones" on page 43). You can modify the print layout ("Defining the Print Layout" on page 66). You can see how the map will appear once printed (see "Previewing Your Printing" on page 68).

3. Select File > Print. 4. Click OK.

1.6.2.1

Printing Recommendations
The appearance of the map is determined by the arrangement and properties of the objects the map contains. Objects in Atoll are arranged in layers. The layers on the top (as arranged on the Data and Geo tabs) are the most visible on the screen and in print. The visibility of the lower layers depends on which layers are above it and on the transparency of these layers (for information on transparency, see "Defining the Transparency of Objects and Object Types" on page 35). Before printing a map, it is recommended to organise the layers from top to bottom as follows, when a document contains surface layers (raster maps or polygonal vector maps), lines (vectors such as roads, or airport), and points (measurements, etc.): Points (vectors) Roads and Lines (vectors) Surface polygons (vectors) Multi-format maps - population, geoclimatic, traffic maps (vector or raster), and others Clutter class maps (transparent raster maps) Images, DTM, or clutter height maps (non-transparent maps).

Sites and transmitters must be above all the other layers. For this reason, visible objects on the Data tab, for example, sites, transmitters, and predictions, are displayed above objects on the Geo tab. For performance reasons, however, it is strongly recommended to put vector layers, such as roads, over predictions. This will ensure that these vector layers are visible when you print the map. To put vector layers from the Geo tab over predictions: 1. In the Explorer window, click the Geo tab. 2. Right-click the vector layer you wish to move to the Data tab. The context menu appears. 3. Select Transfer to Data from the context menu. 4. Click the Data tab. 5. Drag the vector layer to a position above Predictions but below Sites, Antennas, and Transmitters.

1.6.2.2

Defining the Printing Zone

You can define an area to be printed. To create a printing zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Printing Zone folder. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

65

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

Figure 1.27: Printing zone You can also create a printing zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the printing zone. Existing polygon: You can use any existing polygon on the map as a printing zone by right-clicking it and selecting Use as > Printing Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, you can import it and use it as a printing zone. You can import it by right-clicking the Printing Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a printing zone the size of the map window by selecting Fit to Map Window from the context menu.

Once you have created a printing zone, you can change its size by dragging the edges of the zone displayed on the rulers of the map window. You can also use Atolls polygon editing tools to edit the printing zone. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44. Note: You can export the printing zone as a polygon, so that you can use it in a different Atoll document, by right-clicking the Printing Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

1.6.2.3

Defining the Print Layout

You can use the Print Setup dialogue to define how your map will appear when you print it. On the Print Setup dialogue, you can: Set the scale of the map. Choose to print the rulers with the map. Choose to print the area outside the focus zone. Choose to print the legend. Add a title, comment, logo, header, or footer. Select paper size and source, as well as the page orientation and the margins.

These settings can be saved as a configuration, allowing you to define a standard appearance which you can then import the next time you print a similar document.

66

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment To define the appearance of the map when it is printed: 1. Select File > Print Setup. The Print Setup dialogue appears. You define the print set up on the Page tab, the Components tab, and the Header/Footer tab. You can see any changes you make in the schematic preview on the right side of the Print Setup dialogue. Note: If you have previously defined a configuration file containing all the necessary settings, you can click the Import button under Configuration to import those settings.

2. Click the Page tab. On the Page tab, you can define the page size, margins, and orientation and the scale of the printed map: a. Under Orientation, select whether the page should be printed in Portrait or Landscape. b. Under Paper, select the Size of the paper and, optionally, the Source of the paper. c. Under Scaling, define the scale of the printed image either by selecting Fit to page, or by selecting Scale and defining the scale. d. Under Margins, set the margins of the page in millimetres. 3. Click the Components tab. a. Under Map, you can define the appearance of the printed map: Select the Rulers check box if you want to print the map with a scale around it. Select the Area inside focus zone only check box if you only want to print the part of the map inside the focus zone.

b. Under Legend, you can define the placement of the legend. Select the Legend check box if you want to print a legend with the map. Click a button to set the Position of the legend. The buttons inside the square will place the legend on top of the map. The buttons outside of the square will place the legend outside of the map.

Click a Font button to open the Font dialogue to define the font of the legend.

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

iv. Select the correct Width and Height (in pixels). v. Click OK. c. Select the Header/Footer check box if you want to define a header or footer for the map and set its Position. Clicking the Properties button opens a dialogue where you can enter text and set variables such as the current time and date. If you want the header or footer to appear on the map (and not outside of it), select the On the map check box. 5. Once you have made your settings, click OK to close the Print Setup dialogue, or click Print to print the document.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

67

Atoll User Manual

Note:

You can save the current settings as a configuration file by clicking the Export button under Configuration. This enables you to re-use the same settings the next time by importing them.

1.6.3

Previewing Your Printing

When you want to print maps, data tables, or reports, you can preview your printing. To preview your printing: 1. Select the map or table you want to print. 2. Select File > Print Preview. The Print Preview window appears. At the top of the Print Preview window, you can click one of the following buttons: Click Print to open the Print dialogue. Click Zoom In to zoom in on the print preview. Click Zoom Out to zoom out on the print preview. Click Next Page to display the following page Click Prev Page to display the previous page. Click Two Page to display two pages side by side Click One Page to display a single page.

1.6.4

Printing a Docking Window

You can print the content of many docking windows using the context menu; selecting File > Print only prints the contents of a document window, as explained in "Printing a Map" on page 65. The docking windows whose contents you can print are: Legend Window (for more information on this tool, see "Adding an Object Type to the Legend" on page 36) 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

To print the content of a docking window: 1. Open the docking window you want to print. If you want to print a Point Analysis window, click the tab of the study you want to print.

2. Right-click the window you wish to print. 3. Select Print from the context menu. The Print dialogue appears. 4. Click OK to print.

1.6.5

Printing Antenna Patterns

You can print the horizontal or vertical pattern of an antenna. To print an antenna pattern: 1. Click the Data tab of the Explorer window. 2. Open the Antennas table: To open the RF Antennas table: i. Right-click the Antennas folder.

ii. Select Open Table from the context menu. To open the microwave Antennas table: i. Click the Expand button ( ) to the left of the Microwave Radio Links folder.

ii. Right-click the Links folder and select Antennas > Open Table from the context menu. 3. Right-click the antenna whose pattern you want to print. 4. Select Record Properties from the context menu. The Properties dialogue appears. 5. Select the Horizontal Pattern tab or the Vertical Pattern tab. 6. Right-click the antenna pattern and select Linear or Logarithmic from the context menu. 7. Right-click the antenna pattern and select Print from the context menu.

68

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.7

Grouping, Sorting, and Filtering Data

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

1.7.1

Grouping Data Objects

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

For examples of grouping data objects, see "Examples of Grouping" on page 71.

1.7.1.1

Grouping Data Objects by a Selected Property

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

To undo the grouping: 1. Click the Data tab in the Explorer window. 2. Right-click the folder or subfolder whose objects you have grouped. 3. From the context menu, select from the Group By > None. See "Examples of Grouping" on page 71.

1.7.1.2

Configuring the Group By Submenu

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

69

Atoll User Manual

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

7. Click OK to close the Configuration dialogue and click OK to close the Properties dialogue. The Group By submenu will now contain only the fields you selected.

1.7.1.3

Advanced Grouping
You can group data objects by one or more properties, using the Group By button on the Properties dialogue. To group data objects by one or more properties: 1. Click the Data tab in the Explorer window. 2. Right-click the folder or subfolder whose objects you have grouped. 3. Select Properties from the context menu. 4. Select the General tab of the Properties dialogue. 5. Click the Group By button. The Group dialogue appears (see Figure 1.29).

Figure 1.29: The Group dialogue 6. Select the fields by which you want to group the objects. You can select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking each fields separately. To select a field to be used to group the objects, select the field in the Available Fields list and click to move it to the Group these fields in this order list. To remove a field from the list of Group these fields in this order, select the field in the Group these fields in this order list and click to remove it.

70

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

To change the order of the fields, select a field and click or to move it up or down in the list. The objects will be grouped in the order of the fields in the Group these fields in this order list, from top to bottom.

7. Click OK to close the Group dialogue and click OK to close the Properties dialogue and group the objects. To undo the grouping: 1. Click the Data tab in the Explorer window. 2. Right-click the folder or subfolder whose objects you have grouped. 3. From the context menu, select from the Group By > None.

1.7.1.4

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

Figure 1.30: Grouping transmitters by site The result of grouping can be seen in Figure 1.31.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

71

Atoll User Manual

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

Figure 1.32: Grouping transmitters by zone The result of grouping can be seen in Figure 1.31. The transmitters are now in two groups: those inside the focus zone and those outside the focus zone.

Figure 1.33: Transmitters grouped by site

72

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.7.2

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

1.7.2.1

Sorting Data in Tables

When sorting data in tables, you can sort by one column or by several columns.

Sorting by One Column

To sort data in a table by one column: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Select the header of the column that you want to sort on. The entire column is selected. 3. Right-click the column header. The context menu appears. 4. From the context menu, select how you wish to sort: Sort Ascending: sort the data table records from the lowest value in the reference column to the highest value. Sort Descending: sort the data table records from the highest value in the reference column to the lowest value.

Sorting by Several Columns

You can only sort in a table by adjacent columns. If you want to sort by columns that are not adjacent, you can move the columns first as explained in "Moving Columns" on page 58.

Tip:

If you want to sort data by several columns without moving the columns, you can use the Sort function on the Properties dialogue. For information, see "Advanced Sorting" on page 73.

To sort data in a table by several columns: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Click the header of the first column and drag over the adjacent columns that will be your sort references. The entire column is selected. 3. Right-click the column headers. The context menu appears. 4. From the context menu, select how you wish to sort: Sort Ascending: sort the data table records from the lowest value in the first reference column to the highest value. Sort Descending: sort the data table records from the highest value in the first reference column to the lowest value.

1.7.2.2

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

73

Atoll User Manual 7. For each other column you want to sort on: a. Select the column name from the And by list. b. Choose whether you want to sort in ascending or descending order. 8. Click OK.

Figure 1.34: The Sort dialogue

1.7.3

Filtering Data
In Atoll, you can filter data according to one or several criteria. You can filter data to be able to work with a subset of data, or to facilitate working with large documents by reducing the amount of records displayed. The filtered data objects are the data objects that remain after you have applied your filter criteria. You can save the filtering parameters as a folder configuration. For information, see "Folder Configurations" on page 82. This section explains the following: "Filtering in Data Tables by Selection" on page 74 "Advanced Data Filtering" on page 75 "Restoring All Records" on page 76 "Advanced Filtering: Examples" on page 76.

1.7.3.1

Filtering in Data Tables by Selection

You can filter a data table by selecting one or more values. Once you have selected one or more values, you can choose to view only records that have the same value or only records that do not have that value. To filter a data table on one or more fields: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Select the value to filter on. To select more than one value, press CTRL as you click the other values. 3. Select one of the following from the Records menu: Filter by Selection: All records with the selected value or values are displayed. You can now modify these records or make calculations on them as you would normally do with the entire data table (see Figure 1.35 on page 74). Filter Excluding Selection: All records without the selected value or values are displayed. You can now modify these records or make calculations on them as you would normally do with the entire data table (see Figure 1.36 on page 75).

Figure 1.35: Filtering by selection (Antenna AO9209)

74

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

Figure 1.36: Filtering excluding selection (Antenna AO9209)

1.7.3.2

Advanced Data Filtering

You can use advanced data filtering to combine several criteria in different fields to create complex filters. To create an advanced filter: 1. Open the data table as explained in "Opening a Data Table" on page 54. 2. Select Records > Advanced Filter. The Filter dialogue appears.

Tip:

You can also access the Filter dialogue by clicking the Filter button of the Properties dialogue.

3. Click the Filter tab: a. Select a Field from the list. b. Under Values to Include, you will find all the values represented in the selected field. Select the check boxes next to the values you want to include in the filter. Click Clear All to clear all check boxes. Note: Making selections on the Filter tab of the Filter dialogue is the equivalent of filtering by selection as explained in "Filtering in Data Tables by Selection" on page 74.

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

Figure 1.37: The Filter dialogue - Advanced tab b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table:

Formula
=X <> X <X

Data are kept in the table only if

value equal to X (X may be a number or characters) value not equal to X (X may be a number or characters) numerical value is less than X

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

75

Atoll User Manual

Formula
>X <=X >=X *X* *X X*

Data are kept in the table only if

numerical value is greater than X numerical value is less than or equal to X numerical value is greater than or equal to X text objects which contain X text objects which end with X text objects which start with X

5. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. See "Advanced Filtering: Examples" on page 76.

1.7.3.3

Restoring All Records

After you have applied filter criteria to records, you may want to cancel the filter criteria and display all the records again. To restore all records: Select Records > Remove Filter.

1.7.3.4

Advanced Filtering: Examples

In this section, you will find a few examples of advanced filtering: "Advanced Filtering: Example 1" on page 76 "Advanced Filtering: Example 2" on page 77 "Advanced Filtering: Example 3" on page 77.

1.7.3.4.1

Advanced Filtering: Example 1

In this example, there is an Atoll document with antennas from two manufacturers and with different characteristics.

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

The combination of these criteria is all antennas from manufacturers with a name beginning with "K" and with a beamwidth under 100 but over 50. The result of this advanced filter can be seen in the second pane of Figure 1.39.

76

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

Figure 1.39: Advanced filtering

1.7.3.4.2

Advanced Filtering: Example 2

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

The result of this advanced filter can be seen in the second pane of Figure 1.39.

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

1.7.3.4.3

Advanced Filtering: Example 3

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

The result of this advanced filter can be seen in the second pane of Figure 1.39.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

77

Atoll User Manual

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

1.7.4

User Configurations
In Atoll, you can export many types of settings you have made in a user configuration and then import the settings in another document. If you are working in a multiple-user environment with a central database, the information stored in a user configuration, such as geographic data or automatic neighbour allocation parameters, is not stored in the database. You can create a user configuration file, however, to ensure that all users in a large radio-planning project use the same settings. The file extension of the user configuration file is CFG. If only the geographic data set or computation and focus zones are being exported in the user configuration file, Atoll gives the file the extension "GEO." Because the file is in XML (eXtensible Markup Language), you can open and edit it with any XML-capable text editor. When you create a user configuration file, you can export the following information: Geographic data set: The complete path of imported geographic maps, map display settings (such as, the visibility scale, transparency, tips text, etc.), clutter description (code, name, height, standard deviations, indoor loss, orthogonality factor, the percentage of pilot finger of each clutter class, default standard deviations, and indoor loss) and raster or user profile traffic map description. Vector maps must have the same coordinate system as the raster maps. Important: If you export the geographic data set in a user configuration file, the coordinate system of any vector geographic data must be the same as that of the raster geographic data. Computation and Focus Zones: The computation and focus zone in the current document. Folder configurations: Sorting, grouping and filtering settings (those saved by the user and the current settings, even if not saved), the filtering zone, and the display settings of radio data folders (including measurement display settings). Automatic Neighbour Allocation Parameters: The input parameters of the automatic neighbour allocation. Automatic Scrambling Code Allocation Parameters: The parameters of the automatic scrambling code allocation (this option applies to UMTS documents only). Prediction List: The general information (name, comments, group, and sorting and filtering settings), prediction coverage conditions, and display settings of coverage predictions that have been created. AFP Configuration: Calculation options selected when starting an AFP session as well as calculation parameters used for interference histograms (this option applies to GSM documents only). Automatic PN Offset Allocation Parameters: The parameters of the automatic PN offset allocation. (this option applies to CDMA2000 documents only). Macros: The complete path of any macros. Because a macro is linked to an Atoll session, and not to a specific Atoll document, you can export the macros in a user configuration even if you do not have an Atoll document open.

For a detailed description of the user configuration file, see the Administrator Manual. In this section, the following are explained: "Exporting a User Configuration" on page 79 "Importing a User Configuration" on page 79.

78

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.7.4.1

Exporting a User Configuration

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

Figure 1.42: Exporting a user configuration 2. Select the check boxes of the information you want to export as part of the user configuration. 3. Click OK. The Save As dialogue appears. 4. Enter a File name for the user configuration file and click Save. The folder configuration has been saved.

1.7.4.2

Importing a User Configuration

You can import a user configuration that you or another user has created, as explained in "Exporting a User Configuration" on page 79, it into your current Atoll document. To import a user configuration: 1. Select Tools > User Configuration > Import. The Open dialogue appears. 2. Select the user configuration file with the data you want to import. 3. Click Open. The User Configuration dialogue appears (see Figure 1.43).

Figure 1.43: Importing a user configuration 4. Select the check boxes of the information you want to import. 5. Click OK. The user configuration is imported.

1.7.5

Site and Transmitter Lists

In Atoll, you can create lists of sites and transmitters. Once you have created a site or transmitter list, you can modify the list and use it to filter data to be able to work with a subset of data, or to facilitate working with large documents by reducing the amount of records displayed.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

79

Atoll User Manual In a multi-user environment, site lists can be stored in the database. When you open a document from a database, you can select the sites to load according to any defined site lists. In a large radio-planning project, this allows you to more effectively manage your resources by reducing the unnecessary data you retrieve from the database. In this section, the following are explained: "Creating a Site or Transmitter List" on page 80 "Adding a Site or Transmitter to a List from the Explorer Window" on page 80 "Adding a Site or Transmitter to a List from the Map Window" on page 80 "Adding Sites or Transmitters to a List Using a Zone" on page 81 "Editing a Site or Transmitter List" on page 81 "Filtering on a Site or Transmitter List" on page 81.

1.7.5.1

Creating a Site or Transmitter List

You can create lists of sites or transmitters that you can then use to filter the data displayed. To create a site or transmitter list: 1. Click the Data tab in the Explorer window. 2. Right-click the folder where you want to create the list: Site list: if you want to create a site list: a. Right-click the Sites folder. The context menu appears. b. Select Site Lists > Open Table from the context menu. The Site Lists table appears. Transmitter list: if you want to create a transmitter list: a. Right-click the Transmitters folder. The context menu appears. b. Select Transmitter Lists > Open Table from the context menu. The Transmitter Lists table appears. 3. Enter the name of the new list in the row marked with the New Row icon ( ).

1.7.5.2

Adding a Site or Transmitter to a List from the Explorer Window

You can add a site or transmitter to a list by selecting it from the Explorer window. To add a site or transmitter to a list: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to the left of Sites or Transmitters folder to expand the folder.

3. Right-click the site or transmitter you want to add to the list. The context menu appears. Site list: if you want to add a site to a list: Select Add Site to a List from the context menu. A dialogue appears.

Transmitter list: if you want to add a transmitter to a list. Select Add Transmitter to a List from the context menu. A dialogue appears.

4. Select the name of the list from the dialogue.

Tip:

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

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

Tip:

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

1.7.5.3

Adding a Site or Transmitter to a List from the Map Window

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

Transmitter list: if you want to add a transmitter to a list. Select Add Transmitter to a List from the context menu. A dialogue appears.

80

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment 2. Select the name of the list from the dialogue.

Tip:

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

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

1.7.5.4

Adding Sites or Transmitters to a List Using a Zone

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

3. Select the name of the list from the dialogue.

Tip:

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

4. Click OK. The sites or transmitters contained in the zone are added to the selected list.

1.7.5.5

Editing a Site or Transmitter List

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

To delete a site or transmitter from the list: a. Click in the left margin of the row containing the site or transmitter to select it. b. Press DEL to delete the site or transmitter from the list. 5. Click OK when you have finished editing the site or transmitter list.

1.7.5.6

Filtering on a Site or Transmitter List

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

6. Select the check box of the list or lists that you want to display.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

81

Atoll User Manual 7. Click OK to close the Filter dialogue. 8. Click OK to close the Properties dialogue. Only sites or transmitters that belong to the selected list are now displayed in the Data tab of the Explorer window and in the map window.

1.7.6

Folder Configurations
In Atoll, the parameters defining how data contained in a folder are grouped, sorted, or filtered are referred to as a folder configuration. You can define folder configurations and save them, allowing you to consistently apply the same grouping, filtering, or sorting criteria. In this section, the following are explained: "Creating a Folder Configuration" on page 82 "Applying a Saved Folder Configuration" on page 82 "Reapplying the Current Folder Configuration" on page 82 "Exporting a Folder Configuration" on page 83 "Importing a Folder Configuration" on page 83 "Deleting a Folder Configuration" on page 83. Note: For transmitters, there is a default folder configuration called Same as Sites Folder. You can apply this configuration to arrange the transmitters in the Transmitters folder with the same parameters as those defined for sites.

1.7.6.1

Creating a Folder Configuration

In Atoll, you can save the parameters defining how data contained in a folder are grouped, filtered, or sorted as a folder configuration. To create a configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the folder whose settings you want to save. 3. Select Properties from the context menu. 4. Select the General tab in the Properties dialogue. 5. If you have not yet done so, set the following parameters as desired: Group By (see "Grouping Data Objects" on page 69) Sort (see "Sorting Data" on page 73) Filter (see "Filtering Data" on page 74).

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

1.7.6.2

Applying a Saved Folder Configuration

You can apply a configuration that has been created and saved for the present folder. To apply a saved folder configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the folder to which you want to apply a configuration. The context menu appears. 3. On the Configurations submenu, select the name of the configuration you want to apply. The folder configuration is applied to the current folder.

1.7.6.3

Reapplying the Current Folder Configuration

If you have grouped, filtered, or sorted a data folder, you have created and applied a folder configuration. If you then add or modify data, the properties of these may not match the folder configuration you previously made on the data folder. In this case, you can reapply the same filter or sort settings to the new or modified data. To reapply the folder configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the folder whose folder configuration you want to reapply. 3. Select Apply Current Configuration from the context menu. The previously configured folder configuration is reapplied to the data.

82

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.7.6.4

Exporting a Folder Configuration

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

1.7.6.5

Importing a Folder Configuration

Once you have exported a folder configuration as explained in "Exporting a Folder Configuration" on page 83, you can import it into your current document. To import a folder configuration: 1. Select Tools > User Configuration > Import. The Open dialogue appears. 2. Select the CFG file with the folder configuration you want to import. 3. Click Open. The User Configuration dialogue appears (see Figure 1.43 on page 79). 4. Select the Folder Configuration check box. If you want to import other configurations at the same time, select those check boxes as well. 5. Click OK. The folder configuration is imported.

1.7.6.6

Deleting a Folder Configuration

You can delete a folder configuration from the Atoll document when you no longer need it. To delete a folder configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the folder with the folder configuration you want to delete. 3. Select Properties from the context menu. 4. Select the General tab in the Properties dialogue. 5. Under Configuration, select the name of the configuration from the list. 6. Click Delete. The folder configuration is deleted. Caution: When you delete a folder configuration, Atoll will not ask for confirmation; it is deleted immediately.

1.7.7

Creating and Comparing Subfolders

You can compare the effects of different grouping, sorting, or filtering settings by creating subfolders of object folders in the Data tab and applying different settings to each subfolder. Each subfolder contains a copy of the data in the object folder in which it was created. To create a subfolder of a folder: 1. In the Data tab of the Explorer window, right-click the folder you want to create a subfolder of. 2. Select Create a Subfolder from the context menu. A subfolder is created containing a copy of the original folder content. You can now perform the following actions on the subfolder: Grouping (see "Grouping Data Objects" on page 69) Sorting (see "Sorting Data" on page 73) Filtering (see "Filtering Data" on page 74).

Tip:

If you have created several subfolders, you can rename each one to give it a more descriptive name. For information on renaming an object, see "Renaming an Object" on page 29.

Once you have performed the actions on each subfolder, you can compare the differences, by displaying in turn each subfolder, with its grouping, sorting, or filtering settings, on the map. For more information on display properties, see "Display Properties of Objects" on page 32.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

83

Atoll User Manual To compare subfolders: 1. In the Data tab of the Explorer window, clear the check boxes to the left of each subfolder. The data objects are not displayed on the map. 2. Select the check box of one of the subfolders, leaving the check boxes of the other subfolders cleared. The data objects of the selected subfolder, 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 subfolder. How the objects are displayed on the map will change, depending on the different grouping, sorting, or filtering settings of the selected subfolder. You can remove subfolders by deleting them. When you delete a subfolder, the data contained are not deleted. When you delete the last subfolder, the data reappear under the initial folder. To delete a subfolder: Right-click the subfolder to be deleted and select Delete from the context menu.

Tip:

If, after deleting the last subfolder, the data do not reappear under the initial folder, you can refresh the display by right-clicking the folder and selecting Group By > None from the context menu.

1.7.8

Filtering Data Using a Filtering Zone

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

For more information on creating and editing a filtering zone, see "Using a Filtering Zone" on page 41.

1.8

Tips and Tricks

In this section, you will learn a few shortcuts and tricks to help you work more efficiently with Atoll: "Undoing and Redoing" on page 84 "Refreshing Maps and Folders" on page 85 "Searching for Objects on the Map" on page 85 "Using the Status Bar to Get Information" on page 86 "Saving Information Displayed in the Event Viewer" on page 86 "Using Icons from the Toolbar" on page 86 "Using Shortcuts in Atoll" on page 88.

1.8.1

Undoing and Redoing

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

To undo an action: Select Edit > Undo.

To redo an action that you have undone: Select Edit > Redo.

84

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment

1.8.2

Refreshing Maps and Folders

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

1.8.3

Searching for Objects on the Map

Atoll provides several tools for finding data objects on the map. You can search for some objects (sites, transmitters, repeaters, or links) by their name, using the Find toolbar. By using the Location Finder, you can search for a site, a transmitter, a repeater, or a vector by any text field. You can also use the Location Finder to search for a point on the map by its x and y coordinates. This section explains: "Searching for a Map Object by Its Name" on page 85 "Searching for a Map Object using Any Text Property" on page 85 "Searching for a Point on the Map" on page 86.

1.8.3.1

Searching for a Map Object by Its Name

You can use the Find toolbar to search for the following map objects by name: sites transmitters repeaters

To search for a map object by name using the Find toolbar: 1. Select View > Find Toolbar to display the Find toolbar. Note: You can change the Find toolbar to a floating window by double-clicking it.

2. From the Find list, choose the map object you are searching for: Site Transmitter Repeater

3. Enter the name of the object in the Named box. You can use an asterisk ("*")as a wild card in the following ways: *X* X* *X names which contain X names which start with X names which end with X

4. Press ENTER. Atoll selects the object and centres it in the map window. Note: You can also search for a map object by its name by using the Location Finder. For information, see "Searching for a Map Object using Any Text Property" on page 85.

1.8.3.2

Searching for a Map Object using Any Text Property

You can use the Location Finder to search for the following map object using any text (i.e., non-numeric) property: sites transmitters repeaters vectors.

To search for a map object by a text property using the Location Finder: 1. Click the Location Finder button ( ) on the toolbar. The Location Finder dialogue appears.

2. From the Find list, choose the map object you are searching for: Site Transmitter Repeater Vector

3. If you wish to search all the sites in the search, including sites that are presently filtered out, select the Include all the sites in the search (filtered or not) check box. 4. Under Criteria, select a Field to be searched and enter the value of the field. You can use an asterisk as a wild card in the following ways: Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

85

Atoll User Manual *X* X* text objects which contain X text objects which start with X

5. Click OK. Atoll selects the site and centres it in the map window.

1.8.3.3

Searching for a Point on the Map

You can search for a point by entering its x and y coordinates in the Location Finder. To search on the map for a point using the Location Finder: 1. Click the Location Finder button ( 2. From the Find list, choose Point. 3. Enter the x and y coordinates of the point, using the same units as defined under Display on the Coordinates tab of the Options dialogue (see "Projection and Display Coordinate Systems" on page 96). 4. Click OK. Atoll marks the point ( ) and centres it in the map window. ) on the toolbar. The Location Finder dialogue appears.

Note:

To remove the point icon (

), select it and then select Delete from the context menu.

1.8.4

Using the Status Bar to Get Information

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

X-Y coordinates

Altitude (from DTM)

Clutter class

Figure 1.44: Information displayed in the status bar

1.8.5

Saving Information Displayed in the Event Viewer

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

1.8.6

Using Icons from the Toolbar

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

86

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment Open the Open dialogue (CTRL+O) Save the current document (CTRL+S) Cut the selected data (CTRL+X) Copy the selected data (CTRL+C) Paste the content of the clipboard (CTRL+V) Undo the last modification (CTRL + Z) Redo the previous undone modification (CTRL + Y) Print the current window (table or map) (CTRL+P) Preview the current window before printing (table or map) (CTRL+P) Open the About Atoll dialogue In the Radio toolbar Create a new station based on the currently selected model Create a new group of hexagons based on the currently selected station template ( gon radius is defined) Note: indicates that no hexa-

A new hexagon group is created in the Hexagonal Design folder if the check box to the left of this folder is selected when you create a new station or a group of stations. If the check box is not selected, you can create a new station without creating a corresponding hexagon group.

Station model currently selected Create a new repeater or remote antenna for the currently selected transmitter Graphically manage neighbours for the selected transmitter Open the Point Analysis window Calculate only invalid matrices, unlocked coverages, and pending simulations (F7) Force the calculation of all matrices, unlocked coverages, and pending simulations (CTRL+F7) Stop the calculation of all matrices, unlocked coverages, and pending simulations (ESC) In the Map toolbar Select area Refresh display of map and folders (F5) Disable zooming and panning tools. Move the map window (CTRL+D) Map scale currently used Previous/Next view (zoom and location) Zoom in on the map and centre on the cursor location (CTRL+A) and zoom out on the map and centre on the cursor location (CTRL+R) Define a zoom area on the map (CTRL+W) Turn on tool tips Measure distances on the map

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

87

Atoll User Manual Location finder Display a point-to-point profile In the Search toolbar Centre site in the map window. In the Vector Edition toolbar Create a new vector layer (in either the Geo or the Data tab) Select the vector layer to edit Draw a new polygon Draw a new rectangle Draw a new line Draw points Merge several vector polygons Cut out areas in polygons Create new polygon from overlapping areas Split one polygon along the drawn lines. Note: When you place the cursor over an icon, a tool tip appears, giving a short description.

1.8.7

Using Shortcuts in Atoll

Atoll provides many shortcuts that enable you to access commonly used tools and commands more quickly. The shortcuts available are listed below (some of the same commands can be accessed using a toolbar icon; see "Using Icons from the Toolbar" on page 86): Using the CTRL key: CTRL++: Zoom in on the map (in the toolbar, click CTRL+: Zoom out on the map (in the toolbar, click CTRL+A: Select all records in a table CTRL+C: Copy the selected data (in the toolbar, click CTRL+D: In tables: Copy the first cell of a selection down into all selected cells In the map window: Move the map window (in the toolbar, click ) ) and click the map) and right-click the map)

CTRL+E: Export the table of the selected Sites or Transmitters folder or subfolder to a text file. This table exports works in the same manner as the table export explained in "Exporting Tables to Text Files" on page 61, except that all the fields of the table are exported, alongwith the Header, using the Field Separator and Decimal Symbol defined in the Regional Options of the computer. CTRL+F: Open the Find dialogue in a table CTRL+I: Import the table of the selected Sites or Transmitters folder or subfolder from a text file. This table import works in the same manner as the table import explained in "Importing Tables from Text Files" on page 63. CTRL+N: Open the Project Templates dialogue (in the toolbar, click CTRL+SHIFT+N: Create a new document from an existing database CTRL+O: Open the Open dialogue (in the toolbar, click CTRL+P: Print the current window (in the toolbar, click CTRL+Q: Select Zoom In/Out tool (in the toolbar, click ) ) ) )

88

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 1: The Working Environment CTRL+S: Save the current active document (in the toolbar, click CTRL+U: Copy the last cell of a selection up into all selected cells CTRL+V: Paste the content of the clipboard (in the toolbar, click CTRL+W: Define a zoom area on the map (in the toolbar, click CTRL+X: Cut the selected data (in the toolbar, click ) ) ) ) )

CTRL+Y: Redo the previous undone modification (in the toolbar, click CTRL+Z: Undo the last modification (in the toolbar, click )

Using the ALT key: ALT+ ALT+

: Previous zoom and location on the map (in the toolbar, click : Next zoom and location on the map (in the toolbar, click
)

ALT+F8: Open the Add-ins and Macros dialogue F3: Select the Find Site tool. F5: Refresh display of map and folders (toolbar: select ) )

Using the Function Keys -

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 )

Tip:

Menus and commands can be also accessed by pressing the ALT key and typing the underlined letter in the menu or command name.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

89

Atoll User Manual

90

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2
Starting an Atoll Project

RF Planning & Optimisation Software

Atoll

Atoll User Manual

92

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2: Starting an Atoll Project

Starting an Atoll Project

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

2.1

Before Starting a Radio-Planning Project

For every radio-planning project you must assemble the information necessary: Radioequipment: sites, transmitters, antennas, repeaters, and other equipment. For more information on radio equipment, see the technology-specific chapters. Radiodata: frequency bands, technology-specific parameters, coordinate systems, etc. For more information on radio data, see the technology-specific chapters. Geographic data: clutter classes, clutter heights, DTM, population maps, etc. For more information on geographic data, see "Chapter 2: Starting an Atoll Project".

Once the necessary data have been assembled, you can create the Atoll document.

2.2

Creating an Atoll Document

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

2.2.1

Creating a New Atoll Document from a Template

You can create a new Atoll document from a template. Atoll has a template for each technology you will be planning for. Each template provides data and a data structure suitable for the technology. For example, the tabs in the transmitter Properties dialogue as well as the radio parameters available differ according to the project. As well, the objects that are available are appropriate for the technology. For example, UMTS cells are only available in UMTS documents and TRX are only available in GSM-TDMA documents. Once you have selected the appropriate template for your radio-planning project, you configure the basic parameters of the Atoll document (see "Defining a New Atoll Document" on page 95). In this section, the following are explained: "Templates Available" on page 93 "Creating a New Atoll Document from a Template" on page 94 "Defining a New Atoll Document" on page 95

2.2.1.1

Templates Available
Depending on your configuration of Atoll, the following templates are available: GSM/GPRS/EGPRS: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

93

Atoll User Manual GPRS (General Packet Radio Service): GPRS is a packet-switched technology that enables data applications on GSM networks. It is considered a 2.5G technology. EDGE (Enhanced Data for Global Evolution): EDGE is an advancement for GSM/GPRS networks that triples data rates. Because it is based on existing GSM technology, it allows for a smooth upgrade for GSM operators, giving them capabilities approaching those of a 3G network, while remaining with the existing 2G system. EGPRS (GPRS operating over EDGE): EGPRS is GPRS, but operating over EDGE for enhanced data rates.

CDMA2000 1xRTT 1xEV-DO: This template can be used to model third generation (3G) mobile telecommunications based on CDMA2000 technology. CDMA2000 is an evolution of CDMA, or code division multiple access. This template can be used to model the following technologies: 1xRTT (1 Radio Transmission Technology): 1xRTT is sometimes considered not as 3G but as 2.5G in terms of mobile telecommunications. It offers increased voice capacity as compared to 2G technologies, but not as much as pure 3G solutions. 1xEV-DO (1x Evolution - Data Only): 1xEV-DO is an evolution of CDMA2000 that provides data transfer rates of over 10 times those of 1xRTT. It is considered a 3G solution and addresses, as its name suggests, data only. IS-95 cdmaOne: Second generation (2G) mobile telecommunications based on code division multiple access technology. IS-95 is an industry standard while cdmaOne is a proprietary implementation of this standard.

UMTS HSPA: UMTS (Universal Mobile Telecommunications System) and HSDPA (High Speed Downlink Packet Access) and HSUPA (High Speed Uplink Packet Access), collectively referred to as HSPA, are third generation (3G) mobile telecommunication systems based on WCDMA (Wideband Code Division Multiple Access) technology. Although WCDMA is similar in implementation to CDMA, the two technologies are incompatible. UMTS and HSPA are usually implemented in place and over GSM networks. TD-SCDMA: TD-SCDMA (Time Division Synchronous CDMA) is a 3G mobile telecommunication system based on Time Division Duplex (TDD) mode. TD-SCDMA transmits uplink and downlink traffic in the same frame in different time slots. WiMAX: Atoll WiMAX is a state-of-the-art WiMAX and Broadband Wireless Access (BWA) network planning tool developed in cooperation with world-leading WiMAX equipment suppliers. Atoll WiMAX supports the IEEE 802.16d as well as IEEE 802.16e. LTE: This template can be used to model the new fourth generation (4G) networks based on the UTRAN LTE (UMTS Terrestrial Radio Access Networks Long Term Evolution) specifications proposed by the 3GPP. Atoll LTE is strictly follows the latest 3GPP LTE specifications, and has been developed in collaboration with the marketleading equipment manufacturers. Atoll LTE is the first and most comprehensive LTE network planning tool available on the market.

2.2.1.2

Creating a New Atoll Document from a Template

To create a new document from a template: 1. Select File > New > From a Document Template. The Project Templates dialogue appears. 2. Select the template on which you want to base your document and click OK. Atoll creates a new document based on the template selected. Figure 2.45 shows a new Atoll document based on the UMTS HSPA HSPA template. The Data tab of the Explorer window now has a folder structure suitable for a UMTS HSPA HSPA radio-planning project, with, among other UMTSUMTS-specific elements, folders for UMTS HSPA HSPA parameters and UMTS HSPA HSPA simulations. The Antennas folder is expanded to show the UMTSUMTS-compatible antennas suggested by Atoll. These can be modified or replaced. Figure 2.46 and Figure 2.47 show the contents of the Geo and Modules tabs of the new document, respectively.

94

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2: Starting an Atoll Project

Figure 2.45: New Atoll document based on a template

Figure 2.46: New Atoll document Geo tab

Figure 2.47: New Atoll document Modules tab

When you create an Atoll document from a template, the document is not connected to a database. To verify whether the document is connected to a database: Select File > Database > Connection Properties. The dialogue in Figure 2.48 appears.

Figure 2.48: An Atoll document based on a template is not connected to a database

2.2.1.3

Defining a New Atoll Document

Once you have created a new Atoll document as explained in "Creating a New Atoll Document from a Template" on page 94, you configure the basic parameters of the Atoll document. You can accept the default values for some parameters, such as basic measurement units, but you must set projection and display coordinate systems. In this section, the following are explained: "Projection and Display Coordinate Systems" on page 96 "Setting a Coordinate System" on page 96 "Setting Measurement Units" on page 97

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

95

Atoll User Manual

2.2.1.3.1

Projection and Display Coordinate Systems

In Atoll, you define the two coordinate systems for each Atoll document: the projection coordinate system and the display coordinate system. By default, the same coordinate system is used for both. A projection is a method for producing all or part of a round body on a flat sheet. This projection cannot be done without distortion, thus the cartographer must choose the characteristic (distance, direction, scale, area or shape) which is to be shown appropriately at the expense of the other characteristics, or he must compromise on several characteristics1. The projected zones are referenced using cartographic coordinates (meter, yard, etc.). Two projection systems are widely used: The Lambert Conformal-Conic projection: a portion of the earth is mathematically projected on a cone conceptually secant at one or two standard parallels. This projection type is useful for representing countries or regions that lay primarily east to west. The Universal Transverse Mercator projection (UTM): a portion of the earth is mathematically projected on a cylinder tangent to a meridian (which is transverse or crosswise to the equator). This projection type is useful for mapping large areas that are oriented north-south.

A geographic system is not a projection, but a representation of a location on the earth's surface from geographic coordinates (degree-minute-second or grade) giving the latitude and longitude in relation to the origin meridian (Paris for NTF system and Greenwich for 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 distinguishes the cartographic coordinate systems for projection and either cartographic or geographic coordinate systems for display. The maps displayed in the workspace are referenced with the same projection system as the imported geographic data files; thus, the projection system depends on the imported geographic file. By choosing a specific display system, you can see (using the rulers or status bars) the location of sites on the map in a coordinate system different from the projection coordinate system. You can also position on the map sites referenced in the display system: the coordinates are automatically converted from the projection system to the display system and the site is displayed on the map. In Figure 2.49, the French Riviera geographic data file has been imported. The map shows the French Riviera projected using the cartographic NTF (Paris)/France II tendue system (coordinates in metres). On the other hand, site coordinates are stated in the geographic WGS 72 system (coordinates in degrees-minutes-seconds).

Figure 2.49: NTF (Paris)/France II tendue system used with WGS 72 system Notes: All imported raster geographic files must be use the same cartographic system. If not, you must convert them to a single cartographic system.

2.2.1.3.2

Setting a Coordinate System

Because you are working with maps, you must set a coordinate system for your Atoll document. By default, projection and display coordinate systems are the same, but you can choose a different display coordinate system if you wish. To define the coordinate system: 1. Select Tools > Options. The Options dialogue appears. 2. On the Coordinates tab, click the Browse button ( tems dialogue appears. ) to the right of the Projection field. The Coordinate Sys-

3. In the Coordinate Systems dialogue, select a catalogue from the Find in list. For the projection system, only cartographic systems (identified by the symbol) are available.

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.

96

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2: Starting an Atoll Project 4. Select a coordinate system from the list.

Tip:

If you frequently use a particular coordinate system you can add it to a catalogue of favourites by clicking Add to Favourites.

5. Click OK. The selected coordinate system appears in the Projection field and, by default, in the Display field as well. 6. If you wish to set a different coordinate system for the display, click the Browse button ( ) to the right of the Display field and repeat step 3. to step 5. For the display system, both cartographic systems (identified by the symbol) and geographic systems (identified by the symbol) are available.

2.2.1.3.3

Selecting the Degree Display Format

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

To change the degree display format: 1. Select Tools > Options. The Options dialogue appears. 2. On the Coordinates tab, select the format from the Degree Format list. 3. Click OK. Note: The degree format options apply only to the geographic coordinate systems.

2.2.1.3.4

Setting Measurement Units

When you create a new Atoll document, Atoll sets certain measurement units for reception, transmission, distance, height, and offset to internal defaults. You can accept these default measurement units, or you can change them using the Options dialogue. To set the measurement units: 1. Select Tools > Options. The Options dialogue appears. 2. On the Units tab, select the desired unit for the following measurements: Reception Transmission Distance Height and offset

3. Click OK.

2.2.2

Working in a Multi-User Environment

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

97

Atoll User Manual

2.2.2.1

The Atoll Multi-User Environment

An Atoll multi-user environment consists of the following elements, connected over a network: A central Atoll project: The central Atoll project can only be accessed, modified, and updated by the Atoll administrator. Through this central Atoll project, the Atoll administrator can manage all the data shared by all the individual Atoll users or groups of users. Shared data: Shared data are initially set up by the administrator using the central Atoll project and are then accessed, modified, worked on, and updated by the Atoll users and the administrator. The shared data are mainly of the following three types: The central database: The central database stores all the radio data of all the Atoll user documents. It is initiated through the central Atoll project by the administrator, and is then subdivided into sections on which users or groups of users can work simultaneously. Once the database is in place, users can modify their projects, refresh their projects from the data stored in the database, and archive their modifications in the database. The use of a database means that potential data conflicts due to modifications from other users, modified or deleted records, for example, can be detected and resolved. Shared geographic data: Shared geographic data files are usually stored on a common file server with a fast access connection. Since geographic data files are usually large, they are usually linked to an Atoll file, i.e., they are stored externally, so as to minimise the size of the Atoll file. Users who modify geographic data locally, for example, editing edit clutter or traffic in their respective projects, usually store these modifications locally, since these modifications rarely have an impact on other users. Path loss matrices: The path loss matrices are computed through the central Atoll project by the administrator and can be updated only by the administrator. Each user can read these path loss data but cannot modify them. If users modify their Atoll documents in such a way that the path loss data becomes invalid for their document, any path loss matrices computed by these users are stored locally, either embedded in the ATL file or link to an external file. The shared path loss data are not modified. Shared path loss matrices are updated when the calculation administrator performs an update, taking into account the modifications made by other users which have been stored and updated in the central database. Shared path loss matrices enable a number of users to work with a centralised path loss matrices folder, containing path loss matrices corresponding to the central Atoll project. User Documents: Individual user documents are initialised by the administrator but are later worked upon and managed by each user. User documents are Atoll files which are connected to the central database, load only the required part of the geographic data (as defined by the CFG file, for example), and have access to the shared path loss matrices folder.

Figure 2.50: Components of Multi-user Environments Note: For information on creating and maintaining the database, see the Administrator Manual.

98

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2: Starting an Atoll Project

2.2.2.2

Creating a New Atoll Document from a Database

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

The following sections give examples of connecting to two different databases and loading data: "Connecting to an MS Access Database" on page 99 "Connecting to an Oracle Database" on page 99. "Selecting the Data to Load From the Database" on page 99.

An example of a new Atoll document created from a database is shown in: "Working With a Document on a Database" on page 100

2.2.2.2.1

Connecting to an MS Access Database

To create a new document from an MS Access database: 1. Select File > New > From an Existing Database. The Open from a Database dialogue appears. 2. In the Files of type list, select "Microsoft Access" as the type of database: 3. Select the name of the database and click OK. The Data to Load dialogue appears, allowing you to select the data to load into Atoll as a new document (see "Selecting the Data to Load From the Database" on page 99).

2.2.2.2.2

Connecting to an Oracle Database

To create a new document from an Oracle database: 1. Select File > New > From an Existing Database. The Open from a Database dialogue appears. 2. In the Files of type list, select "Oracle" as the type of database: 3. In the dialogue that appears, enter your User Name, Password, and Server (as defined in the tnsnames.ora file).

Figure 2.51: Connecting to an Oracle database Note: Additional dialogues may open asking you to choose which project in the database to load or which site list to load.

4. Click OK. The Data to Load dialogue appears, allowing you to select the data to load into Atoll as a new document (see "Selecting the Data to Load From the Database" on page 99).

2.2.2.2.3

Selecting the Data to Load From the Database

When you create a new document from a database, you can select the data to be loaded from the database to create the document in the Data to load dialogue. You can select which Project, Site List, Custom Fields Groups, and Neighbour to load. If you load the intra-technology or the inter-technology neighbour list, Atoll will also load the associated exceptional pairs table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

99

Atoll User Manual

Figure 2.52: Selecting the data to load

2.2.2.3

Working With a Document on a Database

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

Figure 2.53: New Atoll document opened from a database Note: The new document may open with no site displayed in the map window. This is because the north-west point of the project is by default the axis origin. You can re-centre the document on the data displayed in the Data tab by expanding the Sites folder, rightclicking on any site, and selecting Centre in the map window from the context menu.

100

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2: Starting an Atoll Project

Figure 2.54: New Atoll document Geo tab

Figure 2.55: New Atoll document Modules tab

When you create an Atoll document from a database, you can view the characteristics of the database connection. To view the characteristics of the database connection: 1. Select File > Database > Connection Properties. The Database Connection dialogue appears (see Figure 2.56). 2. You can now: Disconnect your document from the database. Caution: If you disconnect your document from the database, it will be become a stand-alone document and you will not be able to reconnect it to the database.

Modify your connection to the database.

Figure 2.56: The Database Connection dialogue

2.2.2.4

Refreshing an Atoll Document from the Database

As you are working on your document, other users who have access to the database may have modified some of the data. You can ensure that you have the most recent data in your document by refreshing the information from the database. How frequently you refresh the document depends on how frequently the database is updated. If the database is updated frequently, you should refresh your document frequently as well, in order to continue working with the most up-to-date data. To refresh an Atoll document from the database: 1. Select File > Database > Refresh From the Database. The Refresh dialogue appears. 2. In the dialogue, you can do one of the following if you have modified your document but have not yet saved those changes in the database: Archive your changes in the database: This option allows you to archive your changes to the server instead of refreshing your document from the server. Refresh unmodified data only: This option allows you to refresh from the database only those items that you have not modified in your document. Cancel your changes and reload database: This option allows you to cancel any changes you have made and start over from the point of the last archive to the database. Notes: If you chose Refresh unmodified data only or Cancel your changes and reload database, Atoll proceeds without asking for confirmation. If you chose Archive your changes in the database, the Archive dialogue appears. For information on using the Archive dialogue, see "Archiving the Modifications of an Atoll Document in the Database" on page 102.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

101

Atoll User Manual 3. Under Take into account, you can select the neighbour lists, Intra-technology Neighbours and Inter-technology Neighbours, to refresh. 4. Under Modifications Since the Last Refresh, you can generate a report for the refresh process. 5. Click OK. The document is refreshed according to the selected options. If you selected to generate a report, Atoll creates a text file in CSV (Comma Separated Values) format in the temporary files system folder, and opens it. You can then rename the file and save it where you wish. The report lists all the modifications (deletions, additions, and updates) that were stored in the database since the last time you refreshed or opened your document.

2.2.2.5

Archiving the Modifications of an Atoll Document in the Database

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

2.2.2.5.1

Archiving All Modifications in the Database

To archive all your modifications in the database: 1. Select File > Database > Archive to the Database. The Archive dialogue appears (see Figure 2.57). 2. In the Archive dialogue, you can do the following: Click Run All to archive all your changes to the database. Select one item under Pending Changes and click Run to archive the selected modification to the database Select one item under Pending Changes and click Differences to view the differences between the local item and the item on the database. Select one item under Pending Changes and click Undo to refresh the modification with the original data from the database.

Figure 2.57: The Archive dialogue 3. If some of the data has been modified on the database since you last refreshed, Atoll stops the archiving process and asks you to resolve the conflict. For information on managing conflicts, see "Resolving Data Conflicts" on page 103. 4. When you are finished archiving, click Close.

2.2.2.5.2

Archiving Only Site-Related Data in the Database

Atoll allows you to archive only site-related data if you wish. Which data is archived depends on the radio technology you are working with. For example, in a UMTS HSPA radio planning project, the site-related data are: sites, transmitters, cells, and neighbours.

102

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2: Starting an Atoll Project To archive only the site-related data in the database: 1. Select File > Database > Archive to the Database. The Archive dialogue appears. 2. In the Archive dialogue, you can do the following: Click Run All to archive all your changes to the database. Select one item under Pending Changes and click Run to archive the selected modification to the database Select one item under Pending Changes and click Differences to view the differences between the local item and the item on the database. Select one item under Pending Changes and click Undo to refresh the modification with the original data from the database.

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 103. 4. When you are finished archiving, click Close.

2.2.2.5.3

Resolving Data Conflicts

Atoll enables several users to use the same database by allowing user to load the data and then freeing the database for other users. However, this also creates the possibility of two users modifying the same data. When the second user attempts to archive his changes, Atoll warns him that the data have been changed since he last refreshed the data and that there is a conflict. Atoll allows you to resolve data conflicts. When Atoll finds a conflict, it displays the warning shown in Figure 2.58.

Figure 2.58: Conflict warning You have three options: Ignore: If you click Ignore, Atoll ignores items causing conflicts in the table being archived, archives all other modifications in the table, and continues with the next table. You can resolve the conflicts after the archiving process has ended. However, if conflicts are found in other tables, Atoll will warn you with the Database Transfer Error dialogue again. Ignore All: If you click Ignore All, Atoll ignores all items causing conflicts in all tables being archived, and archives all other modifications. You can resolve the conflicts after the archiving process has ended. Abort: If you click Abort, the archiving process stops. You can attempt to resolve conflicts before restarting the archiving process.

Whether you abort the archive process to resolve the conflict immediately, or wait until the end of the archive process, the procedure to resolve the conflict is the same. To resolve data conflicts one by one: 1. In the Pending Changes pane of the Archive dialogue, select the conflict you want to resolve and click Resolve. There are two different types of data conflicts: On a modified record: You are in the process of archiving your modifications on the database and another user has modified the same data since you last archived or refreshed your data. A conflict is caused only by differences in the same field of the same record between the database and the current Atoll document. The Conflict in Changes dialogue appears, with the fields in conflict highlighted (see Figure 2.59). In the Conflict in Changes dialogue, you can see the value of the field in the database in the Database values column, as well as the value of the same field in your document in the Current values column.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

103

Atoll User Manual

Figure 2.59: The Conflict in Changes dialogue If you want to overwrite the database value with the value of the same field in your document, select the check box next to the highlighted change and click Archive. 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 Archive. 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 103. Atoll displays a message explaining that the record you are trying to update has been deleted from the database (see Figure 2.60). Select one of the following:

Figure 2.60: Conflict on a deleted record Yes: Select Yes to store your modifications in the database, thereby recreating the deleted record. No: Select No to abandon your modifications to this record and delete this record from your document. Cancel: Select Cancel to cancel.

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

Figure 2.61: Resolving all the data conflicts simultaneously Yes: Select Yes to accept all the modifications made by other users in the database and update your document with values from the database. No: Select No to overwrite the modifications made by other users in the database with the values from your document. Cancel: Select Cancel to cancel.

2. Click Close to close the Archive dialogue. Important: You should only resolve all the data conflicts when you are certain about the modifications.

104

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2: Starting an Atoll Project

2.3

Making a Backup of Your Document

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

2.3.1

Configuring Automatic Backup

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

Figure 2.62: Automatic backup configuration dialogue 2. Select the Activate automatic backup check box. 3. Select the Prompt before starting automatic backup check box if you want Atoll to ask you before saving the back up of your file every time (see Figure 2.63). 4. Enter a time interval, in minutes, between consecutive backups in the Automatically save backups every text box. Note: It can take a long time to back up large documents. Therefore, you should set a correspondingly larger interval between backups when working with large documents in order to optimise the process.

5. Click OK. If you selected the Prompt before starting automatic backup check box, Atoll prompts you each time before backing up the document. If you click OK, Atoll proceeds to back up all open documents. If you click Cancel, Atoll skips the backup once.

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

105

Atoll User Manual

2.3.2

Recovering a Backup
You can easily recover your backup document and open it in Atoll just like any other Atoll document. To recover your backup document: 1. Using Windows Explorer, navigate to the folder containing your original Atoll document and its backup. 2. If the original document was named "filename.atl," the backup document will be in the same folder and will be called "filename.atl.bak". Rename the document and remove the BAK extension. For example, you could change the name to "filename-backup.atl." Important: If you just remove the BAK extension, your backup file will have the same file name as the original file and Windows will not allow you to rename the file. Therefore, it is safer to give a new name to the backup file and keep the original file until you are sure which version is most recent. 3. Open the renamed backup document in Atoll. You will be able to recover all the work up to the last time the backup was saved.

2.4

Making and Sharing Portable Atoll Projects

You can create portable Atoll documents in two ways: by embedding all the geographic data in the ATL file, or by creating a compressed archive (ZIP file) containing the ATL file and all geographic data linked to the Atoll document.

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

106

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 2: Starting an Atoll Project

Notes: You do not need to have a compression utility, such as WinZip or WinRAR, installed on the computer for this feature. The highest compression level is used when creating the archive.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

107

Atoll User Manual

108

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3
Managing Geographic Data

RF Planning & Optimisation Software

Atoll

Atoll User Manual

110

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data

Managing Geographic Data

Several different geographic data types are used in an Atoll document. For example: the Digital Terrain Model (DTM), clutter classes, clutter heights, scanned images, population maps, and traffic data maps are types of the geographic data that you can import or create. Some data types, such as clutter classes, can be used to give more realistic calculations. Other types such as scanned images, are used to create a more realistic display of the region under study. You can import a wide variety of both vector and raster-format geo data files. When you import a geo data file into Atoll, you can decide in which folder it goes. The Geo tab of the Atoll Explorer window has folders for the commonly used data types. Therefore, choosing a folder is choosing what the file will be used for. You can also create your own data type by importing a file and defining what data is to be used. Once you have imported a file into the Atoll document, you can edit the data, define how the geo data will be displayed. Atoll also allows you to manage multiple files for a single data type, deciding the priority of data files with different information or different resolutions. You can also display geo data over items on the Data tab, either by transferring them to the Data tab, or by importing them directly to the Data tab. You can also create and edit geographic data. You can add a vector layer to certain data types to which you can add contours, lines, or points, create new geographic data, or modify existing data. You can also create raster-based geographic data such as traffic maps or clutter classes. You can export most geo data objects (for example, DTM, clutter classes, clutter heights, raster polygons, or vector layers) for use in other Atoll documents or in other applications. Atoll also allows you to save changes you make to geo data objects back to the original files. This enables you to update the original files and, through the process of saving them, recompact the file. This chapter explains the following topics: "Geographic Data Types" on page 111 "Supported Geographic Data Formats" on page 112 "Importing Geo Data Files" on page 113 "Clutter Classes" on page 120 "Clutter Heights" on page 123 "Digital Terrain Models" on page 120 "Contours, Lines, and Points" on page 123 "Scanned Images" on page 125 "Population Maps" on page 126 "Custom Geo Data Maps" on page 127 "Setting the Priority of Geo Data" on page 129 "Editing Geographic Data" on page 133 "Saving Geographic Data" on page 136.

3.1

Geographic Data Types

An Atoll document can contain several different geographic data types. Atoll supports a wide range of file formats for geographic data files. The different geographic data types play different roles in the Atoll document: Geographic data used in propagation calculation: Digital terrain model Clutter classes Clutter heights Traffic maps Population maps Custom maps Scanned maps Images from web map services (WMS) Contours, lines, and points representing, for example, roads, railways, or regions.

Geographic data used in dimensioning: Geographic data used in statistics:

Geographic data used for display purposes:

In this section, the following data types are described: "Digital Terrain Model" on page 112 "Clutter Classes" on page 112 "Clutter Heights" on page 112 "Contours, Lines, and Points" on page 112 "Scanned Images" on page 112 "Population Maps" on page 112 "Traffic Data Maps" on page 112 "Custom Data Maps" on page 112.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

111

Atoll User Manual

Digital Terrain Model

The DTM describes the elevation of the ground over sea level. You can display the DTM in different ways: by single value, discrete values, or by value intervals (see "Display Properties of Objects" on page 32). The DTM is automatically taken into account by the propagation model during computations.

Clutter Classes
The clutter class geo data file describes land cover or land use. Clutter classes are taken into account by the propagation model during computations. Each pixel in a clutter class file contains a code (from a maximum of 256 possible classes) which corresponds to a clutter class, or in other words to a certain type of ground use or cover. The height per class can be defined as part of the clutter class, however, the height will be defined as an average height for each clutter class. For information on defining the height per clutter class, see "Defining Clutter Class Properties" on page 121. Clutter heights can also be defined by a separate clutter heights file (see "Clutter Heights" on page 112). A clutter height map can represent height much more accurately because it allows a different height to be assigned for each pixel of the map.

Clutter Heights
Clutter height maps describe the altitude of clutter over the DTM with one altitude defined per pixel. Clutter height maps can offer more precise information than defining an altitude per clutter class because, in a clutter height file, it is possible to have different heights within a single clutter class. When clutter altitude is defined both in clutter classes and in a clutter height map, clutter altitude is taken from the clutter height map. You can display the clutter height map in different ways: by single value, discrete values, or by value intervals (see "Display Properties of Objects" on page 32). Note: The only propagation models that can take clutter heights into account in calculations are the Standard Propagation Model and WLL model.

Contours, Lines, and Points

Atoll supports contours, lines, and points to represent polygons such as regions, or lines such as roads or coastlines, or points. They are used for display only and have no effect on computations. Contours can also be used to create filtering polygons or computation or focus zones.

Scanned Images
Scanned images are geographic data files which represent the actual physical surroundings, for example, road maps or satellite images. They are used to provide a precise background for other objects or for less precise maps and are used only for display; they have no effect on calculations.

Population Maps
Population maps contain information on population density or on the total number of inhabitants. Population maps can be used in prediction reports in order to display, for example, the absolute and relative numbers of the population covered. Population maps have no effect on prediction and simulation results.

Traffic Data Maps

Traffic data maps contain information on capacity and service use per geographic area. Traffic data maps are used for network capacity analyses.

Custom Data Maps

You can import many different types of files for, for example, revenue, rainfall, or socio-demographic data. You could use the imported data in prediction reports. For example, you could display the predicted revenue for defined coverage. These imported data have no effect on prediction and simulation results.

3.2

Supported Geographic Data Formats

Atoll supports the following geographic data formats: DTM files in the following formats: TIF (8 or 16-bit), JPEG 2000 (8 to 16-bit), BIL (8 or 16-bit), IST (8 or 16-bit), Planet, BMP (8-bit), GRD/GRC Vertical Mapper (8 or 16-bit), and Erdas Imagine (8 or 16-bit) Clutter height files in the following formats: TIF (8 or 16-bit), JPEG 2000 (8 to 16-bit), BIL (8 or 16-bit), IST (8 or 16-bit), Planet, BMP (8-bit),, GRC Vertical Mapper (8 or 16-bit), and Erdas Imagine (8 or 16-bit) Clutter class and traffic files in the following formats: TIF (8-bit), JPEG 2000 (8-bit), BIL (8-bit), IST (8-bit), BMP (8-bit), Planet, GRC Vertical Mapper (8-bit), and Erdas Imagine (8-bit) Vector data files in the following formats: AGD, DFX, Planet, SHP, MIF, and TAB.

112

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data Vector traffic files in the following formats: AGD, DFX, Planet, SHP, MIF, and TAB. Scanned image files in the following formats: TIF (1 to 24-bit), JPEG 2000 (1 to 24-bit), BIL (1 to 24-bit), IST (1 to 24-bit), BMP (1 to 24-bit), Planet, Erdas Imagine (1 to 24-bit), GRC Vertical Mapper (1 to 24-bit), and ECW (8 or 24-bit) Population files in the following formats: TIF (16-bit), JPEG 2000 (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), JPEG 2000 (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. Caution: All raster maps imported must have the same projection coordinate system.

3.3

Importing Geo Data Files

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

This section explains the following: "Importing a Raster-format Geo Data File" on page 113 "Importing a Vector-format Geo Data File" on page 114 "Importing MSI Planet Geo Data" on page 115 "Importing a WMS Raster-format Geo Data File" on page 117 "Grouping Geo Data Files in Folders" on page 118 "Embedding Geographic Data" on page 119.

Tip:

You can use the drag-and-drop feature to import geo data files into a document. The format is automatically recognized and Atoll presents you with the appropriate dialogue.

3.3.1

Importing a Raster-format Geo Data File

All raster geo data files must be represented in the same projection coordinate system as the Atoll document itself. To import a geographic data file in a raster format: 1. Select File > Import. The Open dialogue appears. 2. Select the geo data file you want to import. You can import more than one geo data file at the same time, providing that the geo data files are of the same type. You can select contiguous files by clicking the first file, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file. 3. Click Open. The File Import dialogue appears (see Figure 3.64). Note: If the Vector Import dialogue appears, go to "Importing a Vector-format Geo Data File" on page 114.

Depending on the type of geo data file you are importing, choose one of the following options: DTM: Select Altitudes (DTM) from the Data Type list. Clutter Classes: Select Clutter Classes from the Data Type list. Clutter Heights: Select Clutter Heights from the Data Type list. Scanned Images: Select Image or Scan from the Data Type list. Population: i. Select Population from the Data Type list. The Use as list becomes available.

ii. Select from the Use as list whether the imported data are to be interpreted as a Density (number of inhabitants per square kilometre) or as a Value (number of inhabitants). Forsk 2010 Custom Geo Data: See "Custom Geo Data Maps" on page 127. Unauthorized reproduction or distribution of this document is prohibited

113

Atoll User Manual Traffic Data Maps: Select Traffic Density from the Data Type list.

4. By default, the imported file is linked to the Atoll document. To embed the data file in the Atoll document, select the Embed in Document check box. For information on embedding files, see "Embedding Geographic Data" on page 119. 5. Click Import. The geo data file is imported and listed in the Geo tab of the Explorer window. When you import a traffic data map, the traffic maps Properties dialogue appears: a. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. b. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. c. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal 100. d. Under Clutter Distribution, enter for each clutter class the percentage of indoor users. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for traffic density maps because the traffic is provided in terms of user density per pixel. e. For UMTS and CDMA, select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink. f. Click OK.

Figure 3.64: Importing a clutter class file

3.3.2

Importing a Vector-format Geo Data File

When you import geo data files in vector format, their geographic system can be converted to the system used by the Atoll document. To import a vector-format geographic data file: 1. Select File > Import. The Open dialogue appears. 2. Select the geo data file you want to import. You can import more than one geo data file at the same time, providing that the geo data files are of the same type. You can select contiguous files by clicking the first file, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file. 3. Click Open. The Vector Import dialogue appears (see Figure 3.67). Note: If the File Import dialogue appears, go to "Importing a Raster-format Geo Data File" on page 113.

Depending on the type of geo data file you are importing, choose one of the following options: Vector Data: i. Select Geo from the Import to list. Select Population from the Import to list. Population:

114

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data ii. Under Fields to be imported, the first list contains the attributes of the population vector data file that you are importing, and the second list lets you select whether the attribute corresponds to population density or to a number of inhabitants. iii. Select from the first list which field is to be imported and from the second list whether the imported field is a Density (number of inhabitants per square kilometre for polygons, or number of inhabitants per kilometre for lines) or a Value (number of inhabitants) (see Figure 3.65 and Figure 3.66).

Figure 3.65: Population density (number of inhabitants/km)

Figure 3.66: Population values (number of inhabitants per item polygon/road/point) Custom Geo Data: See "Custom Geo Data Maps" on page 127. Traffic Data Maps: Select Traffic from the Import to list.

4. By default, the imported file is linked to the Atoll document. To embed the data file in the Atoll document, select the Embed in Document check box. For information on embedding files, see "Embedding Geographic Data" on page 119. 5. Click Import. The geo data file is imported and listed in the Geo tab of the Explorer window.

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

3.3.3

Importing MSI Planet Geo Data

MSI Planet geo data are contained in a series of files described in index files. The index file is in ASCII text format and contains the information necessary to identify and properly interpret each geo data file. When you import MSI Planet geo

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

115

Atoll User Manual data, you can import each type of geo data separately, by importing the corresponding index file, or you can import several MSI Planet geo data files at the same time, by importing several index files. This section explains the following: "Importing One MSI Planet Geo Data Type" on page 116 "Importing a MSI Planet Geo Database" on page 116.

3.3.3.1

Importing One MSI Planet Geo Data Type

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

Figure 3.68: Importing an MSI Planet index file 3. Select the type of geo data you are importing and select the Embed check box if you want to embed the data in the current Atoll document. 4. Click OK to import the geo data into the current Atoll document.

3.3.3.2

Importing a MSI Planet Geo Database

You can import all available MSI Planet geo data at the same time by importing all index files. To import the MSI Planet geo database: 1. Select File > Import. The Open dialogue appears. 2. Select "Planet database" from the Files of Type list. The Planet Data to Be Imported dialogue appears (see Figure 3.69).

116

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data

Figure 3.69: Importing an MSI Planet database 3. For each type of data that you want to import: a. Select the corresponding check box b. If you want to embed the data, select the Embed check box. c. To locate the MSI Planet index file, click . The Open dialogue appears.

d. Select the MSI Planet index file and click Open. The path and name of the file appears in the corresponding field of the Planet Data to Be Imported dialogue. 4. When you have selected all the types of data you want to import, click OK. The data is imported into the current Atoll document.

3.3.4

Importing a WMS Raster-format Geo Data File

You can import raster images from a Web Map Service (WMS) server into your Atoll document. The image must be in TIF format. All images imported at the same time are imported as a single image. Before you import them, you can arrange them by placing on top the image that is the most important, such as roads. Or, you can place the least transparent image towards the bottom so that the other images imported at the same time remain visible. The image will be referenced in the document; it can not be embedded. Only WMS data mapped with a projection system (for example, the Lambert Conformal-Conic or the Universal Transverse Mercator projection) can be imported. Before importing an image from a WMS server, you must ensure that the coordinate system used in your document is the same projection system supported by the server. All raster geo data files must be represented in the same projection coordinate system as that used by the Atoll document itself. To import a geographic data file from a web map service: 1. Select File > Import. The Open dialogue appears. 2. From the Files of Type list, select Connection to a Web Map Services server. The Web Map Services Data Import dialogue appears. 3. Select the URL of the WMS server from the Server URL list or enter it directly. Note: The list of WMS servers that appears in the Server URL list are defined by entries in the atoll.ini file. For information on defining these entries, see the Administrator Manual.

4. Click the Connect button. Atoll connects to the URL of the WMS server and displays the information available along with a description of the service (Figure 3.70 on page 118).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

117

Atoll User Manual

Figure 3.70: The Web Map Services Data Import dialogue 5. In the left pane of the Web Map Services Data Import dialogue, navigate to the item you want to import by clicking the Expand button ( ) to open each level. 6. Select either the image you want to import, or the image group, i.e., a group preceded by an Expand button ( ).

7. Click for each image you want to import. The files you want to import appear in the right pane of the Web Map Services Data Import dialogue. Note: You can remove an image or group of images from the images to be imported by selecting it in the right pane and clicking .

8. Arrange the order in which you want the images to appear by selecting each image in the right pane and clicking to move it towards the top or to move it toward the bottom. The images will be imported as a single object and their appearance will depend on the order you define here. 9. The Web Map Import dialogue appears. The following information is given about the imported WMS data: Data Types: "Image or Scan" is selected. Geographic Coordinates: The geographic coordinates are the WMS data are given.

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

3.3.5

Grouping Geo Data Files in Folders

By default, when you import scanned images and contours, lines, and points, they appear directly on the Geo tab. Other data files, such as clutter classes, are listed together in a single Clutter Classes folder. You can, however, group scanned images and contours, lines, and points into folders as well. Once grouped, these geo data files can be displayed or hidden and moved more easily. They retain, however, their own individual display settings; the display settings cannot be managed at the folder level. You create the folder when you import the first geo data file that will be imported into it. When you import the next geo data file, either raster or vector, you can import it directly into the new folder. To create a new geo data folder when importing: 1. Select File > Import. The Open dialogue appears. 2. Select the geo data file and click Open. If the file to be imported is a raster file, the File Import dialogue appears (see Figure 3.64). If the file to be imported is a vector file, the Vector Import dialogue appears (see Figure 3.67). 3. From the Data Type list (on the File Import dialogue) or the Import To list (on the Vector Import dialogue), select New folder in Geo. The New Folder dialogue appears. Note: If you want to import your file to the Data tab, you can select New folder in Data.

118

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data 4. Enter a name for the folder in Folder Name box and click OK. 5. Click Import. Your file is imported into the newly created folder. You can now import other geo data files into this folder by selecting it from the Data Type list (on the File Import dialogue) or the Import To list (on the Vector Import dialogue) when you import. Note: You can transfer geo data that has been imported from the Geo tab to the Data tab, or vice versa. Right-click the data in the Explorer window and select Transfer to Data or Transfer to Geo.

3.3.6

Embedding Geographic Data

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

To embed a geo data file that is already linked to the current Atoll document: 1. Click the Geo tab in the Explorer window. 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 dialogue. 5. Click Embed. 6. Click OK. The geo data file is now embedded in the current Atoll document.

3.3.7

Repairing a Broken Link to a Geo Data File

By default, when you import a geo data file, Atoll creates a link to the file; the geo data file remains separate and modifying or saving the Atoll document has no effect on the geo data file. If, however, the geo data file is moved, the link will be broken. The next time you open an Atoll document with the linked geo data file, Atoll cannot find the file and displays the error message shown in Figure 3.71.

Figure 3.71: Missing shortcut To find the file yourself: When the Missing Shortcut dialogue (see Figure 3.71) appears, click the Browse button to locate the geo data file.

Atoll automatically searches for the missing file as well. It searches for the nearest match, based on size, date, and type. When it finds a possible match, it informs you with a message (see Figure 3.72). If the file corresponds to the source file: Click Yes. The link will be corrected to point to the indicated file.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

119

Atoll User Manual

Figure 3.72: Problem with shortcut You can also repair the link to the geo data file from within the Atoll document. To repair a broken link from within the Atoll document: 1. Click the Geo tab in the Explorer window. If the geo data file is in a folder, such as the Clutter Classes, Traffic, 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 dialogue, click the Find button. 5. Browse to the geo data file, select it and click OK.

3.4

Digital Terrain Models

The Digital Terrain Model (DTM) is a geographic data file representing the elevation of the ground over sea level. To manage the properties of the DTM: 1. Click the Geo tab in the Explorer window. 2. Right-click the Digital Terrain Model folder. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab to define the display properties for the DTM. For information on Display tab settings, see "Display Properties of Objects" on page 32.

5. Move the Relief slider towards Flat, if you want to display very few little relief or towards x6 if you want to emphasise the differences in altitude. 6. Click OK to close the Properties dialogue.

3.5

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

3.5.1

Assigning Names to Clutter Classes

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

120

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data 3. Select Properties from the context menu. 4. Click the Description tab of the Properties dialogue. 5. In the Name column, enter descriptive text for each class identified in the Code column.

3.5.2

Defining Clutter Class Properties

The parameters are applied in relation to the location of the receiver being studied and the clutter class of the receiver location. These parameters can be set on the Properties dialogue: To define clutter class properties: 1. Click the Geo tab of the Explorer window. 2. Right-click the Clutter Classes folder. 3. Select Properties from the context menu. 4. Click the Description tab of the Properties dialogue. 5. Enter a Name and average Height (m) for each code. Important: If the Height field is left blank, propagation models which use the height information of clutter classes will assume a clutter height of "0" if there is no clutter height map. 6. If desired, you can enter a value for each of the following fields applicable to the current document: For all Atoll documents: Model Standard Deviation (dB): to calculate shadowing losses on the path loss, as related to a userdefined cell edge coverage probability. Indoor Loss (dB): to be applied to the path loss and used in coverage predictions, point analysis, and Monte Carlo simulations. Indoor penetration losses depend on the clutter types as well as the operating frequency. You can define an additional indoor loss, per frequency band used, in the Frequency bands table in GSM GPRS EGPRS, UMTS HSPA, CDMA2000 1xRTT 1xEV-DO, and TD-SCDMA documents. For this, you must first add a new field in the Frequency Bands table in the database. For more information, see the Administrator Manual.

Note:

For GSM/GPRS/EGPRS documents: C/I Standard Deviation (dB): to calculate shadowing losses on the C/I values, as related to a user-defined cell edge coverage probability. Additional Diversity Gain (DL) (dB): to add to the 3 dB gain in case diversity is set at the subcell level. Ec/Io Standard Deviation (dB): to calculate shadowing losses on the Ec/Io values, as related to a userdefined cell edge coverage probability. Eb/Nt Standard Deviation DL (dB): to calculate shadowing losses on the Eb/Nt values, as related to a user-defined cell edge coverage probability. Eb/Nt Standard Deviation UL (dB): to calculate shadowing losses on the Eb/Nt values, as related to a user-defined 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 multi-path, 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 support transmit 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.

For UMTS HSPA, IS-95 cdmaOne, and CDMA2000 1xRTT 1xEV-DO documents: -

For TD-SCDMA documents: -

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

121

Atoll User Manual 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. C/I Standard Deviation (dB): to calculate shadowing losses on the C/(I+N) values, as related to a userdefined cell edge coverage probability. SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs in the MIMO tab of reception equipment. Additional STTD/MRC Gain (DL) (dB): to add to the users downlink C/(I+N), if the user and its reference cell support STTD/MRC. Additional STTD/MRC Gain (UL) (dB): to add to the users uplink C/(I+N), if the user and its reference cell support STTD/MRC. C/I Standard Deviation (dB): to calculate shadowing losses on the C/(I+N) values, as related to a userdefined 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.

For WiMAX 802.16d and WiMAX 802.16e documents: -

For LTE documents: -

7. Click the Default Values tab. Enter default values for each field. For information about each field, see the descriptions in the previous step. The values entered on the Default Values tab 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 Default Values tab to make Atoll use the values specified in this tab instead of the values defined per clutter class. 8. Click the Display tab to define the display properties for clutter classes. In addition to the Display tab options described in "Display Properties of Objects" on page 32, 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. Note: 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.

9. Click OK.

Tip:

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

3.5.3

Adding a Clutter Class

You can add a new clutter class to your document. To add a new clutter class to the your document: 1. Click the Geo tab in the Explorer window. 2. Right-click the Clutter Classes folder. 3. Select Properties from the context menu. 4. Select the Description tab from the Properties dialogue. 5. In the blank row marked with column. at the bottom of the table, enter an unused number from 1 to 255 in the Code

6. Fill in the remainder of the fields as described in step 5. and step 6. of "Defining Clutter Class Properties" on page 121. 7. Click OK. You can now use the new clutter class when modifying the clutter class map. For information on modifying the clutter class map, see "Creating a Clutter Polygon" on page 134.

122

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data

3.5.4

Refreshing the List of Clutter Classes

Under certain circumstances, it can happen that the list of clutter classes on the Description tab of the clutter classes Properties dialogue contains unused clutter classes. For example, if you have imported two clutter class files and then deleted one of them, the list of clutter classes will still contain the clutter classes of the deleted file, even if they are not used in the remaining file. Whenever you want to ensure that the list of clutter classes is accurate and current, you can refresh the list. To refresh the list of the clutter classes: 1. Click the Geo tab in the Explorer window. 2. Right-click the Clutter Classes folder. 3. Select Properties from the context menu. 4. Select the Description tab from the Properties dialogue. 5. Click Refresh. Atoll removes the unused clutter classes from the list. 6. Click OK.

3.5.5

Displaying Total Surface Area per Clutter Class

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

3.6

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

5. Click OK to close the Properties dialogue. The clutter height of the current pointer position as given in the clutter height file or in the clutter classes is displayed in the status bar.

3.7

Contours, Lines, and Points

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

123

Atoll User Manual The vector object data can be managed in the vector layer table. For information on working with data tables, see "Working with Data Tables" on page 53. In this section, the following are explained: "Managing the Display of a Vector Layer" on page 124 "Managing the Properties of the Vector Layer" on page 124 "Moving a Vector Layer to the Data Tab" on page 125.

3.7.1

Managing the Display of a Vector Layer

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

3.7.2

Managing the Properties of the Vector Layer

The properties of the objects on the vector layer can be managed in two ways: either from a table containing all vectors and their attributes or from the Properties dialogue.

Vector Layer Table

All the vector objects of a vector layer and their attributes are listed in the vector table. To open the vector layer table: 1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Open Table from the context menu. The vector table appears. You can edit the contents of this table using the commands from the context menu or from the Edit, Format, and Records menus. For more information on editing tables in Atoll, see "Working with Data Tables" on page 53.

Vector Layer Properties Dialogue

The vector layer Properties dialogue has three tabs: a General tab, a Table tab, and a Display tab. To open the Properties dialogue of a vector layer: 1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Properties from the context menu. 3. Click the General tab. The following options are available: Name: The name of the vector layer. You can rename the vector layer using this field. Source File: The complete path of the vector layer file if the file is linked to the Atoll document; otherwise the file is described as embedded. Find: Click the Find button to redefine the path when the files location has changed. Embed: Click the Embed button to embed a linked vector layer file in the Atoll document.

Coordinate System: When a vector layer is linked, the coordinate system used is the files, as specified when the file was imported. When the a vector layer is embedded, the coordinate system used is documents, as specified when the file was embedded. Change: Click the Change button to change the coordinate system of the vector layer. Sort: Click the Sort button to sort the data contained in the vector layer. For information on sorting, see "Advanced Sorting" on page 73. Filter: Click the Filter button to filter the data contained in the vector layer. For information on filtering, see "Advanced Data Filtering" on page 75.

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 54. 5. Click the Display tab. You can use the Display tab to manage the vector layer display. For information on the Table tab, see "Display Properties of Objects" on page 32.

124

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data

3.7.3

Moving a Vector Layer to the Data Tab

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

3.8

Scanned Images
Scanned images are geographic data files which represent the actual physical surroundings, for example, road maps or satellite images. They are used to provide a precise background for other objects or for less precise maps.They have no effect on calculations. In this section, the following are explained: "Importing Several Scanned Images" on page 125 "Defining the Display Properties of Scanned Images" on page 125.

3.8.1

Importing Several Scanned Images

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

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

3.8.2

Defining the Display Properties of Scanned Images

Because imported images cannot be modified, they have fewer display parameters than other object types. To define the display properties of a scanned image: 1. Click the Geo tab in the Explorer window 2. Right-click the scanned image. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears (see Figure 3.73). 4. Select the Display tab and set the following options: Colour: Select either Automatic, Shades of gray, or Watermark from the list. Transparent Colour: Select White from the list if you wish parts of the scanned image that are coloured white to be transparent, allowing objects in lower layers to be visible. Lightness: Move the slider to lighten or darken the scanned image. Contrast: Move the slider to adjust the contrast.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

125

Atoll User Manual Visibility Scale: Enter a visibility scale minimum in the between 1: text box and maximum in the and 1: text box. When the displayed or printed scale is outside this range, the scanned image is not displayed.

5. Click OK.

Figure 3.73: Scanned image Properties dialogue

3.9

Population Maps
Population maps contain information on population density or on the total number of inhabitants. Population maps can be used in prediction reports in order to display, for example, the absolute and relative numbers of the population covered. In this section, the following are explained: "Managing the Display of Population Data" on page 126 "Displaying Population Statistics" on page 126.

3.9.1

Managing the Display of Population Data

You can manage the display of population data. To manage the display of population data: 1. Click the Geo tab in the Explorer window. 2. Right-click the Population folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Display tab of the Properties dialogue. For information on using the display tab, see "Display Properties of Objects" on page 32. Note: Vector points added to a vector population map are not displayed if the map is displayed by population density.

3.9.2

Displaying Population Statistics

You can display the relative and absolute distribution of population, according to the defined value intervals in the display properties (for information on defining value intervals, see "Defining the Display Type" on page 33), as well as the total population. Atoll displays the statistics for the focus zone if there is one, for the computation zone if there is no focus zone and, if there is no focus or computation zone, Atoll displays the statistics for the entire document. To display the population distribution statistics: 1. Click the Geo tab of the Explorer window. 2. Right-click the Population folder. 3. Select Statistics from the context menu. The Statistics window appears with the distributions of each value interval defined in the display properties. Note: Statistics are displayed only for visible data. See "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.

126

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data

3.10

Custom Geo Data Maps

You can import maps other than the default maps that Atoll uses. For example, you can import files for the revenue, rainfall, or socio-demographic data. Depending on the type of information displayed, you could use it in prediction reports. For example, you could display the predicted revenue for defined coverage. These maps can be raster files of 8, 16, or 32 bits per pixel or vector-format files that you have either imported or created using the vector edition tool "Editing Polygons, Lines, and Points" on page 46. You create an custom data map by: 1. Importing an custom geo data file and creating the custom data map folder. 2. Importing other custom geo data files into the newly created custom data map folder, if more than one file will be used for this custom geo data map. In this section, the following are explained: "Creating a Custom Geo Data Map" on page 127 "Adding a File to a Custom Geo Data Map" on page 128 "Managing the Properties of a Custom Geo Data Map" on page 128 "Displaying Statistics on Custom Geo Data" on page 129 "Integrable Versus Non Integrable Data" on page 129.

3.10.1

Creating a Custom Geo Data Map

The first step in creating a custom geo data map is importing the first file and creating the custom data map folder. To create an custom geo data map: 1. Select File > Import. The Open dialogue appears. 2. Select the first geo data file that will be a part of the custom data map and click Open. If the selected file is a raster file, the File Import dialogue appears (see Figure 3.64). If the selected file is a vector file, the Vector Import dialogue appears (see Figure 3.67).

3. Click the Advanced button. The New Type dialogue appears (see Figure 3.67). 4. Enter a Name for the custom geo data map. Atoll creates a folder with this name on the Geo tab and all other files of the new custom geo data map will go in here. 5. Under Supported Input Formats, select the check boxes corresponding to the formats of both the present file and all other files that will constitute the new custom geo data map: 8-bit Raster 16-bit Raster 32-bit Raster Vector. Important: 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. Important: 8. Click OK. 9. If the imported file is a raster file, the File Import dialogue appears (see Figure 3.64 on page 114); if the imported file is a vector file, the Vector Import dialogue appears (see Figure 3.67 on page 115): File Import dialogue: From the Use as list, select whether the new data is to be used a Density or as a Value. Vector Import dialogue: Under Fields to be imported, select from the first list which field is to be imported and from the second list whether the imported field is a Density or a Value (see Figure 3.65 on page 115 and Figure 3.66 on page 115). 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

127

Atoll User Manual

Important: If the file you first import when you create your custom geo data map is an 8-bit raster map, the Use as and Fields to be imported boxes will not be available for any file that is imported into your new custom geo data map. The values in 8-bit maps are codes and not values such as densities. 10. .Click Import. A new folder is created on the Geo tab of the Explorer window containing the geo data file you imported.

Figure 3.74: The New Type dialogue

3.10.2

Adding a File to a Custom Geo Data Map

Once you have created the custom geo data map by importing the first file, you can add more files that will be part of the custom map. To add a file to an custom geo data map: 1. Select File > Import. The Open dialogue appears. 2. Select the geo data file that you want to add to the custom data map and click Open. If the selected file is a raster file, the File Import dialogue appears (see Figure 3.64). 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 dialogue appears (see Figure 3.67). i. From the Import To list, select the name of the custom geo data map.

ii. Under Fields to be imported, select from the first list which field is to be imported and from the second list whether the imported field is a Density or a Value (see Figure 3.65 on page 115 and Figure 3.66 on page 115). Important: If the file you first imported when you created your custom geo data map was an 8-bit raster map, the Use as and Fields to be imported boxes will not be available for any file that is imported into your new custom geo data map. To use imported data as a surface density value, you must select the Integrable check box.

3. Click Import. The file is added to the custom geo data file on the Geo tab of the Explorer window containing the geo data file you imported.

3.10.3

Managing the Properties of a Custom Geo Data Map

To manage the properties of an custom geo data map: 1. Right-click the custom geo data map on the Geo tab of the Explorer window. 2. Select Properties from the context menu: 3. Depending on the imported file types, the following tabs are available: Description: The Description table lists the classes of all 8-bit raster files contained in the custom geo data map. You must enter a different value for each class. Table: The Table tab enables you to manage the contents of the class table presented on the Description tab. For information on working with the Table tab, see "Adding, Deleting, and Editing Data Table Fields" on page 54. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

128

Chapter 3: Managing Geographic Data Data Mapping: The Data Mapping tab enables you to select which value from each imported vector file is part of the custom geo data map. The imported vector files are listed in the Name column, with the relevant data selected in the Field column. You can change this value by selecting another value from the Field list. If the custom geo data map is marked as integrable (see "Integrable Versus Non Integrable Data" on page 129), there is also a Density check box. If the value in the Field column is to be considered as a density, select the Density check box. Display: The Display tab enables you to define how the custom geo data map appears in the map window. Discrete value and value interval are the available display types. In the Field list, display by value is not permitted if the custom geo data map has: different raster maps with different resolutions both line and polygon vectors both raster and vector maps.

In the Field list, display by density is not permitted if the custom geo data map consists of vector points or lines. For information on using the display tab, see "Display Properties of Objects" on page 32.

3.10.4

Displaying Statistics on Custom Geo Data

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

3.10.5

Integrable Versus Non Integrable Data

Integrable data can be summed over the coverage area defined by the item in a prediction report (for example, by transmitter or threshold). The data can be value data (revenue, number of customers, etc.) or density data (revenue/km, number of customer/km, etc.). For example, if the integrable data comes from a revenue map, a prediction report would indicate: The percentage of coverage for each revenue class for the entire focus zone, and for each single coverage area (transmitter, threshold, etc.), The revenue of the focus zone and of each single coverage area, The percentage of the revenue map covered for the entire focus zone and for each single coverage area.

Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic classes, etc. In the example of a socio-demographic classes map, a prediction report would indicate: The coverage of each socio-demographic class for the entire focus zone and for each single coverage area (transmitter, threshold, etc.)

3.11

Setting the Priority of Geo Data

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

3.11.1

Setting the Display Priority of Geo Data

There are several factors that influence the visibility of geo data: The display check box: The check box immediately to the left of the object name in the Geo tab controls whether or not the object is displayed on the map. If the check box is selected ( ), the object is displayed; if the check box is cleared ( ), the object is not displayed. If the check box, is selected but shaded ( ), not all objects in the

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

129

Atoll User Manual folder are displayed. For more information, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. The order of the layers: The layer at the top of the Geo tab is on top of all other layers in the map window. Data on layers below is only visible where there is no data on the top layer or if you adjust the transparency of the objects on the top layer. You can use drag and drop to change the order of layers by dragging a layer on the Geo tab of the Explorer window towards the top or the bottom of the tab. Note: All objects on the Data tab, such as transmitters, antennas, and predictions, are displayed over all objects on the Geo tab. Vector geo data, however, can be transferred to the Data tab, where they can be placed over data such as predictions. In this way, you can ensure that certain vector geo data, for example, major geographical features, roads, etc., remain visible in the map window For more information, see "Moving a Vector Layer to the Data Tab" on page 125.

The transparency of objects: You can change the transparency of some objects, such as predictions, and some object types, such as clutter classes, to allow objects on lower layers to be visible on the map. For more information, see "Defining the Transparency of Objects and Object Types" on page 35. The visibility range of objects: You can define a visibility range for object types. An object is visible only in the map window if the scale, as displayed on the zoom toolbar, is within this range. For more information, see "Defining the Visibility Scale" on page 35.

In Figure 3.75, 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.

Figure 3.75: Displaying Geo data layers

3.11.2

Setting the Priority of Geo Data in Calculations

The priority of geo data in calculations is determined in much the same way as it is for display. When you make calculations in Atoll, the data taken into account in each folder (Clutter Classes, DTM, etc.) is the data from the top down. In other words, Atoll takes the object on top and objects below only where there is no data in higher levels; what is used is what is seen. Note: The visibility in the context of calculations must not be confused with the display check box ( ). Even if the display check box of an object is cleared ( ), so that the object is not displayed on the map, it will still be taken into consideration for calculations. The only cases where clearing the display check box means that the data will not be used are for population data in reports, and for custom geo data maps.

Object folders, for example, the DTM, clutter classes, clutter heights, and traffic density folders, can contain more than one data object. These objects can represent different areas of the map or the same parts of the map with the same or different resolutions. Therefore for each folder, you should place the objects with the best data at the top. These are normally the

130

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data objects which cover the least area but have the highest resolution. For example, when calculating coverage in an urban area, you might have two clutter class files: one with a higher resolution for the downtown core, where the density of users is higher, and one with a lower resolution but covering the entire area. In this case, by placing the clutter class file for the downtown core over the file with the lower resolution, Atoll can base its calculations for the downtown core on the clutter class file with the higher resolution, using the second file for all other calculations. Population maps and custom geo data maps, both of which can be used in prediction reports follow the same rules of calculation priority. The following sections give several examples to better illustrate how data are used in Atoll: "Example 1: Two DTM Maps Representing Different Areas" on page 131 "Example 2: Clutter Classes and DTM Maps Representing the Same Area" on page 131 "Example 3: Two Clutter Class Maps Representing a Common Area" on page 132.

3.11.2.1

Example 1: Two DTM Maps Representing Different Areas

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

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

Explorer window
Case 1 DTM

Work space

DTM 2 (20m) DTM 1 (50m)

Case 2 DTM

DTM 1 (50m) DTM 2 (20m)

Figure 3.76: Multi-layer management in calculations two DTM maps representing different areas

3.11.2.2

Example 2: Clutter Classes and DTM Maps Representing the Same Area
In this example, there are two imported maps: A clutter class map called Clutter. A DTM map called DTM.

Independently of the order of the two maps in the Explorer window, Atoll uses both the clutter and DTM data in calculations. In Case 1, the clutter class map is on top of the DTM map. In Case 2, the DTM map is on top of the clutter class map. In both Case 1 and Case 2, Atoll will use both the clutter and DTM data in calculations.

Explorer window
Case 1 Clutter classes Clutter DTM DTM Case 2 DTM DTM Clutter classes Clutter

Work space

Figure 3.77: Multi-layer management in calculations Clutter and DTM maps representing the same area

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

131

Atoll User Manual

3.11.2.3

Example 3: Two Clutter Class Maps Representing a Common Area

In this example, there are two imported clutter classes maps: "Clutter 1" represents a large area with a resolution of 50 m. "Clutter 2" represents a smaller area with a resolution of 20 m. This area is also covered by "Clutter 1"

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

Explorer window

Work space

Case 1 Clutter classes Clutter 2 (20m) Clutter 1 (50m)

Case 2 Clutter classes Clutter 2 (50m) Clutter 1 (20m)

Figure 3.78: Multi-layer management in calculations two clutter maps representing the same area

3.12

Displaying Information About Geo Data

You can display information about a geo data map by using tooltips. For information on how to display information in tooltips, see "Defining the Object Type Tip Text" on page 36. To display information about the geo data in a tool tip: Hold the pointer over the geo data until the tool tip appears. The surface area is only given for closed polygons.

Note:

Tool tips only appear when the Display Tips button ( selected.

) on the toolbar has been

3.13

Geographic Data Sets

In Atoll, once you have imported geographic data and defined their parameters, you can save much of this information in a user configuration file. Then, another user, working on a similar Atoll document, can import the configuration file containing the paths to the imported geographic data and many of the defined parameters. When you export the geographic data set, you export: the paths of imported geographic maps map display settings (visibility scale, transparency, tips text, etc.) clutter description (code, name, height, standard deviations, indoor loss, orthogonality factor, percentage pilot finger of each clutter class, default standard deviations, and indoor loss) raster or user profile traffic map description.

In this section, the following are explained: "Exporting a Geo Data Set" on page 133 "Importing a Geo Data Set" on page 133. Note: You can export and import other types of information with user configuration files as well. For information, see the Administrator Manual.

132

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data

3.13.1

Exporting a Geo Data Set

When you export a geo data set in a user configuration file, the information listed in "Geographic Data Sets" on page 132 is saved into an external file. Important: Vectors must be in the same coordinate system as the raster maps. To export a geo data set in a user configuration file: 1. Select Tools > User Configuration > Export. The User Configuration dialogue appears (see Figure 3.79). 2. In the User Configuration dialogue, select the Geographic Data Set check box.

Figure 3.79: The User Configuration dialogue 3. Click OK, The Save As dialogue appears. 4. In the Save As dialogue, browse to the folder where you want to save the file and enter a File name. 5. Click OK.

3.13.2

Importing a Geo Data Set

When you import a user configuration file containing a geo data set, the information listed in "Geographic Data Sets" on page 132 is imported into your current Atoll document. To import a user configuration file containing a geo data set: 1. Select Tools > User Configuration > Import. The Open dialogue appears. 2. Browse to the user configuration file, select it and click Open. 3. The User Configuration dialogue appears. When you import a user configuration file including a geographic data set, Atoll checks if there are already geographic data in the current Atoll document. If so, the option Delete existing geo data appears with other options in the User Configuration dialogue. 4. In the User Configuration dialogue, select the check boxes of the items you want to import. 5. If you already have geographic data in your current Atoll document and would like to replace it with any imported data, select the Delete existing geo data check box. If you do not want to replace existing geo data with imported data, clear the Delete existing geo data check box. 6. Click OK. Note: 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 is the complete path to the user configuration file.

3.14

Editing Geographic Data

In Atoll, you can edit geo data that you have imported or you can create geo data by, for example, adding a vector layer to the Population folder and then adding polygons. The following types of geographic data can be edited: Clutter classes (for more information, "Editing Clutter Class Maps" on page 134)

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

133

Atoll User Manual Contours, lines, and points (for more information, "Editing Polygons, Lines, and Points" on page 46) Population maps (if they are in vector format, i.e., Erdas Imagine (16-bit), AGD, DXF, SHP, MIF, or TAB format) (for more information, "Editing Population or Custom Data Maps" on page 135) Geoclimatic maps (for more information, "Editing Population or Custom Data Maps" on page 135) Traffic data maps Custom data maps (for more information, "Editing Population or Custom Data Maps" on page 135).

3.14.1

Editing Clutter Class Maps

Clutter class maps and certain traffic maps are raster maps. You can edit these maps by creating or modifying polygons. In this section, the following are explained: "Creating a Clutter Polygon" on page 134 "Editing Clutter Polygons" on page 134 "Displaying the Coordinates of Clutter Polygons" on page 135. "Deleting Clutter Polygons" on page 135

3.14.1.1

Creating a Clutter Polygon

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

Figure 3.80: Editor toolbar 4. From the list, select the clutter class for the polygon you want to create. Note: Clutter classes are defined on the Descriptions tab of the clutter classes Properties dialogue.

5. Click the polygon drawing button (

). The pointer changes to a pencil (

).

6. Click once on the map where you want to begin drawing the polygon. 7. Click each time you change angles on the border defining the outside of the polygon. 8. Double-click to close the polygon. Note: You can copy the exact coordinates of a closed polygon by right-clicking it on the map and selecting Properties from the context menu.

3.14.1.2

Editing Clutter Polygons

You can edit clutter polygons by moving existing points of the polygon or by adding or deleting points. To edit clutter polygons: 1. Click the Geo tab in the Explorer window. 2. Right-click the Clutter Classes folder. The context menu appears. 3. Select Edit from the context menu. The Editor toolbar appears (see Figure 3.80). 4. Select the polygon. You can now edit the clutter polygon by: Moving a point: i. Position the pointer over the point you want to move. The pointer changes ( ).

ii. Drag the point to its new position. Adding a point: i. Position the pointer over the polygon border where you want to add a point. The pointer changes ( ).

134

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data 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.

3.14.1.3

Displaying the Coordinates of Clutter Polygons

To display the coordinates of the points defining the polygon area: 1. Click the Geo tab in the Explorer window. 2. Right-click the Clutter Classes folder. The context menu appears. 3. Select Edit from the context menu. The Editor toolbar appears (see Figure 3.80). 4. Right-click the polygon and select Properties from the context menu. The Properties dialogue appears with the coordinates of the points defining the polygon and the total area. Note: You can select and copy the coordinates displayed in the Properties dialogue of the polygon.

3.14.1.4

Deleting Clutter Polygons

You can delete clutter polygons. To delete a clutter polygon: 1. Click the Geo tab in the Explorer window. 2. Right-click the Clutter Classes folder. The context menu appears. 3. Select Edit from the context menu. The Editor toolbar appears (see Figure 3.80). 4. Click the polygon deletion tool ( ). The pointer changes ( ).

5. Click the polygon you want to delete. The polygon is deleted.

3.14.2

Editing Population or Custom Data Maps

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

Tip:

You can also activate the vector tools by selecting the vector layer to edit from the Vector Edition toolbar list. Because Atoll names all new vector layers "Vectors" by default, it might be difficult to know which Vectors folder you are selecting. By renaming each vectors folder, you can ensure that you select the correct folder. For information on renaming objects, see "Renaming an Object" on page 29. ) on the Vector Edition toolbar:

6. To draw a polygon, click the New Polygon button (

a. Click once on the map where you want to begin drawing the contour. b. Click each time you change angles on the border defining the outside of the contour. c. Double-click to close the contour. 7. To draw a rectangle, click the New Rectangle button ( ) on the Vector Edition toolbar:

a. Click the point on the map that will be one corner of the rectangle. b. Drag to the opposite corner of the rectangle. c. Release the mouse to create the rectangle defined by the two corners. 8. Right-click the new polygon or rectangle and select Properties from the context menu. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

135

Atoll User Manual 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. ) or the New Rectangle ( ) button on the Vector Edition toolbar.

10. Press ESC to deselect the New Polygon (

11. For Atoll to consider the new vector layer as part of the data map, you must map the vector layer. Right-click the the Population, or the Custom Data folder. The context menu appears. 12. Select Properties from the context menu. The Properties dialogue appears. 13. Click the Data Mapping tab. For the following geo data: Population Map: i. In the Field column, "Population" is selected by default.

ii. If the vector layer contains a population density, select the check box in the Density column. If the vector layer indicates the number of inhabitants, and not the population density, clear the check box in the Density column. Custom Data Map: The data you map will depend on the type of custom data map you created.

You can edit the vector objects as explained in "Editing Polygons, Lines, and Points" on page 46.

3.15

Saving Geographic Data

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

This section explains the following: "Saving Modifications to an External File" on page 136 "Updating the Source File" on page 138 "Combining Several Files into One File" on page 138 "Exporting an Embedded File" on page 138 "Creating a New File from a Larger File" on page 139

3.15.1

Saving Modifications to an External File

In Atoll, you can save your modifications to an external file. This section explains the following: "Exporting an Edited Clutter Class Map in a Raster-Format File" on page 136 "Exporting an Edited Vector Layer in Vector-Format File" on page 137.

3.15.1.1

Exporting an Edited Clutter Class Map in a Raster-Format File

You can export clutter class modifications in a raster-format file, either in the same format as used in the current Atoll document, or in a different raster format. You can also choose to export the entire clutter class geo data, the part containing the computation zone, or just your modifications to the geo data. When you have made modifications to a raster-format geo data file, exporting either the entire geo data or just your modifications allows you to save those modifications to an external file. To export clutter class modifications in a raster-format file: 1. Click the Geo tab of the Explorer window. 2. Right-click the Clutter Classes folder. 3. Select Save As from the context menu. The Save As dialogue appears. 4. In the Save As dialogue, browse to the folder where you want to save the file, enter a name for the file, and select the file format from the Save as type list. You can select from one of the following file formats: BMP: When you select bitmap format, Atoll automatically creates the corresponding BPW file containing the georeference information. TXT: The ArcView text format is intended only for export; no corresponding geo-reference file is created. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

136

Chapter 3: Managing Geographic Data TIF: When you select tagged image file format, Atoll automatically creates the corresponding TFW file containing the georeference information. BIL: When you select the BIL format, Atoll automatically creates the corresponding HDR file containing the georeference information. When exporting in BIL format, Atoll allows you to export files larger than 2 Gb. JPEG 2000: When you select the JPEG 2000 format, no corresponding geo-reference file is created. GRC or GRD: Files with the extension GRC or GRD are Vertical Mapper files. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 Gb.

5. Click Save. The Export dialogue appears (see Figure 3.81).

Figure 3.81: Export dialogue 6. Under Region, select one of the following: The Entire Project Area: This option allows you to export the entire clutter class geo data file, including any modifications you have made to the geo data. The exported geo data file will replace the geo data file in the current Atoll document. Only Pending Changes: This option allows you to export a rectangle containing any modifications you have made to the clutter classes. The exported geo data file will be added as a new object to the Clutter Classes geo data folder. The Computation Zone: This option allows you to export the clutter class geo data contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible. The exported geo data file will be added as a new object to the selected geo data folder.

7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. The suggested resolution value is defined by the following criteria: If one object has been modified, the suggested resolution is the resolution of the modified object. If several objects have been modified, the suggested resolution is the highest resolution of the modified objects. If there is no initial clutter class object, the resolution will equal the highest resolution of the DTM maps. If the Atoll document in which you created the clutter class file has no DTM, no other clutter class geo data file, or traffic objects, the suggested resolution is 100 m.

8. Click OK. The selected data is saved in an external file.

3.15.1.2

Exporting an Edited Vector Layer in Vector-Format File

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

Once you save a vector layer, the exported file replaces the vector layer as a linked file. You can embed the file afterwards (see "Embedding Geographic Data" on page 119). To export a vector layer: 1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Save As from the context menu. The Save As dialogue appears. 3. In the Save As dialogue, browse to the folder where you want to save the file, enter a name for the file, and select the file format from the Save as type list. You can select from one of the following file formats: AGD: The Atoll Geographic Data format is an Atoll-specific format. As a format created for Atoll, Atoll can read AGD files faster than the other supported vector formats. SHP: The ArcView vector format should be used for vector layers containing only polygons; it cannot save vectors made of lines or points. If you have a vector layer with vector lines or points, use either the AGD, the MIF or the TAB format. MIF and TAB: MapInfo formats.

4. Click Save in the Save As dialogue. The Vector Export dialogue appears, displaying the current coordinate system and allowing you to change the coordinate system by clicking Change. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

137

Atoll User Manual 5. Click Export. The vector layer is saved in the format and with the name you specified and the exported file replaces the vector layer in the current document as a linked file.

3.15.2

Updating the Source File

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

3.15.3

Combining Several Files into One File

In certain circumstances, for example, after importing an MSI Planet index file, you may have several geo data files of the same type. You can combine these separate files to create one single file. The files will be combined according to their order from the top down in the folder on the Geo tab of the Explorer window. If the files overlap on the map, the combined file will show the file on the top. You can create a one file from a section of the following geo data types: Digital terrain model Clutter classes Clutter heights Scanned maps

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

3.15.4

Exporting an Embedded File

You can export an embedded geo data file to be used in a different Atoll document, or in a different application. When you export an embedded file, Atoll replaces the embedded file in the current Atoll document with the newly exported file. To export an embedded geo data file: 1. Click the Geo tab in the Explorer window. 2. Right-click the folder of the embedded geo data file you want to export. The context menu appears. 3. Select Save As from the context menu. The Save As dialogue appears. 4. Enter a File name and select a file type from the Save as type list. 5. Click OK. If the geo data file is a vector file, the Vector Export dialogue appears (see Figure 3.82).

138

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 3: Managing Geographic Data

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

Figure 3.83: Export dialogue a. Under Region, select one of the following: The Entire Project Area: This option allows you to export the entire raster-format geo data file, including any modifications you have made to the geo data. The exported file will replace the embedded file in the Geo data tab. Only Pending Changes: This option allows you to export a rectangle containing any modifications you have made to the geo data. The exported file will be added as an object in the geo data folder. The Computation Zone: This option allows you to export the geo data contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible. The exported file will be added as an object in the geo data folder.

b. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. c. Click OK. The selected data is saved in an external file.

3.15.5

Creating a New File from a Larger File

You can create a new file from a section of a larger file. You can use this new file in the same Atoll document, or in a new Atoll document. To create a new file, you must first define the area by creating a computation zone. You can create a new file from a section of the following geo data types: Digital terrain model Clutter classes Clutter heights Scanned maps Population Geoclimatic maps

To create a new file from a section of a larger file: 1. Click the Geo tab in the Explorer window. 2. Right-click the folder of the embedded geo data file you want to export. The context menu appears. 3. Select Save As from the context menu. The Save As dialogue appears. 4. Enter a File name and select a file type from the Save as type list. 5. Click OK. The Export dialogue appears (see Figure 3.82).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

139

Atoll User Manual 6. Under Region, select The Computation Zone. This option allows you to export the geo data contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible. The exported geo data file will be added as a new object to the selected geo data folder. 7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. 8. Click OK. The selected data is saved as a new file.

140

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 4
Antennas and Equipment

RF Planning & Optimisation Software

Atoll

Chapter 4: Antennas and Equipment

Antennas and Equipment

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

4.1

Working With Antennas

Atoll enables you to work with antennas in many ways. To create a new antenna, you can import the data necessary from external sources, such as from a spreadsheet or from a Planet-format file. Once you have created an antenna, you can improve signal level prediction by smoothing the high-attenuation points of the vertical pattern. In this section, the following are explained: "Creating an Antenna" on page 143 "Importing Planet-Format Antennas" on page 144 "Importing 3-D Antenna Patterns" on page 145 "Smoothing an Antenna Pattern" on page 146.

4.1.1

Creating an Antenna
Each Atoll project template has antennas specific to the technology supported by the template. As well, Atoll allows you to create antennas and set the parameters such as manufacturer, gain, horizontal pattern, and vertical pattern.

Tip: To create an antenna:

When you create a new antenna, you can copy the horizontal and vertical antenna patterns from a spreadsheet or word processor.

1. Click the Data tab in the Explorer window. 2. Right-click on the Antennas folder. The context menu opens. 3. Select New from the context menu. A properties dialogue appears. 4. Click the General tab. You can enter information in the following fields: Name: Atoll automatically enters a default name for each new antenna. You can modify the name Atoll enters if you wish. Manufacturer: The name of the antenna manufacturer. Gain: The antennas isotropic gain. Pattern Electrical Tilt: The antennas electrical tilt. This field is for information only; for an antennas electrical tilt to be taken into consideration in calculations, it must be integrated into the horizontal and vertical patterns. Atoll automatically calculates the pattern electrical tilt if the Pattern Electrical Tilt field is left blank or has a value of "0." Note: If you use the same antenna several times but with a different electrical tilt, you must create a new antenna with corresponding patterns for each electrical tilt.

Comments: Any additional information on the antenna.

5. Click the Horizontal Pattern tab. The Horizontal Pattern tab has a table describing the horizontal antenna pattern in terms of the attenuation in dB (Att.) per Angle and a graphical representation of the pattern. Atoll allows you to enter antenna pattern attenuations for as many as 720 angles. Therefore, attenuation values can also be defined for angles other than integer values from 0 to 359. If you have the horizontal pattern in a spreadsheet or text document, you can copy the data directly into the table: a. Switch to the document containing the horizontal pattern. b. Select the columns containing the angles and attenuation values of the horizontal pattern. c. Copy the selected data.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

143

Atoll User Manual

Figure 4.84: Copying horizontal pattern values d. Switch to Atoll. e. Click the upper-left cell of the horizontal pattern. f. Press CTRL+V to paste the data in the table. If there are some blank rows in your data sheet, Atoll will interpolate the values in order to obtain a complete and realistic pattern. When performing a calculation along an angle for which no data is available, Atoll calculates a linear interpolation from the existing pattern values.

g. Click Apply to display the pattern. 6. Click the Vertical Pattern tab. The Vertical Pattern tab has a table describing the vertical antenna pattern in terms of the attenuation in dB (Att.) per Angle and a graphical representation of the pattern. Atoll allows you to enter antenna pattern attenuations for as many as 720 angles. Therefore, attenuation values can also be defined for angles other than integer values from 0 to 359. If you have the vertical pattern in a spreadsheet or text document, you can copy the data directly into the table as described in step 5. 7. Click the Other Properties tab. You can define the following fields (not used in any calculation): Beamwidth: In a plane containing the direction of the maximum lobe of the antenna pattern, the angle between the two directions in which the radiated power is one-half the maximum value of the lobe. Translated in terms of dB, half power corresponds to -3 dB. In this window, you may enter this angle in degrees. FMin: The minimum frequency that the antenna is capable of emitting. FMax: The maximum frequency that the antenna is capable of emitting.

8. Click OK. Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are correctly aligned when: the horizontal pattern attenuation at 0 is the same as the vertical pattern attenuation at the pattern electrical tilt angle, and the horizontal pattern attenuation at 180 is the same as the vertical pattern attenuation at the 180 less the pattern electrical tilt angle.

4.1.2

Importing Planet-Format Antennas

In Atoll, you can import Planet-format antennas by importing an index file listing the individual antenna files to be imported. Standard Atoll fields are directly imported. Other fields are imported for information only and are accessible on the Other Properties tab of the Antenna Properties dialogue. If you are working with a database, you will have to create the fields in the table below in the database before you import the Planet-format antennas:

Field
FREQUENCY H_WIDTH V_WIDTH FRONT_TO_BACK TILT

Definition
The design frequency of the antenna The azimuth beamwidth The elevation beamwidth The ratio of forward antenna gain at 0 and 180 degree elevation Indicates whether the antenna is to be electrically or mechanically tilted

Other fields available in the Planet-format antenna files that you wish to import in Atoll can be created in the database before importing. Atoll imports all the custom fields as long as the field data in the antenna file matches the field type in the database. For more information on working with databases, see The Administrator Manual.

144

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

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

4.1.3

Importing 3-D Antenna Patterns

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

To import three-dimensional antenna pattern files: 1. Select the Data tab in the Explorer window. 2. Right-click the Antennas folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the file to import. 5. Click Open. The Setup dialogue appears (see Figure 4.85).

Figure 4.85: Importing a 3-D antenna pattern

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

145

Atoll User Manual 6. If you already have an import configuration defining the data structure of the imported file, you can select it from the Configuration list. If you do not have an import configuration, continue with step 7. a. Under Configuration, select an import configuration from the Configuration list. b. Continue with step 10. 7. Under Name, you can define a name for the imported antenna pattern. This name will appear in the Antennas folder on the Data tab. If no name is defined, Atoll will use the file name as the name of the antenna: If the name of the antenna is in the file, check the Value read in the file check box and enter a Keyword identifying the name value in the file. If you want to enter a name for the antenna, clear the Value read in the file check box and enter a name.

8. Under Gain, you can define the antenna gain. If no gain is defined, Atoll will assume that the gain is "0." If the gain of the antenna is in the file, check the Value read in the file check box and enter a Keyword identifying the gain value in the file. If you want to enter a gain for the antenna, clear the Value read in the file check box and enter a gain value.

9. 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.

10. 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. Note: You can save the choices you have made in the Setup dialogue as a configuration file by clicking the Save button at the top of the dialogue and entering a name for the configuration. The next time you import a three-dimensional antenna pattern file, you can select the same settings from the Configuration File list.

11. Click Import. The antenna patterns are imported into the current Atoll document.

4.1.4

Smoothing an Antenna Pattern

Empirical propagation models, such as the Standard Propagation Model (SPM), require antenna pattern smoothing in the vertical plane to better simulate the effects of reflection and diffraction, which, therefore, improves signal level prediction. In Atoll, you can smooth antennas vertical as well as horizontal patterns. Important: You should make a copy of the antenna before smoothing its vertical pattern. You can make a copy of the antenna by opening the Antennas table and copying and pasting the antenna data into a new row. For information on data tables, see "Working with Data Tables" on page 53. To smooth the vertical or horizontal pattern of an antenna: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Antennas folder.

3. Right-click the antenna whose pattern you want to smooth. The context menu appears. 4. Select Properties from the context menu. 5. Select the Vertical Pattern or the Horizontal Pattern tab. 6. Right-click the graphical representation of the pattern. The context menu appears. 7. Select Smooth from the context menu. The Smoothing Parameters dialogue appears. 8. Enter the following parameters and click OK to smooth the vertical pattern: Max Angle: Enter the maximum angle. Smoothing will be applied to the section of the vertical pattern between 0 and the maximum angle (clock-wise). Peak-to-Peak Deviation: Enter the attenuation values to which smoothing will be applied. Atoll will smooth all attenuation values greater than or equal to the peak-to-peak deviation with the defined correction factor. Correction: Enter the correction factor by which the attenuation values will be smoothed.

9. Click OK.

146

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 4: Antennas and Equipment

4.1.5

Printing an Antenna Pattern

You can print the horizontal or vertical pattern of an antenna. To print an antenna pattern: 1. Click the Data tab of the Explorer window. 2. Open the Antennas table: a. Right-click the Antennas folder. b. Select Open Table from the context menu. 3. Right-click the antenna whose pattern you want to print. 4. Select Record Properties from the context menu. The Properties dialogue appears. 5. Select the Horizontal Pattern tab or the Vertical Pattern tab. 6. Right-click the antenna pattern and select Linear or Logarithmic from the context menu. 7. Right-click the antenna pattern and select Print from the context menu.

4.2

Working With Equipment

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

4.2.1

Defining TMA Equipment

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

4.2.2

Defining Feeder Cables

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

147

Atoll User Manual

4.2.3

Defining BTS Equipment

The BTS is modelled for UMTS, CDMA2000, TD-SCDMA, WiMAX, and LTE. In GSM, only the downlink losses are modelled. Once you have defined a BTS, it can be assigned to individual transmitters. To create a base transceiver station: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Equipment > BTS Equipment from the context menu. The BTS Equipment table appears. 4. In the table, create one BTS per row. For information on data tables, see "Working with Data Tables" on page 53. For each BTS, enter: Name: Enter a name for the BTS. This name will appear in other dialogues when you select a BTS. Noise Figure (dB): Enter the noise figure for the BTS. This value is not used in GSM GPRS EGPRS documents. Downlink Losses Due to the Configuration (dB): Enter the losses on downlink due to the BTS configuration. Uplink Losses Due to the Configuration (dB): Enter the losses on uplink due to the BTS configuration. This value is not used in GSM GPRS EGPRS documents. Rho Factor (%): Enter the Rho factor, as a percentage. The Rho factor enables Atoll to take into account self-interference produced by the BTS. 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 signal-tonoise ratio in the downlink. This value is only used in CDMA based technologies (CDMA2000, UMTS, and TD-SCDMA). It is not used in GSM, WiMAX, and LTE documents.

4.2.4

Updating the Values for Total Losses and the BTS Noise Figure for Transmitters
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 BTS as the reference point when evaluating total losses and the total noise figure. The BTS noise figure used by Atoll is the one specified in the BTS properties. Transmitter reception losses include feeder reception losses, connector reception losses, miscellaneous reception losses, antenna diversity gain, TMA benefit gain (as calculated using the Friis equation), and an additional loss modelling the noise rise generated from repeaters (if any). Transmitter transmission losses include feeder transmission losses, connector transmission losses, miscellaneous transmission losses, and TMA transmission losses. For more information on the total noise figure and on transmitter reception and transmission losses, see the Technical Reference Guide. You can assign equipment to a transmitter: Using the Equipment Specifications dialogue, available by clicking the Equipment button on the Transmitter tab of the transmitters Properties dialogue, or Using the Transmitters table, available by right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Open Table from the context menu.

When you assign equipment to a transmitter using the Equipment Specifications dialogue, Atoll updates the real values when you click OK and close the dialogue. When you assign equipment to a transmitter using the Transmitters table, Atoll does not update the real values automatically. To update the real values (total losses and the BTS noise figure) with the computed values of all transmitters: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Equipment > Recalculate Losses and Noise Figure from the context menu. To update the real values (total losses and the BTS noise figure) with the computed values of a group of transmitters: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters. The objects in the folder are grouped by that property. 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.

148

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 4: Antennas and Equipment 7. In the Transmitters table, select the values you want to update in the following columns and press DEL: Transmission Loss (dB) Reception Loss (dB) BTS Noise Figure (dB)

Atoll automatically recalculates and updates these values. in

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

149

Atoll User Manual

150

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5
Managing Calculations in Atoll

RF Planning & Optimisation Software

Atoll

Atoll User Manual

152

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

Managing Calculations in Atoll

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

5.1

Working with Propagation Models

In the section, the following are explained: "Propagation Model Characteristics: Overview" on page 153 "The Standard Propagation Model" on page 154 "The Okumura-Hata Propagation Model" on page 160 "The Cost-Hata Propagation Model" on page 161 "The ITU 529-3 Propagation Model" on page 162 "The ITU 370-7 Propagation Model" on page 164 "The Erceg-Greenstein Propagation Model" on page 164 "The ITU 526-5 Propagation Model" on page 165 "The WLL Propagation Model" on page 165 "The Longley-Rice Propagation Model" on page 166 "The ITU 1546 Propagation Model" on page 166 "The Sakagami Extended Propagation Model" on page 167 "Managing Propagation Models" on page 167.

5.1.1

Propagation Model Characteristics: Overview

Each propagation model available in Atoll is suited for certain conditions, frequencies and radio technologies. The following table summarises the frequency band, necessary geo data, recommended use of each propagation model.

Model

Frequency Range
100 400 MHz

Geo Data Taken into Account

Recommended Use
d > 10 km Low frequencies Broadcast 1 < d < 1000 km Land and maritime mobile, broadcast Fixed receivers WLL Fixed receivers WLL, Microwave links, WiMAX 1 < d < 20 km GSM 900, CDMA2000, LTE

ITU 370-7 Vienna 93

Terrain profile

ITU 1546

30 3000 MHz

Terrain profile

ITU 526-5 (theoretical) WLL Okumura-Hata (Automatic calibration available) Cost-Hata (Automatic calibration available) ITU 529-3

30 10000 MHz 30 10000 MHz

Terrain profile Terrain profile Deterministic clutter Terrain profile Statistical clutter (at the receiver)

150 1000 MHz

1500 2000 MHz

Terrain profile Statistical clutter (at the receiver) Terrain profile Statistical clutter (at the receiver)

1 < d < 20 km GSM 1800, UMTS, CDMA2000, LTE 1 < d < 100 km GSM 900, CDMA2000, LTE

300 1500 MHz

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

153

Atoll User Manual

Model
Standard Propagation Model

Frequency Range

Geo Data Taken into Account

Recommended Use

150 3500 MHz (Automatic calibration available) Erceg-Greenstein (SUI) Sakagami Extended (Automatic calibration available) 3000 8000 MHz 1900 6000 MHz

Terrain profile Statistical clutter

1 < d < 20 km GSM, UMTS, CDMA2000, WiMAX, LTE Urban and suburban areas 100 m < d < 8 km Fixed WiMAX 1 < d < 20 km WiMAX

Terrain profile Statistical clutter (at the receiver)

Terrain profile Statistical clutter

5.1.2

The Standard Propagation Model

The Standard Propagation Model is a propagation model based on the Hata formulas and is suited for predictions in the 150 to 3500 MHz band over long distances (from one to 20 km). It is best suited to GSM 900/1800, UMTS, and CDMA2000 radio technologies. The Standard Propagation Model is based on the following formula: K 1 + K 2 Log ( d ) + K 3 Log ( H Txeff ) + K 4 DiffractionLoss + K 5 Log ( d ) Log ( H Txeff ) + P R = P Tx K 6 H Rx + K 7 Log ( H Rx ) + K clutter f ( clutter ) + K hill, LOS
eff eff

where: PR PTx K1 K2 d K3 H Tx K4
eff

received power (dBm) transmitted power (EIRP) (dBm) constant offset (dB) multiplying factor for Log(d) distance between the receiver and the transmitter (m) multiplying factor for Log(HTxeff) effective height of the transmitter antenna (m)

multiplying factor for diffraction calculation. K4 must be a positive number DiffractionLoss losses due to diffraction over an obstructed path (dB) K5 multiplying factor for Log(HTxeff) x Log(d) multiplying factor for HRxeff multiplying factor for Log(HRxeff)
eff

K6 K7 H Rx Kclutter f(clutter) Khill, LOS

mobile antenna height (m) multiplying factor for f(clutter) average of weighted losses due to clutter corrective factor for hilly regions (=0 in case of NLOS)

These parameters can be defined on the tabs (Parameters, and Clutter) of the Standard Propagation Model Properties dialogue. You can also calibrate the Standard Propagation Model using a wizard. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide. In this section, the following are explained: "Recommendations for Working with the Standard Propagation Model" on page 154 "Calculating Diffraction With the SPM" on page 155 "Sample Values for SPM Formulas" on page 156 "Calculating f(clutter) with the Standard Propagation Model" on page 156 "Modelling Fixed Receivers" on page 157 "Defining the Parameters of the Standard Propagation Model" on page 157.

5.1.2.1

Recommendations for Working with the Standard Propagation Model

It is important to remember that clutter information can be taken into consideration in both diffraction loss and f(clutter). To avoid taking clutter information into account twice, you should choose one of the following approaches: Approach #1: If you specify losses per clutter class, do not consider clutter altitudes in diffraction loss over the transmitter-receiver profile. This approach is recommended if the clutter height information is statistical (i.e., where the clutter is roughly defined and without a defined altitude).

154

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

Note:

Because the Standard Propagation Model is a statistical propagation model, using this approach is recommended.

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

Figure 5.86: Diffraction caused by surrounding buildings when the receiver is indoors

5.1.2.2

Calculating Diffraction With the SPM

You can set the parameters used to calculate diffraction losses on the Parameters and Clutter tabs of the Standard Propagation Model Properties dialogue. On the Parameters tab, you can define the calculation method used for diffraction and the K4 factor. The methods available are: Deygout Epstein-Peterson Deygout with correction Millington

For detailed information on each method, see the Technical Reference Guide. The methods for calculating diffraction are based on the general method for one or more obstacles described in the ITU 526-5 recommendations. The calculations take the curvature of the earth into account. Along the transmitter-receiver profile, you can choose to take either the ground altitude only or both the ground altitude and the clutter height into account. If you choose to take clutter height into account, Atoll uses the clutter height information in the clutter heights file. Otherwise, it uses average clutter height specified for each clutter class in the clutter classes. When the clutter height information is statistical, Atoll also uses clearance values per clutter class to model streets.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

155

Atoll User Manual To take heights into account when calculating diffraction: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Standard Propagation Model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Clutter tab. 6. Under Heights, select one of the following for Clutter taken into account in diffraction: 1 - Yes: Select "1 - Yes" if you want heights from the clutter heights to be taken into account on top of the DTM when calculating diffraction. 0 - No: Select "0 - No" if you want diffraction to be calculated using only the DTM.

7. Click OK.

5.1.2.3

Sample Values for SPM Formulas

The following table gives some possible values for the constants used in the Standard Propagation Model formulas.

Minimum K1 K2 K3 K4 K5 K6 K7
Variable 20 -20 0 -10 -1 -10

Typical
Variable 44.9 5.83 0.5 -6.55 0 0

Maximum
Variable 70 20 0.8 0 0 0

K1 is a constant; its value depends on the radio frequency and on the radio technology. The following table gives some possible values for K1.

Project Type
GSM 900 GSM 1800 GSM 1900 UMTS 1xRTT

Frequency (MHz)
935 1805 1930 2110 1900 2300 2500

K1
12.5 22 23 23.8 23 24.7 25.4 26.1 27.8 28.3

WiMAX

2700 3300 3500

Its value is heavily influenced by the values given to losses per clutter class.

5.1.2.4

Calculating f(clutter) with the Standard Propagation Model

The average of weighted losses due to clutter, f(clutter), is defined as follows: f ( clutter ) = where L: loss due to clutter. w: weight. n: number of points taken into account over the profile.

i=1

Li wi

156

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll The losses due to clutter are calculated for the maximum distance from the receiver, defined as Maximum Distance on the Clutter tab of the Standard Propagation Model Properties dialogue. When the Maximum Distance is defined as "0", Atoll only considers the losses on the pixel where the receiver is located. On the Clutter tab, each clutter class is assigned losses and a weighting function, enabling Atoll to give a weight to each point. For more information, see the Technical Reference Guide. Note: 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
Dense urban Woodland Urban Suburban Industrial Open in urban Open Water

Losses (dB)
from 4 to 5 from 2 to 3 0 from -5 to -3 from -5 to -3 from -6 to -4 from -12 to -10 from -14 to -12

Note:

The Standard Propagation Model is based on Hata formulas, which are valid for an urban environment. The values above are consistent with an urban environment because losses of 0 dB are indicated for an urban clutter class, with positive values for more dense clutter classes and negative values for less dense clutter classes.

5.1.2.5

Modelling Fixed Receivers

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

5.1.2.6

Defining the Parameters of the Standard Propagation Model

You can define the parameters of the Standard Propagation Model using the Standard Propagation Model Properties dialogue. Note: Default values have been assigned to the multiplying factors. The default values correspond to the rural (quasi-open) Okumura-Hata formula valid for a frequency of 935 MHz. The values for K values can be calculated using an automatic or assisted calibration method. For more information, see the Measurements and Model Calibration Guide.

To define the calculations parameters of the Standard Propagation Model: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Standard Propagation Model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab (see Figure 5.87).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

157

Atoll User Manual

Figure 5.87: Standard Propagation Model - Parameters tab Under Near Transmitter, you can set the following parameters: Maximum Distance: Set the maximum distance for a receiver to be considered near the transmitter. If the distance between the receiver and the transmitter is greater than the set distance, the receiver is considered far from the transmitter. K1 - los and K2 - los: Enter the K1 and K2 values that will be used for calculations when the receiver is in the transmitter line of sight. K1 - nlos and K2 - nlos: Enter the K1 and K2 values that will be used for calculations when the receiver is not in the transmitter line of sight.

Under Far from Transmitter, the values you set will be used for all receivers whose distance from the transmitter is greater than the distance specified in Maximum Distance under Near Transmitter. You can set the following parameters: K1 - los and K2 - los: Enter the K1 and K2 values that will be used for calculations when the receiver is in the transmitter line of sight. K1 - nlos and K2 - nlos: Enter the K1 and K2 values that will be used for calculations when the receiver is not in the transmitter line of sight. Note: 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. Note: 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.

Under Diffraction, you can set the following parameters: Method: Select the method that will be used to calculate diffraction. K4: Enter the K4 value.

158

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

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

6. Click the Clutter tab (see Figure 5.88).

Figure 5.88: Standard Propagation Model - Clutter tab Under Clutter Taken into Account, you can set the following parameters under Heights: 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 the receiver to be considered to be located on top of clutter. This option can be used where fixed receivers are located on top of buildings.

Under Clutter Taken into Account, you can set the following parameters under Range: Max. distance: Set the maximum distance from a receiver to be considered when calculating f(clutter). Weighting function: Select a weighting function to be used when calculating f(clutter). It enables you to weight losses for each pixel between a receiver and a maximum distance. For more information on weighting functions, see the Technical Reference Guide.

Under Parameters per clutter class, you can set the following parameters for each clutter class: Losses: Enter, if desired, losses for each clutter class to be considered when calculating f(clutter). Clearance: Enter, if desired, a clearance around each receiver for each clutter class. The clearance information is used to model streets because it is assumed that the receiver is in the street. The clearance is used when calculating diffraction when statistical clutter is taken into account.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

159

Atoll User Manual Rx Height: Enter, if desired, a specific receiver height for each clutter class. Or, you can select "(default)" for the receiver height. When creating a coverage prediction, Atoll will then read the receiver height on the Receiver tab of the Properties dialogue for the Predictions folder.

7. Click OK.

5.1.3

The Okumura-Hata Propagation Model

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

5.1.3.1

Defining General Settings (Okumura-Hata)

To set general parameters on the Okumura-Hata propagation model: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Okumura-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. You can modify the following settings: Add diffraction loss: The Okumura-Hata propagation model can take into account losses due to diffraction, using a 1-knife-edge Deygout method, and using the ground altitude given in the DTM. For detailed information on the Deygout method, see the Technical Reference Guide. The calculations take the curvature of the earth into account. Select "1 - Yes" if you want the propagation model to add losses due to diffraction. You can weight this diffraction for each Hata environment formula (See "Creating or Modifying Environment Formulas (Okumura-Hata)" on page 161) 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.

6. Click OK.

5.1.3.2

Selecting an Environment Formula (Okumura-Hata)

The Okumura-Hata propagation model can use an environment formula appropriate to each clutter class when calculating. You can assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. To select environment formulas: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Okumura-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Under Formulas assigned to clutter classes, select the Default formula row. Under this grid, choose the appropriate formula in the formula scrolling list. Atoll uses the default environment formula for calculations on any clutter class to which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. 7. For each clutter class under Formulas assigned to clutter classes, select a formula from the list. 8. For each clutter class under Additional Losses per Clutter Class, enter an optional correction (in dB). This correction acts as an additional loss on the loss calculated by the chosen formula. For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (OkumuraHata)" on page 161. 9. Click OK.

160

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

Note:

Correction terms can be evaluated using the Automatic Calibration Wizard. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.

5.1.3.3

Creating or Modifying Environment Formulas (Okumura-Hata)

Several environment formulas are available with the Okumura-Hata propagation model to model different environments. You can modify existing environment formulas used by the Okumura-Hata propagation model or create new environmental formulas. To create or modify an environment formula: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Okumura-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Click the Formulas button. The Formulas dialogue appears. You can do the following: Add: To create a new formula, click the Add button and modify the parameters of the formula. Delete: To delete a formula, select the formula and click the Delete button. Modify: To modify an existing formula, select the formula and modify the parameters.

7. Click OK to save your changes and close the Formulas dialogue. 8. Click OK. Notes: You can weight the diffraction loss by setting the diffraction multiplying factor within the range ]0;1]. Constant values and diffraction multiplying factor can be evaluated using the Automatic Calibration Wizard for each environment formula. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.

5.1.4

The Cost-Hata Propagation Model

The Cost-Hata model is suited for coverage predictions in the 1500 to 2000 MHz band over long distances (from one to 20 km). It is best suited to DCS 1800 and UMTS radio technologies. Hata models in general are well adapted to the urban environment. You can define several corrective formulas and associate a formula with each clutter class to adapt the Hata model to a wide variety of environments. You can also define a default formula to be used when no land use data is available. In this section, the following are explained: "Defining General Settings (Cost-Hata)" on page 161 "Selecting an Environment Formula (Cost-Hata)" on page 162 "Creating or Modifying Environment Formulas (Cost-Hata)" on page 162.

5.1.4.1

Defining General Settings (Cost-Hata)

To set general parameters on the Cost-Hata propagation model: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Cost-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. You can modify the following settings: Add diffraction loss: The Cost-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 (CostHata)" on page 162) 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.

6. Click OK. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

161

Atoll User Manual

5.1.4.2

Selecting an Environment Formula (Cost-Hata)

The Cost-Hata propagation model can use an environment formula appropriate to each clutter class when calculating. You can assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. To select environment formulas: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Cost-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Under Formulas assigned to clutter classes, select the Default formula row. Under this grid, choose the appropriate formula in the formula scrolling list. Atoll uses the default environment formula for calculations on any clutter class to which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. 7. For each clutter class under Formulas assigned to clutter classes, select a formula from the list. 8. For each clutter class under Additional Losses per Clutter Class, enter an optional correction (in dB). This correction acts as an additional loss on the loss calculated by the chosen formula. 9. Click OK.

5.1.4.3

Creating or Modifying Environment Formulas (Cost-Hata)

Several environment formulas are available with the Cost-Hata propagation model to model different environments. You can modify existing environment formulas used by the Cost-Hata propagation model or create new environmental formulas. To create or modify an environment formula: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Cost-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Click the Formulas button. The Formulas dialogue appears. You can do the following: Add: To create a new formula, click the Add button and modify the parameters of the formula. Delete: To delete a formula, select the formula and click the Delete button. Modify: To modify an existing formula, select the formula and modify the parameters.

7. Click OK to save your changes and close the Formulas dialogue. 8. Click OK. Notes: You can weight the diffraction loss by setting the diffraction multiplying factor within the range ]0;1]. Constant values and diffraction multiplying factor can be evaluated using the Automatic Calibration Wizard for each environment formula. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.

5.1.5

The ITU 529-3 Propagation Model

The ITU 529-3 model is suited for predictions in the 300 to 1500 MHz band over long distances (from one to 100 km). It is best suited to the GSM 900 radio technology. Hata models in general are well adapted to the urban environment. You can define several corrective formulas and associate a formula with each clutter class to adapt the Hata model to a wide variety of environments. You can also define a default formula to be used when no land use data is available. In addition, for long distances 20km<d<100 km), the model uses automatically a corrective formula as defined in the recommendation. In this section, the following are explained: "Defining General Settings (ITU 529-3)" on page 163 "Selecting an Environment Formula (ITU 529-3)" on page 163 "Creating or Modifying Environment Formulas (ITU 529-3)" on page 163.

162

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

5.1.5.1

Defining General Settings (ITU 529-3)

To set general parameters on the ITU 529-3 propagation model: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click ITU529. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. You can modify the following settings: Add diffraction loss: The ITU 529-3 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 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.

6. Click OK.

5.1.5.2

Selecting an Environment Formula (ITU 529-3)

The ITU 529-3 propagation model can use an environment formula appropriate to each clutter class when calculating. You can assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. To select environment formulas: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click ITU529. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Under Formulas assigned to clutter classes, select a Default formula. Atoll uses the default environment formula for calculations on any clutter class to which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. 7. For each clutter class under Formulas assigned to clutter classes, select a formula from the list. For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (ITU 529-3)" on page 163. 8. Click OK.

5.1.5.3

Creating or Modifying Environment Formulas (ITU 529-3)

Several environment formulas are available with the ITU 529-3 propagation model to model different environments. You can modify existing environment formulas used by the ITU 529-3 propagation model or create new environmental formulas. To create or modify an environment formula: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click ITU529. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Click the Formulas button. The Formulas dialogue appears. You can do the following: Add: To create a new formula, click the Add button and modify the parameters of the formula. Delete: To delete a formula, select the formula and click the Delete button. Modify: To modify an existing formula, select the formula and modify the parameters.

7. Click OK to save your changes and close the Formulas dialogue. 8. Click OK.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

163

Atoll User Manual

5.1.6

The ITU 370-7 Propagation Model

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

3. Right-click ITU370. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. 6. Under Calculate exceeded signal during, select one of the following: 50% of the time 10% of the time 1% of the time

7. Click OK. Note: When using the ITU 370-7 model, do not define the cell edge coverage probability in the coverage prediction properties with a value other than 50%, or cell edge coverage probability will be considered twice.

5.1.7

The Erceg-Greenstein Propagation Model

The Erceg-Greenstein (SUI) propagation model is suited for predictions in the 1900 and 6000 MHz range over distances between 100 m and 8 km. The Erceg-Greenstein (SUI) propagation model is suited for WiMAX (IEEE 802.16d and 802.16e). The Erceg-Greenstein (SUI) propagation model is well adapted for suburban environment. You can define several corrective formulas and associate a formula with each clutter class to adapt the model to a wide range of environments. You can also define a default formula to be used when no land use data is available. You can also set a default formula which is used when no clutter data is available. In this section, the following are explained: "Defining General Settings (Erceg-Greenstein (SUI))" on page 164 "Selecting an Environment Formula (Erceg-Greenstein (SUI))" on page 165 "Creating or Modifying Environment Formulas (Erceg-Greenstein (SUI))" on page 165.

5.1.7.1

Defining General Settings (Erceg-Greenstein (SUI))

To set general parameters on the Erceg-Greenstein (SUI) propagation model: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Erceg-Greenstein (SUI). The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Click the Parameters tab. You can modify the following settings: Add diffraction loss: The Erceg-Greenstein (SUI) propagation model can take into account losses due to diffraction, using a 1-knife-edge Deygout method, and using the ground altitude given in the DTM. For detailed information on the Deygout method, see the Technical Reference Guide. The calculations take the curvature of the earth into account. Select "1 - Yes" if you want the propagation model to add losses due to diffraction. Limitation to free space loss: When using the Erceg-Greenstein (SUI) propagation model, it is possible to calculate a theoretical path loss that ends up being lower than the free space loss. In Atoll, you can define the Erceg-Greenstein (SUI) propagation model to never calculate a path loss that is lower than the calculated free space loss per pixel. Select "1 - Yes" if you want the propagation model to limit the path loss calculated per pixel to the calculated free space loss.

7. Click OK.

164

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

5.1.7.2

Selecting an Environment Formula (Erceg-Greenstein (SUI))

The Erceg-Greenstein (SUI) propagation model can use an environment formula appropriate to each clutter class when calculating. You can assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. To select environment formulas: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Erceg-Greenstein (SUI). The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Under Formulas assigned to clutter classes, select a Default formula. Atoll uses the default environment formula for calculations on any clutter class to which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. 7. For each clutter class under Formulas assigned to clutter classes, select a formula from the list. For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (ErcegGreenstein (SUI))" on page 165. 8. Click OK.

5.1.7.3

Creating or Modifying Environment Formulas (Erceg-Greenstein (SUI))

Several environment formulas are available with the Erceg-Greenstein (SUI) propagation model to model different environments. You can modify existing environment formulas used by the Erceg-Greenstein (SUI) propagation model or create new environmental formulas. To create or modify an environment formula: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Erceg-Greenstein (SUI). The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Click the Formulas button. The Formulas dialogue appears. You can do the following: Add: To create a new formula, click the Add button and modify the parameters of the formula. Delete: To delete a formula, select the formula and click the Delete button. Modify: To modify an existing formula, select the formula and modify the parameters.

7. Click OK to save your changes and close the Formulas dialogue. 8. Click OK.

5.1.8

The ITU 526-5 Propagation Model

The ITU 526-5 model is suitable for predictions in the 30 to 10,000 MHz band with fixed receivers. According to the ITU 526-5 recommendations: If there are no obstacles, propagation takes place in free space If there is an obstacle, attenuation due to diffraction will be taken into account. The model uses the terrain profile and a diffraction mechanism (3-knife-edge Deygout method), optionally with correction, to calculate path loss.

To set the parameters on the ITU 526-5 propagation model: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click ITU526. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. 6. If desired, select the Apply to empirical correction check box and enter a formula that will be used as a correction with the Deygout method. Otherwise, the Deygout method will be used without correction. 7. Click OK.

5.1.9

The WLL Propagation Model

The WLL propagation model is designed for radio local loop applications in the 30-10,000 MHz band. The model is derived from the ITU 526-5 model.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

165

Atoll User Manual Along the Tx-Rx profile, both ground altitude and clutter height are considered to calculate diffraction losses. Atoll takes clutter height information in clutter heights file if available in the ATL document. Otherwise, it considers average clutter height specified for each clutter class in the clutter classes file description. If the ATL document does not contain any clutter height file and no average height per clutter class is specified, Atoll will consider ground altitude only. To set the parameters on the WLL propagation model: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click WLL. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. You can set the following parameters: Free space loss: You can modify the parameters of the formula used to calculate path loss in free space. Line of sight only: If the Line of sight only option is selected, Atoll checks for each pixel if the receiver is in the transmitter line of sight. The receiver is considered to be in the transmitter line of sight if 100% of the Fresnel half-ellipsoid is clear, in other words, if no obstacle is on the transmitter-receiver profile. If the receiver is not in the transmitter line of sight, no results at all will be displayed. If the Line of sight only option is not selected, Atoll calculates the path loss for each pixel, using the formula defined in the dialogue. Important: 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.

6. Click OK.

5.1.10

The Longley-Rice Propagation Model

Longley-Rice is a theoretical model suited for predictions in the 40-MHz band in flat areas. The Longley-Rice propagation model uses the terrain profile to calculate propagation. However, the parameters of the Longley-Rice propagation model can be set using distance and an additional loss value. To set the parameters on the Longley-Rice propagation model: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click Longley-Rice. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. 6. Under Add to propagation loss, enter the formula that will be used to calculate additional losses (in flat terrain, a value of "0" means a signal decreasing in a linear fashion as a function of distance). "dkm" in the formula is the distance in kilometres from the transmitter. 7. Click OK.

5.1.11

The ITU 1546 Propagation Model

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

166

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll the type of path over which the signal level is to be predicted (land in urban or suburban zones, land other zones, or sea).

To set the propagation model parameters: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click ITU1546. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. 6. Under Calculate Signal Level Exceeded During, select one of the following: 50% of the time 10% of the time 1% of the time

7. Under Type of Path, select one of the following: Land (Urban or Suburban Zones) Land (Other Zones) Sea

8. Select Use clutter altitude if you want to take the height of the clutter into account in diffraction. The height of the clutter will be taken from the Clutter Height folder, if clutter heights are available. Otherwise the average height of each clutter class will be used when evaluating diffraction. If this box is unselected, the diffraction is evaluated using only the DTM. 9. Click OK. For more information, see the Technical Reference Guide and the ITU-R P.1546 recommendation.

5.1.12

The Sakagami Extended Propagation Model

The Sakagami extended propagation model is based on a simplified version of the extended Sakagami-Kuboi propagation model. The Sakagami extended propagation model is valid for frequencies above 3 GHz. Therefore, it is only available in WiMAX 802.16d and WiMAX 802.16e documents by default. The Sakagami-Kuboi propagation model requires detailed information about the environment, such as the widths of the streets where the receiver is located, the angles formed by the street axes and the directions of the incident waves, the heights of the buildings close to the receiver, etc. The Sakagami-Kuboi propagation model is valid for frequencies below 2.2 GHz. Studies have shown that the Sakagami-Kuboi propagation model can be extended to frequencies higher than 3 GHz, which also allows the input required by the model to be simplified. The same studies show that the path loss predicted by the extended model is almost independent of the input parameters such as street widths and angles. The path loss calculation formula of the Sakagami extended propagation model is similar to the formula of the Standard Propagation Model. In Atoll, this model is in fact a copy of the Standard Propagation Model with the following values assigned to the K coefficients:

K Coefficient K1 K2 K3 K4 K5 K6 K7

Value Assigned
65.4 (calculated for 3.5 GHz) 40 -30 0 0 0 -5

For more information on working with the Standard Propagation Model, see "The Standard Propagation Model" on page 154.

5.1.13

Managing Propagation Models

The propagation models available for the current Atoll document can be found in the Propagation Models folder on the Modules tab of the Explorer window. You can manage the propagation models with the commands available on the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

167

Atoll User Manual To manage the propagation models of the current Atoll document: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to expand the Propagation Models folder.

3. Right-click the propagation model you want to manage. The context menu appears. 4. Select one of the following commands from the context menu: Properties: The Properties dialogue appears. You can view the general information about the propagation model on the General tab: Name: The name of the propagation model, as displayed in the Propagation Models folder Signature: The signature is assigned to the propagation model by Atoll. Each time you modify the parameters of the selected propagation model, Atoll changes the signature. The signature of the propagation model used to calculate a set of path loss matrices is stored with the matrices. This enables Atoll to verify the validity of the path loss matrices. When path loss matrices are not embedded in the Atoll document but are stored externally, the signature is found in the MODEL_SIG field of the Pathloss.dbf file. The name of the propagation model used is found in the MODEL_NAME field of the Pathloss.dbf file. Description: You can enter a description or comments in this field.

Duplicate: The selected propagation model is duplicated. It appears in the Propagation Models folder with the same name, preceded by "Copy of." Copy: The selected propagation model is copied. You can paste it, with its current settings into a new Atoll document by opening the document, clicking the Modules tab of the Explorer window and pressing CTRL+V. Note: 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.

Delete: The selected propagation model is deleted. Rename: You can enter a new name for the selected propagation model.

5.2

Defining Calculation Parameters

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

By using a calculation radius, Atoll limits the scope of calculations to a defined area. Atoll enables you to calculate two path loss matrices: a main and an extended one. By using two sets of calculation parameters, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter with one propagation model, while reducing calculation time and storage size by using an extended matrix with a lower resolution and another propagation model. Atoll will calculate the extended matrix only if you define all three parameters: propagation model, calculation radius, and resolution. If you do not define a calculation radius for the main propagation model and if you do not assign an extended propagation model, Atoll uses the prediction minimum threshold to define the calculation radius for each transmitter. However, this can lead to lengthy calculation times. Note: When creating coverage predictions, you can define a coverage resolution that is different from the resolution defined for the path loss matrices.

In this section, the following are explained: "Defining Calculation Parameters for One Transmitter" on page 168 "Defining the Same Calculation Parameters for a Group of Transmitters" on page 169 "Defining the Same Calculation Parameters for All Transmitters" on page 169 "Defining a Default Propagation Model" on page 170 "Defining a Default Resolution" on page 170.

5.2.1

Defining Calculation Parameters for One Transmitter

In Atoll, you can define calculation parameters, in other words, the propagation model, resolution, and calculation radius, for each transmitter.

168

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll To define main and extended calculation parameters for one transmitter: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign main and extended calculation parameters. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

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

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

5.2.2

Defining the Same Calculation Parameters for a Group of Transmitters

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

4. Click the Expand button (

) to expand the Transmitters folder.

5. Right-click the group of transmitters for which you want to define main and extended calculation parameters. The context menu appears. 6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected group. For each transmitter, you can set the calculation parameters in the following columns: Main Propagation Model Main Calculation Radius Main Resolution Extended Propagation Model Extended Calculation Radius Extended Resolution

7. To enter the same values in one column for all transmitters in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

5.2.3

Defining the Same Calculation Parameters for All Transmitters

In Atoll, you can choose one set of calculation parameters and assign them to all transmitters.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

169

Atoll User Manual To define the same calculation parameters for all transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

6. If desired, under Extended Matrix: Select a Propagation Model Enter a Radius and Resolution.

7. Click OK. The selected calculation parameters will be used for all transmitters. Note: Setting a different main or extended matrix on an individual transmitter as explained in "Defining Calculation Parameters for One Transmitter" on page 168 will override this entry.

5.2.4

Defining a Default Propagation Model

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

5.2.5

Defining a Default Resolution

When the resolution of the path loss matrix is not defined in the transmitter properties, Atoll uses the default resolution set for the Atoll document. Additionally, this resolution is used as the default coverage resolution when you create a new coverage prediction. To define the default resolution of the Atoll document: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Predictions tab. 5. Enter a Default Resolution.

Tip:

By setting an option in the atoll.ini file, you can set Atoll to use the currently defined default resolution if you clear the value entered in the Resolution text box when you create a coverage prediction. That way, if you have many coverage predictions, you can change their resolution by changing the default resolution and recalculating the coverage predictions. Atoll will then calculate them using the updated resolution. For information on changing entries in the atoll.ini file, see the Administrator Manual.

6. Click OK.

5.3

Managing Path Loss Matrices

In this section, the following are explained: "Calculating Path Loss Matrices" on page 171 "Stopping Path Loss Matrix Calculation" on page 171 "Setting the Storage Location of Path Loss Matrices" on page 171 "Using Centralised Path Loss Matrices" on page 172

170

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll "Checking the Validity of Path Loss Matrices" on page 172 "Tuning Path Loss Matrices Using Measurement Data" on page 173 "Exporting Path Loss Matrices" on page 179.

5.3.1

Calculating Path Loss Matrices

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

5.3.2

Stopping Path Loss Matrix Calculation

Depending on the size of the path loss matrices, it can take a long time and a lot of computer resources to calculate them. If necessary, you can stop calculation at any point. To stop calculations: Click the Stop Calculations button ( ) in the toolbar. Atoll immediately stops all ongoing calculations. The results of calculations that have already been completed, however, will be saved.

5.3.3

Setting the Storage Location of Path Loss Matrices

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

To set the storage location of the path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss matrices: Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are loading path loss matrices from a shared location, where you store your changes to shared path loss matrices. Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

171

Atoll User Manual

Caution:

When you save the path loss files externally, the external files are updated as soon as calculations are performed and not only when you save the Atoll document. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it, if you have updated the path loss matrices.

5. Click OK.

5.3.4

Using Centralised Path Loss Matrices

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

To use pre-calculated path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for the shared path loss matrices: Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the common path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see The Administrator Manual. Caution: The shared path loss matrices must be unlocked in order for users to be able to work with them. The administrator can check whether shared path loss matrices are unlocked or not in the Propagation tab of the Transmitters folders Properties dialogue.

5. Click OK.

5.3.5

Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices when calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid before calculating a coverage prediction. To check whether the path loss matrices are valid: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 5. Select one of the following display options: Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.

The Available Results table lists the following information for each displayed path loss matrix: Transmitter: The name of the transmitter. Locked: If the Locked check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a boolean field indicating whether or not the path loss matrix is valid. Reason for Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed. Tuned: If the Tuned check box has been selected, the initial path loss matrix obtained by the propagation model has been tuned by the use of real measurement points. See "Tuning Path Loss Matrices Using Measurement Data" on page 173 for more information.

172

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll 6. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 5.89) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.

Figure 5.89: Path loss matrix statistics

5.3.6

Tuning Path Loss Matrices Using Measurement Data

In Atoll, the path loss matrices are calculated using the propagation model and parameters defined as explained in "Defining Calculation Parameters" on page 168. However, the results calculated by a propagation model can vary from actual measurements. Atoll allows you to use available drive test data paths and CW measurements to increase the accuracy of calculated path loss matrices. Atoll uses the selected measurement data to tune a user-defined elliptical area around each measurement point. The main axis of the ellipse is oriented in the direction of the transmitter or repeater. Atoll smoothes the differences between tuned path loss matrix points and uncorrected path loss matrix points using an average error calculated between each measured value and the corresponding value in the path loss matrices. Important: When you use measurement data to tune path loss matrices, the results are stored locally. If you are using shared path loss matrices, these results will be automatically deleted when you make a calculation if the FullResyncPrivShared option is set in the atoll.ini file. If you are using shared path loss matrices, you should disable this option before tuning path loss matrices using measurement data. For more information, see the Administrator Manual. When using measurement data to tune path loss matrices, you need to have valid path loss matrices (for more information on path loss matrix validity, see "Managing Path Loss Matrices" on page 170): 1. Define the elliptical area around the measurement point as explained in "Defining the Area to be Tuned" on page 173. 2. Select the measurement data to be used to tune the path loss matrices: CW Measurements: You select the CW measurements from the CW Measurements folder as explained in "Tuning Path Loss Matrices Using CW Measurements" on page 175. 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 176. 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 177. By activating or deactivating the tuning paths, you can select the tuning path to be applied to the existing path loss matrices. Therefore, even if the path loss is recalculated, the path loss is automatically retuned using the active tuning paths.

5.3.6.1

Defining the Area to be Tuned

Atoll tunes the path loss matrices over an elliptical area around each measurement point. The main axis of the ellipse is oriented in the direction of the transmitter. To define the elliptical area around each measurement point: 1. Click the Data tab in the Explorer window. 2. Right-click the measurement type that you will use to tune the path loss matrices: CW Measurements: If you are going to use CW measurements to tune the path loss matrices, right-click the CW Measurements folder. The context menu appears. Drive Test Data: If you are going to use drive test data to tune the path loss matrices, right-click the Drive Test Data folder. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

173

Atoll User Manual 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Path Loss Tuning Parameters tab (see Figure 5.90).

Figure 5.90: Defining the ellipse for tuning path loss matrices 5. Under Path Loss Tuning Ellipse, set the following parameters: Radius of the Axis Parallel to the Profile: Enter the radius of the ellipse axis oriented in the same direction as the transmitter (or repeater). Radius of the Axis Perpendicular to the Profile: Enter the radius of the ellipse axis perpendicular to the transmitter (or repeater).

6. Click OK.

5.3.6.2

Defining Maximum Corrections and Thresholds on Path Loss Tuning

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

3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Path Loss Tuning Parameters tab (see Figure 5.90). 5. Under Tuning Range, set the following parameters: 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.

6. Click OK.

174

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

5.3.6.3

Tuning Path Loss Matrices Using CW Measurements

Atoll allows you to use available CW measurements to increase the accuracy of calculated path loss matrices. To use CW measurements to tune path loss matrices: 1. Click the Data tab in the Explorer window. 2. Select how you want to tune the path loss matrices: To tune the path loss matrix for a single transmitter: a. Click the Expand button ( ) to expand the CW Measurement folder.

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

Figure 5.91: Selecting all CW measurement paths c. Under Measurement Paths, select All. d. Click OK. Atoll begins optimising the path loss matrices for all transmitters on which CW measurements are available. The progress is displayed in the Event Viewer window. To tune the path loss matrices for selected transmitters using selected CW measurement paths: a. Right-click the CW Measurement folder. The context menu appears. b. Select Tune Path Loss Matrices from the context menu. The Measurement Path Selection dialogue appears (see Figure 5.91). c. Under Measurement Paths, select the option beside the list of CW measurements. d. Select the check box corresponding to each transmitter for which you want to tune the path loss matrices. For some transmitters, more than one CW measurement may exist. In this case, selecting the check box for the transmitter will select all the CW measurements. If you do not want to use all CW measurements, click the Expand button ( ) to expand the transmitter list and then select the single CW measurements you want to use. e. Click OK. Atoll begins optimising the path loss matrices for all transmitters on which CW measurements are available. The progress is displayed in the Event Viewer window. Note: In the case of repeaters, Atoll also tunes the path loss matrix of both the donor transmitter and the repeater. The contribution of the repeater and donor to the measured value is calculated based on the ratio of calculated values between the repeater signal and the donor signal. Each evaluated contribution is then used as input to tune the path loss matrix of each element. For more information, please refer to the Technical Reference Guide.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

175

Atoll User Manual

5.3.6.4

Tuning Path Loss Matrices Using Drive Test Data

Atoll allows you to use available drive test data paths to increase the accuracy of calculated path loss matrices. To use drive test data to tune path loss matrices: 1. Click the Data tab in the Explorer window. 2. Select how you want to tune the path loss matrices: To tune the path loss matrix using a single drive test data path: a. Click the Expand button ( ) to expand the Drive Test Data folder.

b. Right-click the drive test data path you want to use to tune the path loss matrices. The context menu appears. c. Select Tune Path Loss Matrices from the context menu. The Path Loss Tuning dialogue appears (see Figure 5.92).

Figure 5.92: Path Loss Tuning dialogue d. Click the For the following transmitters list. The list opens. e. Select the check box for each transmitter whose path loss matrix you want to tune. f. Click the Select the measured signal levels list. The list opens.

g. For each transmitter selected fromthe For the following transmitters list, select the check box for each measured signal strength that will be used to tune the path loss matrices. h. Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement was made. The progress is displayed in the Event Viewer window. To tune the path loss matrices using all drive test data paths: a. Right-click the Drive Test Data folder. The context menu appears. b. Select Tune Path Loss Matrices from the context menu. The Measurement Path Selection dialogue appears (see Figure 5.93).

Figure 5.93: Selecting all CW measurement paths c. Under Measurement Paths, select All. d. Click the For the following transmitters list. The list opens. e. Select the check box for each transmitter whose path loss matrix you want to tune.

176

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll f. Click the Select the measured signal levels list. The list opens.

g. For each transmitter selected fromthe For the following transmitters list, select the check box for each measured signal strength that will be used to tune the path loss matrices. h. Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement was made. The progress is displayed in the Event Viewer window. To tune the path loss matrices for selected transmitters using selected drive test data paths: a. Right-click the Drive Test Data folder. The context menu appears. b. Select Tune Path Loss Matrices from the context menu. The Measurement Path Selection dialogue appears (see Figure 5.93). c. Under Measurement Paths, select the option beside the list of drive test data paths. d. Select the check box corresponding to the drive test data you want to use to tune the path loss matrices. e. Click the For the following transmitters list. The list opens. f. Select the check box for each transmitter whose path loss matrix you want to tune.

g. Click the Select the measured signal levels list. The list opens. h. For each transmitter selected fromthe For the following transmitters list, select the check box for each measured signal strength that will be used to tune the path loss matrices. i. Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement was made. The progress is displayed in the Event Viewer window. Note: In the case of repeaters, Atoll also tunes the path loss matrix of both the donor transmitter and the repeater. The contribution of the repeater and donor to the measured value is calculated based on the ratio of calculated values between the repeater signal and the donor signal. Each evaluated contribution is then used as input to tune the path loss matrix of each element. For more information, please refer to the Technical Reference Guide.

5.3.6.5

Managing the Path Loss Tuning Points

After tuning the path loss matrices is complete, Atoll creates a tuning measurement file for each transmitter and stores it in a folder with the extension ".tuning". The .pts tuning file contains a header and a list of points defining the measurement data path excluding the antenna losses. A tuning file can contain several measurement paths, so that several calibrations can be applied successively on a path loss matrix and stored in a single tuning file. All the tuning files are stored as a catalogue in the current project. Each single tuning path can be activated or deactivated in order to be automatically applied to path loss matrices, even after recalculation. Tuning files are stored in the same way as path loss matrices, as explained in "Setting the Storage Location of Path Loss Matrices" on page 171. They can be saved on a network and shared between users. To manage the catalogue of the tuning path loss data: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 5. Select one of the following display options: Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.

The Available Results table lists the following information for each displayed path loss matrix: Transmitter: The name of the transmitter or repeater. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a boolean field indicating whether or not the path loss matrix is valid. Reason for Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed. Tuned: If the check box is selected, the initial path loss matrix obtained by the propagation model has been tuned by the use of real measurement data.

6. Select the tuning path loss matrices you want to manage using the available catalogue by holding CTRL and click the corresponding line in the Available Results table and then right-clicking. The context menu appears. 7. Select Path Loss Tuning Points from the context menu. The Path Loss Tuning Points dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

177

Atoll User Manual

Figure 5.94: Path Loss Tuning Catalogue 8. Select one of the following display options: All: All the tuning paths are displayed. Active Only: Only the active tuning paths are displayed.

The Available Results table lists the following information for each displayed tuning path, assuming each transmitter (or repeater) can have several ones coming from either the same or different measurement paths: Transmitter: The name of the transmitter or repeater. File: The location of the tuning file. Name: The name of the tuning entry. Each entry is automatically named by Atoll based on the source of the tuning data. You can edit the name by right-clicking the line and selecting Properties from the context menu. Active: You can set each tuning path as active by selecting the check box. Only active entries are used to tune the path loss matrices. When several entries are active and therefore applied to the same transmitter (or repeater), the applicable tunings on the path loss matrix are realised in turn from the top to the bottom of the catalogue. No. points: Displays the number of measurement points on the tuning path. X Radius (m): Displays the radius of the ellipse axis oriented in the same direction as the transmitter (or repeater) during the tuning session. Y Radius (m): Displays the radius of the ellipse axis perpendicular to the transmitter (or repeater) during the tuning session. Gain (dB): Displays the gain of the measurement receiver. Max. total correction (dB): Displays the user-defined maximum admissible total correction. Max. local correction (dB): Displays the user-defined maximum admissible local correction. Min. Threshold (dBm): Displays the user-defined level under which measurement values are not taken into account for path loss tuning Total correction (dB): Displays the mean error between each measured value and its corresponding pixel in the path loss matrix. This is the correction which is applied globally to all the matrices during the first step of path loss tuning (For more information, please refer to the Technical Reference Guide). Valid: This is a boolean field indicating whether or not the measurement path data (excluding the antenna information) are valid. Reason for Invalidity: If the measurement path data is indicated as being invalid, the reason is given here. Comments: Additional comments referring to the measurement entry are given in this field. You can edit the comment by right-clicking the line and selecting Properties from the context menu. Note: When path loss tuning entries are changed (e.g., activated or deleted) Atoll suggests deleting the corresponding path loss matrices.

You can import tuning files to replace an existing tuning or to benefit from a path loss tuning done by another user. The PTS files are imported using a DBF file containing all the information relative to matrices and their tuning. To import a path loss tuning catalogue: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 5. Select the tuning path loss matrices for which you want to import tuning files by holding CTRL and click the corresponding line in the Available Results table and then right-clicking. The context menu appears. 6. Select Import Path Loss Tuning Catalogue from the context menu. The Open dialogue appears. 7. Select the DBF path loss tuning catalogue file you want to import. 8. Click Open. The existing PTS files are replaced by the ones referenced in the catalogue file. Any additional files in the DBF catalogue file are added. You can work with the imported PTS files with the same options as files from a tuning carried out in the current project.

178

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

5.3.7

Exporting Path Loss Matrices

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

Figure 5.95: Exporting path loss matrices 8. Click OK to export the path loss matrices.

5.4

Predictions Available in Atoll

There are two types of predictions available in Atoll: Point predictions using the Point Analysis tool: It allows you to predict, at any point on the map, the profile between a reference transmitter and a receiver, the value of the signal levels of the surrounding transmitters, 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 studies such as interference studies for GSM/GPRS/ EDGE projects or handover, service availability, etc. for UMTS, CDMA2000 and TD-SCDMA projects. Many customisation features on coverage studies are available in order to make their analysis easier.

In this section, the following are explained: "Making Point Predictions" on page 179 "Making Coverage Predictions" on page 182.

5.4.1

Making Point Predictions

In this section, the following are explained: "Starting a Point Analysis" on page 180 "The Tabs of the Point Analysis Tool Window" on page 180 "Moving the Receiver on the Map" on page 181 "Taking Indoor Losses into Account" on page 181 "Taking Shadowing into Account in Point Analyses" on page 181.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

179

Atoll User Manual

5.4.1.1

Starting a Point Analysis

When you start a point analysis, Atoll automatically opens the Point Analysis Tool window. To make a point analysis: 1. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

If a transmitter was already selected on the map, a line appears connecting the selected transmitter and the receiver. Note: You can open the Point Analysis Tool window without starting a point analysis by selecting View > Point Analysis Tool.

2. Select the tab of the Point Analysis Tool window corresponding to the type of point prediction you want to make. For information on the tabs available in the Point Analysis Tool window, see "The Tabs of the Point Analysis Tool Window" on page 180.

5.4.1.2

The Tabs of the Point Analysis Tool Window

The Point Analysis Tool window has several tabs, enabling you to make several different point predictions. The tabs available depend on the radio technology of the current document: The Profile tab: The Profile tab is available in the Point Analysis Tool window for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA, WiMAX, and LTE projects. The Profile tab of the Point Analysis Tool window displays the profile between a reference transmitter and the receiver. As well, Atoll displays the strength of the received signal from the selected transmitter. This is calculated in real time. The Reception tab: The Reception tab is available in the Point Analysis Tool window for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA, WiMAX, and LTE projects. The Reception tab of the Point Analysis Tool window displays the predicted signal level from different transmitters in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. The calculations are based on the path loss matrices. Each bar is displayed in the colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they represent. The best server is indicated by a thick black line from the pointer to the server. The best server for 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 tooltip. The AS Analysis tab: The AS Analysis tab is available in the Point Analysis Tool window for CDMA and UMTS projects. The AS Analysis tab 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 Interference tab: The Interference tab is available in the Point Analysis Tool window for GSM/GPRS/EDGE projects, WiMAX, and LTE projects. The Interference tab displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar indicating the total interference experienced by the receiver, and bars representing the interference received from each interferer. In the map window, arrows from the receiver towards each transmitter are also displayed in the colour of the transmitters they represent. If you let the pointer rest, the interference level received from the corresponding transmitter at the receiver location will be displayed in the tooltip along with information on the channel being interfered and the type of interference, i.e., co- or adjacent channel. The PN Offset Interference tab: The PN Offset Interference tab is available in the Point Analysis Tool window for CDMA projects. The PN Offset Interference tab of the Point Analysis window gives you information on the reception for any point on the map where there is PN Offset interference. The SC Interference tab: The SC Interference tab is available in the Point Analysis Tool window for UMTS projects. The SC Interference tab of the Point Analysis window gives you information on reception for any point on the map where there is scrambling code interference.

180

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll The Results tab: The Results tab is available in the Point Analysis Tool window for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA, WIMAX, and LTE projects. The Results tab displays the current position and height of the receiver, the clutter class it is situated on. In addition, it also displays: in GSM/GPRS/EDGE projects, you can select to display the results from specific TRX types (or all), 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 signal level, the total level of interferences (I) over its subcells, the elementary level of interference of each interferer, and the resulting total C/I (or C/I+N). 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 WiMAX, LTE and TD-SCDMA projects, Atoll displays for each transmitter its signal level.

In the map window, arrows from the receiver towards each transmitter are also displayed in the colour of the transmitters they represent. The C/I levels at the receiver from transmitters are displayed as titles for the arrows. The best server is indicated by a thick black line from the pointer to the server. The best server for the pointer is the transmitter from which the pointer receives the highest signal level.If you let the pointer rest on an arrow, the interference level received from the corresponding transmitter at the receiver location will be displayed in the tooltip along with information on the channel being interfered and the type of interference, i.e., co- or adjacent channel.

5.4.1.3

Moving the Receiver on the Map

When you make a point analysis, the pointer ( tion of the receiver in several ways: ) represents the receiver in the map window. You can change the posiYou can move the receiver manually You can enter the coordinates of the new position You can place the receiver on a selected site.

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

To enter the coordinates of a position: 1. Right-click the receiver ( ) in the map window. The context menu appears.

2. Select Coordinates from the context menu. The Receiver Position dialogue appears. 3. Enter or paste the X and Y coordinates of the position and click OK. The receiver moves to the specified position. To place the receiver on a selected site: 1. Right-click the receiver ( ) in the map window. The context menu appears.

2. Select Target Site from the context menu. The Target Site dialogue appears. 3. Select the site on which you want to place the receiver from the Name list and click OK. The receiver moves to the specified position.

5.4.1.4

Taking Indoor Losses into Account

In Atoll you can calculate indoor predictions by taking indoor losses into consideration. You can define default indoor losses for all clutter classes, or you can define different indoor losses for each clutter class so that the characteristics of each clutter class are taken into consideration during calculations. To take indoor losses into account when making a point analysis: 1. Right-click the tab you are using in the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. 2. Select the Indoor Coverage check box to add indoor losses to the total path loss.

5.4.1.5

Taking Shadowing into Account in Point Analyses

Shadowing, or slow fading, is signal loss along a path caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be greater and in 50% of the measured cases, the result will be worse.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

181

Atoll User Manual Atoll uses a model standard deviation with the defined cell edge coverage probability to model the effect of shadowing and thereby provide predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. For example, a properly calibrated propagation model calculates a loss leading to a signal level of -70 dBm. You have set a cell edge coverage probability of 85%. If the calculated shadowing margin is 7 dB for a specific point, the target signal will be equal to or greater than -77 dBm 85% of the time. For information on setting the model standard deviation and the CI standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 121. You can take shadowing into account when you are making a point analysis. To take shadowing into account when making a point analysis: 1. Right-click the tab you are using in the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. 2. Select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Atoll calculates the shadowing using the standard deviation defined per clutter class. 3. From the Shadowing Margin list, you can select the standard deviation to see the value used by Atoll to calculate the shadowing. The standard deviation used by Atoll depends on the Point Analysis tab chosen. For GSM/GPRS/EDGE, WiMAX, and LTE projects: From Model: Atoll uses the model standard deviation to calculate the results for the Profile, and Reception tabs. CI: Atoll uses the CI standard deviation to calculate the results for the Interference tab (GSM/GPRS/EDGE, WiMAX, and LTE).

For UMTS, CDMA and TD-SCDMA projects: From Model: Atoll uses the model standard deviation to calculate the results for the Profile or Reception tabs. Atoll also uses the model standard deviation, along with the other defined standard deviations, to calculate the results for the AS Analysis tab (UMTS and CDMA only). Atoll also uses the model standard deviation, along with the EcI0 defined standard deviations, to calculate the results for the PN Offset Interference tab (CDMA) and SC Interference tab (UMTS) P-CCPCH Eb/Nt: Atoll uses the P-CCPCH EbNt standard deviation to calculate the results for the Profile or Reception tabs (TD-SCDMA only). EcI0: Atoll uses the EcI0 standard deviation, along with the model defined standard deviations, to calculate the results for the PN Offset Interference tab (CDMA) and SC Interference tab (UMTS). EbNt UL: Atoll uses the EbNt UL standard deviation, along with the other defined standard deviations, to calculate the results for the AS Analysis tab (UMTS and CDMA only). EbNt DL: Atoll uses the EbNt DL standard deviation, along with the other defined standard deviations, to calculate the results for the AS Analysis tab (UMTS and CDMA only). Note: The standard deviation chosen from the Shadowing Margin list is for information only; it is used only to display the value used by Atoll and does not change the standard deviation used to calculate the displayed results.

5.4.2

Making Coverage Predictions

A coverage prediction displays the results of defined coverage conditions. It is calculated using the path loss matrices and is based on coverage conditions and coverage resolutions. After calculation, Atoll displays the results as a graphical representation of the pixels for which the defined coverage conditions are satisfied. Atoll offers the following general coverage predictions, available for all technologies: Coverage by transmitter Coverage by signal level Coverage by overlapping zones.

Atoll also offers technology-specific coverage predictions, described in the technology-specific chapters, for example: Interference studies in GSM/GPRS/EDGE projects Coding scheme and throughput studies for GPRS/EDGE UMTS or CDMA2000 coverage predictions.

Atoll gives you a large flexibility over how the results of your coverage prediction are displayed. You can select which attributes should be displayed on the map and how they are displayed. As well, you can define information to be displayed in the legend, in the label, or in tooltips. Furthermore, Atoll also allows you to filter, sort, or group results before displaying them. Atoll offers several options and ways enabling you to create and work with coverage predictions. In this section, the following are explained: "Creating Coverage Predictions" on page 183 "Defining the Storage Location of Coverage Prediction Results" on page 184 "Calculating Coverage Predictions" on page 184 "Saving Defined Coverage Predictions" on page 186.

182

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

5.4.2.1

Creating Coverage Predictions

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

5.4.2.1.1

Creating a New Coverage Prediction

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

5. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

For more information on calculating coverage predictions, see "Calculating Coverage Predictions" on page 184.

5.4.2.1.2

Duplicating a Coverage Prediction

You can create a new coverage prediction by duplicating an existing coverage prediction. When you duplicate an existing coverage prediction, the coverage prediction you create will have the same coverage and display settings as the original one. Duplicating a coverage prediction is a way to quickly create a new coverage prediction with the same settings as an original one. The newly created coverage prediction is not automatically calculated. To duplicate an existing coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. A new coverage prediction appears in the Predictions folder with the same name as the original coverage prediction, preceded by "Copy of." The duplicated coverage prediction has the same coverage and display settings as the original one. For information on calculating coverage predictions, see "Calculating Coverage Predictions" on page 184.

5.4.2.1.3

Cloning a Coverage Prediction

You can create a new coverage prediction by cloning an existing coverage prediction. When you clone an existing coverage prediction, Atoll creates a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction. Cloning is useful if the existing coverage prediction has a display by discrete values (e.g., coverage by transmitter with a display by transmitter) and if you want a new coverage prediction with another display by discrete values (e.g., display by RNC or BSC). In this case, Atoll maps the results to the selected field and you do not need to recalculate the coverage prediction. On the other hand, cloning is not relevant if you change the display from a discrete field to value intervals, in which case, you must recalculate the study. To clone an existing coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction you want to clone. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

183

Atoll User Manual 4. Select Clone from the context menu. A new coverage prediction appears in the Predictions folder with the same name as the original coverage prediction, preceded by "Clone of." The cloned coverage prediction not only has the same coverage and display settings as the original one, but keeps the same results as well. 5. Right-click the cloned coverage prediction. The context menu appears. 6. Select Properties from the context menu. The Properties dialogue appears. 7. Select the Display tab. 8. On the Display tab, keep the Display Type "Discrete Values" selected. 9. Select another value from the Field list to change the value displayed. 10. Click OK to apply the new display parameter.

5.4.2.2

Defining the Storage Location of Coverage Prediction Results

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

To define the storage location of coverage prediction results: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction for which you want to define the storage location of the results. The context menu appears. 4. Select Properties from the context menu. The coverage predictions Properties dialogue appears. 5. On the General tab, click the button beside Folder ( ) and select the storage location of the results:

Saving in the Atoll document: To store the results in the document, select Embedded. Saving externally: To store the results externally, select the external storage location. Atoll creates a folder for the results in the same folder with the Atoll document and gives it the name of the document, with the extension "studies." Sharing the results of another coverage prediction: To display the results of a coverage prediction that was calculated in a different document, select Connect to Results to navigate to the XML file describing the coverage prediction results.

Externally stored coverage prediction results can be imported as customised studies. For more information on importing customised studies, see "Saving Defined Coverage Predictions" on page 186. For a detailed description of the XML file, see Studies.XML in the Administrator Manual.

5.4.2.3

Calculating Coverage Predictions

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

184

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll In this section, the following are explained: "Calculating Several Coverage Predictions" on page 185 "Calculating a Single Coverage Prediction" on page 185 "Forcing Calculations" on page 185 "Stopping Calculations" on page 185 "Locking Coverage Predictions" on page 185.

5.4.2.3.1

Calculating Several Coverage Predictions

When you have several defined coverage predictions, you can start calculation when you want and Atoll will calculate them one after the other. When you calculate coverage predictions, only unlocked coverage predictions are calculated. Unlocked coverage predictions are displayed in the Predictions folder with the unlocked icon ( age predictions, see "Locking Coverage Predictions" on page 185. To calculate created coverage predictions: Click the Calculate button ( ) in the toolbar. When you click the Calculate button, Atoll first calculates nonexistent and invalid path loss matrices and then, unlocked coverage predictions in the Predictions folder. The progress of the calculations is displayed in the Event Viewer window. After calculation, the results are displayed in the map window, if the coverage predictions visibility check box has been selected. ). For information on locking and unlocking cover-

5.4.2.3.2

Calculating a Single Coverage Prediction

To calculate a single coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction you want to calculate. The context menu appears. 4. Select Calculate from the context menu. Atoll first calculates non-existent and invalid path loss matrices and then, the coverage prediction even if this one has been previously locked. After calculation, the results are displayed in the map window, if the coverage predictions visibility check box has been selected.

5.4.2.3.3

Forcing Calculations
When you have several defined coverage predictions, you can start calculation when you want and Atoll will calculate them one after the other. Normally, Atoll only recalculates non-existent and invalid path loss matrices before calculating coverage predictions. If you want, you can make Atoll recalculate all path loss matrices, including valid ones. When you calculate coverage predictions, only unlocked coverage predictions are calculated. Unlocked coverage predictions are displayed in the Predictions folder with the unlocked icon ( age predictions, see "Locking Coverage Predictions" on page 185. ). For information on locking and unlocking cover-

To force Atoll to recalculate all path loss matrices before calculating coverage predictions: Click the Force Calculate button ( ) in the toolbar. When you click the Force Calculate button, Atoll first removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions. After calculation, the results are displayed in the map window, if the coverage predictions visibility check box has been selected.

5.4.2.3.4

Stopping Calculations
When Atoll has begun to calculate coverage predictions, you can stop the calculation at any given point. This can be useful if, for example, you want to change one of the coverage predictions or if you dont want to calculate the coverage predictions at that time. To stop calculations: Click the Stop Calculations button ( ) in the toolbar. Atoll immediately stops all ongoing calculations. The results of calculations that have already been completed, however, will be saved.

5.4.2.3.5

Locking Coverage Predictions

Coverage predictions are locked by default as soon as they have been calculated. Then, when you calculate new coverage predictions, only unlocked coverage predictions are calculated. Locking a coverage prediction retains the information as calculated under given conditions (e.g., before a new base station is created or before optimising the network). It also saves time by limiting unnecessary recalculation.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

185

Atoll User Manual

Note:

To prevent Atoll from automatically locking coverage predictions after calculating them, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.

To lock a coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction you want to lock. The context menu appears. Unlocked coverage predictions are displayed in the Predictions folder with the unlocked icon ( 4. Select Study Locked from the context menu. The icon changes to the locked icon ( ) and the Study Locked item in the context menu now appears checked. The coverage prediction is now locked and will not be calculated when the Calculate button in the toolbar is clicked. However, if you select Calculate from the coverage predictions context menu, Atoll will first unlock the coverage prediction and then calculate it. You can lock all unlocked coverage predictions using the Predictions folders context menu. ).

5.4.2.3.6

Unlocking Coverage Predictions

Coverage predictions are locked by default as soon as they have been calculated. You can unlock a single coverage prediction. To unlock a coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction you want to unlock. The context menu appears. Locked coverage predictions are displayed in the Predictions folder with the locked icon ( 4. Select Study Locked from the context menu. The icon changes to the unlocked icon ( ) and the Study Locked item in the context menu is no longer selected. ).

You can unlock all locked coverage predictions using the Predictions folders context menu.

5.4.2.4

Saving Defined Coverage Predictions

Once you have defined a coverage prediction, you can use it again in other Atoll documents, either by using the coverage prediction to create a customised study or by exporting its coverage and display parameters in a user configuration. In this section, the following are explained: "Saving a Coverage Prediction as a Customised Study" on page 186 "Exporting a Defined List of Predictions in a User Configuration File" on page 187.

5.4.2.4.1

Saving a Coverage Prediction as a Customised Study

Once you have defined a coverage prediction, you can use it as a customised study. This study will be available to you in the Study Types dialogue the next time you want to create a new coverage prediction. The initial parameters of the coverage prediction will be the same as the coverage prediction it is based on but, when you select it in the Study Types dialogue, Atoll allows you to modify them. To save a coverage prediction as a customised study: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction you want to save as a customised study. The context menu appears. 4. Select Save as Customised Study from the context menu. The Save As dialogue appears. In the Save As dialogue, Atoll proposes a name and location for the XML file that will contain the customised study. You can accept the default values or you can change the name and save the XML file in any folder you have write access to. 5. Click Save. Atoll saves the study in the selected XML file. The next time you create a new coverage prediction, the customised study will be available at the bottom of the list, under the full path and file name of the XML file (see Figure 5.96). If you have other XML template files, you can click the Customised Studies button and select it in the Open dialogue.

186

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 5: Managing Calculations in Atoll

Figure 5.96: Study Types dialogue Coverage predictions stored in the XML template files are also directly available in the Calculations menu of the context menus of the Transmitters folder, of a group of transmitters, and of a single transmitter. In a multi-user environment, the administrator can make customised studies available for all the users by saving the XML file in the Atoll installation directory. For more information, see the Administrator Manual.

5.4.2.4.2

Exporting a Defined List of Predictions in a User Configuration File

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

5.4.2.5

Calculating Indoor Coverage

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

5.4.2.6

Taking Shadowing into Account

Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be greater and in 50% of the measured cases, the result will be worse. Atoll uses a model standard deviation with the defined cell edge coverage probability to model the effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. For example, a properly calibrated propagation model calculates a loss leading to a signal level of -70 dBm. You have set a cell edge coverage probability of 85%. If the calculated shadowing margin is 7 dB for a specific point, the target signal will be equal to or greater than -77 dBm 85% of the time. For information on setting the model standard deviation and the CI standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 121. When creating the coverage prediction, select the Shadowing Taken into Account check box. Then, you can define the Cell Edge Coverage Probability.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

187

Atoll User Manual

188

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6
GSM/GPRS/EDGE Networks

RF Planning & Optimisation Software

Atoll

Atoll User Manual

190

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

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 191. Creating the network of base stations is explained in "Planning and Optimising GSM/GPRS/EDGE Base Stations" on page 192. 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 study base stations. In "Studying Network Capacity" on page 253, using traffic maps to study network capacity is explained. Creating traffic captures 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 "Verifying Network Capacity" on page 389. How to filter imported drive test data paths, and how to use the data in coverage predictions is also explained.

6.1

Designing a GSM/GPRS/EDGE Network

Figure 6.97 depicts the process of planning and creating a GSM/GPRS/EDGE network.
1 Open an Existing Project or Create a New One Network Configuration - Add Network Elements - Change Parameters Basic Predictions (Best Server, Signal Level) Neighbour Allocation 5a 5b Required number of TRXs 5 4

Traffic Maps

Dimensioning

User-defined values

5c

Automatic Frequency Allocation (AFP)

6a List of Frequencies 6

6b Manual Frequency Allocation

GSM/GPRS/EDGE Predictions 8

Prediction Study Reports

7a

Frequency Plan Analysis

Figure 6.97: Planning a GSM/GPRS/EDGE network - workflow The steps involved in planning a GSM/GPRS/EDGE network are described below. The numbers refer to Figure 6.97. 1. Open an existing radio-planning document or create a new one ( 1

).

You can open an existing Atoll document by selecting File > Open. Creating a new a new Atoll document is explained in Chapter 2: Starting an Atoll Project.
2

2. Configure the network by adding network elements and changing parameters ( You can add and modify the following elements of base stations: "Creating or Modifying a Site" on page 201 "Creating or Modifying a Transmitter" on page 201 "Applying a New Cell Type" on page 202.

).

You can also add base stations using a base station template (see "Placing a New Station Using a Station Template" on page 203). 3. Carry out basic coverage predictions ( 3

"Making a Point Analysis to Study the Profile" on page 215

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

191

Atoll User Manual "Studying Signal Level Coverage" on page 216 and "Signal Level Coverage Predictions" on page 225
4

4. Allocate neighbours, automatically or manually ( "Planning Neighbours" on page 241.

5

).

5. Estimate the required number of TRXs ( -

) in one of the following ways:

You can import or create traffic maps ( 5a ) and use them as a basis for dimensioning 5b ) (see "Studying Network Capacity" on page 253). You can define them manually either on the TRXs tab of each transmitters Properties dialogue or in the Subcells table (see "Modifying a Subcell" on page 202) (
5c

).
6

6. Once you have the required number of TRXs, manually or automatically create a frequency plan ( "Allocating Frequencies and BSICs Manually" on page 274 "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 270.
7

).

7. With the frequency plan, make GSM/GPRS/EDGE-specific coverage predictions ( "Analysing Network Quality" on page 317.
8

).

8. Analyse the frequency plan ( -

).

"Auditing a GSM/GPRS/EDGE Frequency Plan" on page 338 "Checking Consistency Between Transmitters and Subcells" on page 340 "Displaying the Frequency Allocation" on page 341.

6.2

Planning and Optimising GSM/GPRS/EDGE Base Stations

As described in Chapter 2: Starting an Atoll Project, you can start an Atoll document from a template, with no sites, or from a database with a set of sites. As you work on your Atoll document, you will still need to create sites and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such as the TMA, feeder cables, etc. In a GSM/GPRS/EDGE project, you must also add subcells to each transmitter. A subcell refers to the characteristics of a group of TRXs on a transmitter. Atoll lets you create one site or transmitter at a time, or create several at once by using 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, subcells, and TRXs. Atoll allows you to make a variety of coverage predictions, such as signal level or transmitter coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, or studied. 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 studies, such as interference studies, or circuit or packet-dedicated studies. In this section, the following are explained: "Creating a GSM/GPRS/EDGE Base Station" on page 192 "Creating a Group of Base Stations" on page 208 "Modifying Sites and Transmitters Directly on the Map" on page 209 "Display Tips for Base Stations" on page 209 "Creating a Repeater" on page 210 "Creating a Remote Antenna" on page 212 "Setting the Working Area of an Atoll Document" on page 214 "Studying a Single Base Station" on page 215 "Studying Base Stations" on page 218 "Planning Neighbours" on page 241.

6.2.1

Creating a GSM/GPRS/EDGE Base Station

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

192

Chapter 6: GSM/GPRS/EDGE Networks "Placing a New Station Using a Station Template" on page 203 "Managing Station Templates" on page 204 "Duplicating an Existing Base Station" on page 207.

6.2.1.1

Definition of a Base Station

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

6.2.1.1.1

Site Description
The parameters of a site can be found in the sites Properties dialogue. The Properties dialogue has one tab: The General tab (see Figure 6.98):

Figure 6.98: New Site dialogue Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you want to change the default name that Atoll gives to new sites, see the Administrator Manual. Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of the site here.

Tip:

While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.

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 wish. If an altitude is specified here, Atoll will use this value for calculations. Comments: You can enter comments in this field if you wish.

6.2.1.1.2

Transmitter Description
The parameters of a transmitter can be found in the transmitters Properties dialogue. When you create a transmitter, the Properties dialogue has four tabs: the General tab, the Transmitter tab, the TRXs tab, the AFP tab (see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 270), and the Configurations tab. Once you have created a transmitter, its Properties dialogue has four additional tabs: the Intra-Technology Neighbours tab (see "Allocating or Deleting Neighbours Using the Intra-Technology Neighbours Tab of the Transmitter Properties Dialogue" on page 248), the InterTechnology Neighbours tab), the Propagation tab (see Chapter 5: Managing Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 32). 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

193

Atoll User Manual For information on the site Properties dialogue, see "Site Description" on page 193. You can click the New button to create a new site on which the transmitter will be located. 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 dialogue, see "Setting HCS Layers" on page 400. 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 positions, and then enter the x-axis and y-axis coordinates, X and Y, respectively.

The Transmitter tab (see Figure 6.99):

Figure 6.99: Transmitter dialogue - Transmitter tab Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder of the Data tab. Note: 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 Extra-Network (Interferer Only). No coverage for an Interferer Only transmitter will be calculated for coverage predictions. This feature 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 423.

Transmission: Under Transmission, you can select to enter either Power and Total Losses or EIRP (Effective Isotropically Radiated Power). If you select EIRP, you can enter the value yourself, without defining power and losses for the transmitter. If you select Power and Total Losses, Atoll calculates losses and noise according to the characteristics of the equipment assigned to the transmitter. Equipment can be assigned using the Equipment Specifications dialogue which appears when you click the Equipment button. Atoll will calculate the EIRP with the following formula: EIRP = Power + Gain - Losses

194

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks On the Equipment Specifications dialogue (see Figure 6.100), the equipment you select and the gains and losses you define are used to initialise total transmitter DL losses. UL losses are not modelled in GSM/GPRS/ EDGE projects. 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 147. 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 147. BTS: You can select a base transceiver station (BTS) equipment from the BTS list. In GSM, only the downlink losses are modelled. You can click the Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defining BTS Equipment" on page 148. Feeder Length: You can enter the feeder length at transmission. Miscellaneous Losses: You can enter miscellaneous losses at transmission. Receiver Antenna Diversity Gain: This field is not used for GSM/GPRS/EDGE projects. Loss Related to Repeater Noise Rise: This field is not used for GSM/GPRS/EDGE projects.

Figure 6.100: The Equipment Specifications dialogue Note: You can modify the Total Losses at transmission if you wish. 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. 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. For information on working with data tables, see "Working with Data Tables" on page 53.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

195

Atoll User Manual The Configurations tab (see Figure 6.101):

Figure 6.101: Transmitter dialogue - Configurations tab 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 411. Note: 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.

In addition, EDGE Evolution can be modelled on the terminal side through: 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 C/I) graphs. The support of multi-carriers which can be set up on the terminal side.

For more information, see "Creating or Modifying a GSM/GPRS/EDGE Terminal" on page 419. 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 408.

6.2.1.1.3

Subcell Definition
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 404). 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 dialogue of the transmitter to which it is assigned. The TRXs tab has the following subcell-related options: Under Cell Type: 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 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

196

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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 415. 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. Note: Although coverage may be restricted within the set minimum range and maximum range, interference from the transmitter is not limited within these ranges.

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 273. 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 272. 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 synthesized 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 dual-band transmitters. For information on dual-band transmitters, see "Advanced Modelling of Multi-Band Transmitters" on page 415. 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. 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. DL Power Reduction: 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 of 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 415 and the Administrator Manual.

Note:

Note:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

197

Atoll User Manual 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 studies and in the AFP. 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. 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 414. Hopping Mode: The frequency hopping mode supported by the selected TRX type. The hopping mode can be either "Base Band Hopping mode (BBH)" or "Synthesized 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. 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 (Synthesized Frequency Hopping) or BBH (Base Band Hopping) and if the Allocation Strategy is Free. 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 (Synthesized 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 (Synthesized Frequency Hopping) or BBH (Base Band Hopping). Lock HSN: When the Lock HSN check box is selected, the subcells currently assigned HSN is kept when a new AFP session is started. Synchronisation: The value entered in the Synchronisation column is used during frequency hopping; frequency hopping is synthesized 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. 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 mulitplies the cost which has to be minimised by the AFP. % Max. Interference: 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: 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. Number of Antennas (Transmission Diversity): The number of antennas the subcell can use for transmission. In most cases, a transmitter will transmit with only one antenna, however, some transmitters are capable of transmission diversity. By transmitting on more than one antenna, the signal experiences a gain of 3 dB. An additional transmission diversity gain can be defined per clutter class in order to correctly model gain due to the environment. Lock the number of 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.

198

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Note:

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 404.

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 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. Total Circuit Demand (Erlangs): 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). Total Packet 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. 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 reinjected, 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.

Figure 6.102: Overflow between concentric cells

Figure 6.103: Overflow between HCS layers Important: The target rate of traffic overflow and the half-rate traffic ratio must be the same for BCCH and TCH subcells. 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. 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. 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. AFP Indicators: The information displayed comes from the results of an AFP model; it is displayed for informational purposes only and can not be edited.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

199

Atoll User Manual 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: 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. 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. 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 right-clicking the Transmitters folder in the Data tab of the Explorer window and then selecting Network Settings > 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 Data tab of the Explorer window and then selecting Network Settings > Subcells Table: Traffic data, (or AFP Indicators, from the context menu.

Note:

6.2.1.1.4

TRX Definition
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: 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.

The TRXs and their properties are found on TRXs tab of the Properties dialogue of the transmitter to which they are assigned. Note: 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 Data tab of the Explorer window and then selecting Network Settings > 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: 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 dialogue. 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.

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 "Synthesized 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 intrasite 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 the Lock Channels and MAIO check box is selected, the TRXs currently assigned channels and MAIO are kept when a new AFP session is started. TRX Configuration: The TRX Configuration selected defines the highest coding scheme index number possible in GPRS and in EDGE. For the TRX Configuration to be used fully, the terminal must be capable of using

200

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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. Inter-technology DL Noise Rise: 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 424.

6.2.1.2

Creating or Modifying a Base Station Element

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells and TRXs. This section describes how to create or modify the following elements of a base station: "Creating or Modifying a Site" on page 201 "Creating or Modifying a Transmitter" on page 201 "Applying a New Cell Type" on page 202 "Modifying a Subcell" on page 202 "Creating or Modifying a TRX" on page 203.

6.2.1.2.1

Creating or Modifying a Site

You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 193, through the sites Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create or modify a site: 1. If you are creating a new site: a. Click the Data tab in the Explorer window. b. Right-click the Sites folder. The context menu appears. c. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 6.98 on page 193). 2. If you are modifying the properties of an existing site: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Sites folder.

c. Right-click the site you want to modify. The context menu appears. d. Select Properties from the context menu. The sites Properties dialogue appears. 3. Modify the parameters described in "Site Description" on page 193. 4. Click OK.

Tip:

If you are creating several sites at the same time, or modifying several existing sites, you can do it quickly by editing or pasting the data directly in the Sites table. You can open the Sites table by right-clicking the Sites folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

6.2.1.2.2

Creating or Modifying a Transmitter

You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 193, through the transmitters Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create or modify a transmitter: 1. If you are creating a new transmitter: a. Click the Data tab in the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 6.99). 2. If you are modifying the properties of an existing transmitter: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Transmitters folder.

c. Right-click the transmitter you want to modify. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

201

Atoll User Manual d. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Modify the parameters described in "Transmitter Description" on page 193. 4. Click OK. If you are creating 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 202.

Tips: 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 right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. 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.

6.2.1.2.3

Applying a New Cell Type

In GSM/GPRS/EDGE, the subcells are defined by the cell type. By selecting a different cell type, you can change the existing subcells to the subcells defined by the new cell type. Atoll will then create the subcells that exist in the new cell type and remove the subcells that do not exist in the new cell type. If the same subcells exist in the new cell type, Atoll offers you the choice of keeping current parameters or resetting them to those found in the new cell type. To apply a new cell type: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to apply a new cell type. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. 5. Select the TRXs tab. 6. Under Cell Type, 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.

7. Modify the parameters described in "Subcell Definition" on page 196 of the cell type and its subcells. 8. Click OK.

Tip:

If you are applying a new cell type to 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 right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

6.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 Definition" on page 196, through the Properties dialogue of the transmitter where the subcell is located. To create or modify a subcell: 1. Click the Data tab of the Explorer window. 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 dialogue appears. 5. Select the TRXs tab. 6. Modify the parameters described in "Subcell Definition" on page 196. 7. Click OK.

Tip:

If you are creating several subcells at the same time, or modifying several existing subcells, you can do it more quickly by editing or pasting the data directly in the Subcells table. You can open the Subcells table by right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Subcells > Subcells Table: Standard Data from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

202

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.2.1.2.5

Creating or Modifying a TRX

When a GSM/GPRS/EDGE network is first created, TRXs are assigned as part of the dimensioning process. Once the network exists, you can add TRXs manually to either existing or new transmitters. You can also modify existing TRXs. You can access the properties of a TRX, described in "TRX Definition" on page 200, through the Properties dialogue of the transmitter the TRX is assigned to. To create or modify a TRX: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter on which you want to create a TRX or whose TRX you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. 5. Select the TRXs tab. 6. Under TRXs: If you are creating a new TRX, enter the parameters described in "TRX Definition" on page 200 in the row marked with the New Row icon ( ). If you are modifying an existing TRX, modify the parameters described in "TRX Definition" on page 200.

7. Click OK.

Tip:

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 on the Data tab of the Explorer window and selecting Subcells > TRXs Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

6.2.1.3

Placing a New Station Using a Station Template

In Atoll, a station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding subcells and TRXs. To place a new station using a station template: 1. In the Radio toolbar, select a template from the list.

2. Click the New Transmitter or Station button (

) in the Radio toolbar.

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.

Tips:

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 38. If you let the pointer rest over the station you have placed, Atoll displays its tip text with its exact coordinates, allowing you to verify that the location is correct.

You can also place a series of stations using a Atoll template. You do this by defining an area on the map where you want to place the stations. Atoll calculates the placement of each station according to the defined hexagonal subcell radius in

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

203

Atoll User Manual the station template. For information on defining the subcell radius, see "Creating or Modifying a Station Template" on page 204. To place a series of stations within a defined area: 1. In the Radio toolbar, select a template from the list. 2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of stations created from the same station template.

Note:

If the Hexagonal Design button is not available ( ), the hexagonal subcell radius for this template is not defined. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 204.

3. Draw a zone delimiting the area where you want to place the series of stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. Atoll fills the delimited zone with new stations and their hexagonal shapes. Station objects such as sites and transmitters are also created and placed into their respective folders. You can work with the sites and transmitters in these stations as you work with any station object, adding, for example, another antenna to a transmitter.

Placing a Station on an Existing Site

When you place a new station using a station template as explained in "Placing a New Station Using a Station Template" on page 203, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place a station on an existing site: 1. On the Data tab, clear the display check box beside the Hexagonal Design folder. 2. In the Radio toolbar, select a template from the list. 3. Click the New Station button ( ) in the Radio toolbar.

4. Move the pointer to the site on the map. When the frame appears around the site, indicating it is selected, click to place the station.

6.2.1.4

Managing Station Templates

Atoll comes with GSM/GPRS/EDGE station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio toolbar (see Figure 6.104).

Figure 6.104: The Radio toolbar In this section, the following are explained: "Creating or Modifying a Station Template" on page 204 "Copying Data from One Station Template to Another" on page 206 "Modifying a Field in a Station Template" on page 207 "Deleting a Station Template" on page 207.

6.2.1.4.1

Creating or Modifying a Station Template

When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. As well, you can modify the properties of any station template. To create or modify a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. You can now create a new station template or modify an existing one: To create a new station template: Under Station Templates, select the station template that most closely resembles the station template you want to create and click Add. The Properties dialogue appears.

204

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To modify an existing station template: Under Station Templates, select the station template whose properties you want to modify and click Properties. The Properties dialogue appears.

4. Click the General tab of the Properties dialogue. In this tab (see Figure 6.105), you can modify the following: 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, the HCS Layer, the Cell Type, the Max. TRXs/ Sector, the Min. Range, the Max. Range, and the BSIC Domain.

Figure 6.105: Station Template Properties dialogue General tab Under Main Antenna, you can modify the following: the antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Height of the antenna 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 Mechanical Downtilt, and the Additional Electrical Downtilt. Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

5. Click the Transmitter tab. In this tab (see Figure 6.106), you can modify the following: Under Transmission, you can select to enter either Power and Total Losses or EIRP (Effective Isotropically Radiated Power). If you select EIRP, you can enter the value yourself, without defining power and losses for the transmitter. If you select Power and Total Losses, Atoll calculates losses and noise according to the characteristics of the equipment assigned to the transmitter. Equipment can be assigned using the Equipment Specifications dialogue which appears when you click the Equipment button. Atoll will calculate the EIRP with the following formula: EIRP = Power + Gain - Losses For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 193.

Figure 6.106: Station Template Properties dialogue Transmitter tab If you want transmitters created with this station template to be active by default, select the Active check box.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

205

Atoll User Manual 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 Extra-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 423. 6. Click the Configurations tab. In this tab (see Figure 6.107), you select the configuration used for GSM and GPRS/ EDGE stations. Under GPRS/EDGE Properties, you must select the GPRS/EDGE Transmitter check box 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 411. Note: 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.

In addition, EDGE Evolution can be modelled on the terminal side through: 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 C/I) graphs. The support of multi-carriers which can be set up on the terminal side.

For more information, see "Creating or Modifying a GSM/GPRS/EDGE Terminal" on page 419. For all transmitters, you can select a codec configuration from the list. For information on creating a coding scheme configuration, see "Codec Configuration" on page 408.

Figure 6.107: Station Template Properties dialogue Configurations tab 7. Click the Neighbours tab. In this tab (see Figure 6.108), you can modify the Max Number of Intra-Technology Neighbours and the Max Number of Inter-Technology Neighbours. For information on defining neighbours, see "Planning Neighbours" on page 241.

Figure 6.108: Station Template Properties dialogue Neighbours tab 8. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Sites table, or if you have defined an additional field in the Station Template Properties dialogue. 9. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.

6.2.1.4.2

Copying Data from One Station Template to Another

You can copy properties from one template to another template by using the Station Templates table.

206

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To copy properties from one template to another template: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Station Templates from the context menu. The Station Templates table appears. 4. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy from and paste them into the row corresponding to the station template you want to modify.

6.2.1.4.3

Modifying a Field in a Station Template

To modify a field in a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Select the template in the Available Templates list. 4. Click the Fields button. 5. In the dialogue that appears, you have the following options: Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Types Data Table" on page 54) for it to appear as an option in the station template properties. To add a new field: i. Click the Add button. The Field Definition dialogue appears.

ii. Enter a Name for the new field. This is the name that will be used in database. iii. If desired, you can define a Group that this custom field will belong to. When you open an Atoll document from a database, you can then select a specific group of custom fields to be loaded from the database, instead of loading all custom fields. iv. In Legend, enter the name for the field that will appear in the Atoll document. v. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/ Time, and Currency. If you choose text, you can also set the field Size (in characters), and create a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER after each one. vi. Enter, if desired, a Default Value for the new field. vii. Click OK to close the Field Definition dialogue and save your changes. Delete: To delete a user-defined field: i. Select the user-defined field you want to delete.

ii. Click the Delete button. The user-defined field appears in strikethrough. It will be definitively deleted when you close the dialogue. Properties: To modify the properties of a user-defined field: i. Select the user-defined field you want to modify.

ii. Click the Properties button. The Field Definition dialogue appears. iii. Modify any of the properties as desired. iv. Click OK to close the Field Definition dialogue and save your changes. 6. Click OK.

6.2.1.4.4

Deleting a Station Template

To delete a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Under Station Templates, select the station template you want to delete and click Delete. The template is deleted. 4. Click OK.

6.2.1.5

Duplicating an Existing Base Station

You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same site, transmitter, subcell, TRX parameter values as 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

207

Atoll User Manual To duplicate an existing base station: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Sites folder.

3. Right-click the site you want to duplicate. The context menu appears. 4. From the context menu, select one of the following: Select Duplicate > 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. 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.

You can now place the new base station on the map using the mouse. 5. In the map window, move the pointer over the map to where you would like to place the new base station. The exact coordinates of the pointers current location are visible in the Status bar.

Figure 6.109: Placing a new station

Tips:

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 38. 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.

6. Click to place the duplicate base station. A new base station is placed on the map. The site, transmitters, subcells, and TRXs of the new base station have the same names as the site, transmitters, subcells, and TRXs of the original base station with each name marked as "Copy of." The site, transmitters, subcells, and TRXs of the duplicate base station have the same settings as those of the original base station. All the remote antennas and repeaters of any transmitter on the original site are also duplicated. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate base station. For more information on the site, transmitter, subcell, and TRX properties, see "Definition of a Base Station" on page 193.

6.2.2

Creating a Group of Base Stations

You can create base stations individually as explained in "Creating a GSM/GPRS/EDGE Base Station" on page 192, or you can create one or several base stations by using station templates as explained in "Placing a New Station Using a Station Template" on page 203. However, if you have a large data-planning project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations. Note: 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 96.

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 subcell data in the Subcells table, in that order. Important: The table you copy data from must have the same column layout as the table you are pasting data into.

208

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. 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" on page 61. For information on importing table data, see "Importing Tables from Text Files" on page 63. Note: You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio toolbar. For information, see "Placing a New Station Using a Station Template" on page 203.

6.2.3

Modifying Sites and Transmitters Directly on the Map

In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu on the Data tab of the Explorer window. However, in a complex radio-planning project, it can be difficult to find the data object in the Data tab, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. If there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: "Selecting One of Several Transmitters" on page 31 "Moving a Site Using the Mouse" on page 31 "Moving a Site to a Higher Location" on page 31 "Changing the Azimuth of the Antenna Using the Mouse" on page 31 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32.

6.2.4

Display Tips for Base Stations

Atoll allows to you to display information about base stations in a number of different ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object types data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information will lead to a cluttered display. For information on defining the label, see "Defining the Object Type Label" on page 35. Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip 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 every field in that object types data table, including from fields that you add. For information on defining the tooltips, see "Defining the Object Type Tip Text" on page 36. 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 "Defining the Display Type" on page 33. 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 "Defining the Display Type" on page 33.

6.2.5

Modelling Packet-switched Transmitters

By default, transmitters are not packet-capable in Atoll GSM/GPRS/EDGE documents. Therefore, when modelling a GPRS/EDGE-capable network, it is important to correctly configure it: 1. Verify the definition of the existing coding schemes (see "Opening the Coding Schemes Table" on page 411). 2. Correctly define the coding scheme configuration (see "Creating or Modifying a Coding Scheme Configuration" on page 412). 3. For each packet-capable transmitter, select the GPRS/EDGE Transmitter check box to identify the transmitter as GPRS/EDGE-capable (see "Transmitter Description" on page 193).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

209

Atoll User Manual 4. Choose configuration from the Coding Scheme Configuration list that is consistent with the transmitters configuration, and that is also consistent with other parameters, such as, HCS layers, frequency bands, and cell types. For example, if the cell type assigned to the transmitter is "Concentric Cell 1800," it would be illogical to choose "GPRS 900" as the configuration (see "Transmitter Description" on page 193).

6.2.6

Creating a Repeater
A repeater receives, amplifies, and re-transmits the radiated or conducted RF carrier both in downlink and uplink. It has a donor side and a server side. The donor side receives the signal from a donor transmitter, repeater, or remote antenna. This signal might be carried by different types of links such as radio link or microwave link. The server side re-transmits the received signal. Atoll models RF repeaters and microwave repeaters. The modelling focuses on: The additional coverage these systems provide to transmitters in the downlink. The UL total gain value in service areas studies (effective service area and UL Eb/Nt service area) and the noise rise generated at the donor transmitter by the repeater.

In this section, the following are explained: "Creating and Modifying Repeater Equipment" on page 210 "Placing a Repeater on the Map Using the Mouse" on page 210 "Creating Several Repeaters" on page 211 "Defining the Properties of a Repeater" on page 211 "Tips for Updating Repeater Parameters" on page 212. Note: Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor transmitter are amplified.

6.2.6.1

Creating and Modifying Repeater Equipment

You can define repeater equipment to be assigned to each repeater in the network. To create or modify repeater equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Repeaters > Equipment from the context menu. The Repeater Equipment table appears. 4. To create repeater equipment, enter the following in the row marked with the New Row icon ( a. Enter a Name and Manufacturer for the new equipment. b. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. c. 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 ( dialogue. ) on the General tab of the repeater Properties ):

d. Enter a Max. Downlink Power. This parameter is used to ensure that the downlink power is not exceeded after amplification by the repeater. Note: Uplink losses and noise figures are not modelled in GSM/GPRS/EDGE so any value entered into the Max. Uplink Power column will not be used. The column is included to ensure consistency with other technologies.

e. If desired, enter an Internal Delay and Comments. These fields are for information only and are not used in calculations. 5. To modify repeater equipment, change the parameters in the row containing the repeater equipment you wish to modify.

6.2.6.2

Placing a Repeater on the Map Using the Mouse

In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. For information on creating a remote antenna, see "Creating a Remote Antenna" on page 212.

210

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder of the Explorer windows Data tab, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Repeater from the menu. 4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tooltip and label display the same information as displayed for the donor. As well, its tooltip identifies the repeater and the donor. In the Explorer window, the repeater is found in the Transmitters folder of the Data tab under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 211. Note: You can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter or repeater. ) on the Radio toolbar.

6.2.6.3

Creating Several Repeaters

In Atoll, the characteristics of each repeater are stored in the Repeaters table. You can create several repeaters at the same time by pasting the information into the Repeaters table: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document. Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

6.2.6.4

Defining the Properties of a Repeater

To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or from the Transmitters folder of the Explorer windows Data tab. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: You can change the Name of the repeater. By default, repeaters are named "RepeaterN" where "N" is a number assigned as the repeater is created. You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another repeater, or a remote antenna. Clicking the Browse button ( ) opens the Properties dialogue of the donor.

You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Properties dialogue of the site. You can enter a Position relative to site location, if the repeater is not located on the site itself. You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties dialogue of the equipment. You can change the Amplification gain. The amplification gain is used in the link budget to evaluate the repeater total gain.

4. Click the Donor Side tab. You can modify the following parameters: Under Donor-Repeater Link, select a Link Type. If you select Microwave Link, enter the Propagation Losses and continue with step 5. If you select Air Link, 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. Important: If you want to create a remote antenna, you must select Optical Fibre Link. If you selected Air Link under Donor-Repeater Link, enter the following information under Antenna:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

211

Atoll User Manual i. Select a Model from the list. You can click the Browse button ( antenna. ) to access the properties of the

ii. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the transmitter as given by the DTM. iii. Enter the Azimuth and the Mechanical Downtilt. Note: You can click the Calculate button to update azimuth and downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.

If you selected Air Link 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 ( the feeder. ) to access the properties of

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 Data tab of the Explorer window) 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 Under Antennas, you can modify the following parameters: i. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the site as given by the DTM.

ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and, if applicable, the Additional Electrical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater coverage side correspond to the characteristics of the donor. iii. 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. For information on working with data tables, see "Working with Data Tables" on page 53. Under Feeders, you can modify the following information: i. Select a Type of feeder from the list. You can click the Browse button ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at Reception. Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.

6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

6.2.6.5

Tips for Updating Repeater Parameters

Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: You can update the calculated azimuth and downtilt of the donor-side antennas of all repeaters by selecting Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu. You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side Propagation Losses 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 select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 31) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32).

6.2.7

Creating a Remote Antenna

Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optic fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise.

212

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks In certain cases, you might want to model a remote antenna with equipment or a remote antenna connected to a base station that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a Repeater" on page 210. In this section, the following are explained: "Placing a Remote Antenna on the Map Using the Mouse" on page 213 "Creating Several Remote Antennas" on page 213 "Defining the Properties of a Remote Antenna" on page 213 "Tips for Updating Remote Antenna Parameters" on page 214.

6.2.7.1

Placing a Remote Antenna on the Map Using the Mouse

In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the Transmitters folder of the Explorer windows Data tab, or directly on the map. Note: Ensure that the remote antennas donor transmitter does not have any antennas.

2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Remote Antenna from the menu.

) on the Radio toolbar.

4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tooltip and label display the same information as displayed for the donor transmitter. As well, its tooltip identifies the remote antenna and the donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 213. Note: You can see to which base station the remote antenna is connected by clicking it; Atoll displays a link to the donor transmitter.

6.2.7.2

Creating Several Remote Antennas

In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. You can create several remote antennas at the same time by pasting the information into the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document. Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

6.2.7.3

Defining the Properties of a Remote Antenna

To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or from the Transmitters folder of the Explorer windows Data tab. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: You can change the Name of the remote antenna. By default, remote antennas are named "RemoteAntennaN" where "N" is a number assigned as the remote antenna is created. You can change the Donor transmitter by selecting it from the Donor list. Clicking the Browse button ( opens the Properties dialogue of the donor transmitter. )

You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the site. You can enter a Position relative to site location, if the remote antenna is not located on the site itself. Note: A remote antenna does not have equipment.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

213

Atoll User Manual 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 Data tab of the Explorer window) 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 Under Antennas, you can modify the following parameters: i. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the site as given by the DTM.

ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and, if applicable, the Additional Electrical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater coverage side correspond to the characteristics of the donor transmitter. iii. 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. For information on working with data tables, see "Working with Data Tables" on page 53. Under Feeders, you can modify the following information: i. Select a Type of feeder from the list. You can click the Browse button ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at 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 5: Managing Calculations in Atoll.

6.2.7.4

Tips for Updating Remote Antenna Parameters

Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: You can update the calculated azimuth and downtilt of the donor-side antennas of all remote antennas by selecting Remote Antennas > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu. You can update the propagation losses of all off-air remote antennas by selecting Remote Antennas > Calculate Donor Side Propagation Losses from the Transmitters context menu. 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 select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 31) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32).

6.2.8

Setting the Working Area of an Atoll Document

When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project might cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the sites that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of sites covered by a coverage prediction, each with its own advantages: Filtering the desired sites You can simplify the selection of sites to be studied by using a filter. You can filter sites according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 84. This enables you to keep only the base stations with the characteristics you want to study. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 74. Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings might not be significant. In a larger project, especially when you are making repeated studies in order to see the effects of small changes in site configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible.

214

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks It is important not to confuse the computation zone and the focus zone or hot spot zone. The computation zone defines the area where Atoll computes path loss matrices, coverage predictions, interference matrices, etc., while the focus zone or hot spot zone is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 223. You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.

6.2.9

Studying a Single Base Station

As you create a site, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of sites can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the site you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of sites once you have optimised the settings for each individual site. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Atoll enables you to assign both a main propagation model, with a shorter radius and a higher resolution, and an extended propagation model, with a longer radius and a lower resolution. By using a calculation radius, Atoll limits the scope of calculations to a defined area. By using two matrices, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter, while reducing calculation time by using an extended matrix with a lower resolution. You can assign a propagation model to all transmitters at once, to a group of transmitters, or to a single transmitter. Assigning a propagation model is explained in "Assigning a Propagation Model" on page 221. In this section, the following are explained: "Making a Point Analysis to Study the Profile" on page 215 "Studying Signal Level Coverage" on page 216.

6.2.9.1

Making a Point Analysis to Study the Profile

In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a GSM/ GPRS/EDGE user. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 221. To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Profile tab. 5. The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude (in metres) is reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results might display two additional attenuations peaks. The total attenuation is displayed above the main peak. The results of the analysis are displayed at the top of the Profile tab: The received signal strength of the selected transmitter The propagation model used The shadowing margin and the cell edge coverage probability used for calculating it The distance between the transmitter and the receiver.

You can change the following options at the top of the Profile tab: Transmitter: Select the transmitter from the list. Subcell: Select the subcell to be analysed. Display Geo Data Only: Select the Display Geo Data Only check box if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate nor display signal levels and losses. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

215

Atoll User Manual 6. Right-click the Profile tab to choose one of the following commands from the context menu: Properties: Select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. You can change the following: - Change the X and Y coordinates to change the present position of the receiver. - Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Select Signal Level, Path loss, and Total losses from the Result Type list. - You can select the Indoor Coverage check box to add indoor losses. Link Budget: Select Link Budget to display a dialogue with the link budget. Model Details: Select Model Details to display a text document with details on the displayed profile analysis. Model details are only available for the standard propagation model.

Figure 6.110: Point Analysis Tool - Profile tab

6.2.9.2

Studying Signal Level Coverage

As you are building your radio-planning project, you might want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single site. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. Note: You can use the same procedure to study the signal level coverage of several sites by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 69.

To study the signal level coverage of a single base station: 1. Click the Data tab of the Explorer window. 2. Right-click the transmitter folder and select Group By > Sites from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated.

Tip:

If you wish to study only sites by their status, at this step you could group them by status.

3. Select the propagation parameters to be used in the coverage prediction: a. Click the Expand button ( ) to expand the Transmitters folder.

b. Right-click the group of transmitters you want to study. The context menu appears. c. Select Open Table from the context menu. A table appears with the properties of the selected group of transmitters. d. In the table, you can configure two propagation models: one for the main matrix, with a shorter radius and a higher resolution, and another for the extended matrix, with a longer radius and a lower resolution. By calculating two matrices you can reduce the time of calculation by using a lower resolution for the extended matrix and you can obtain more accurate results by using propagation models best suited for each distance for the main and extended matrices.

216

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks e. In the Main Matrix column: f. Select a Propagation Model Enter a Radius and Resolution.

If desired, in the Extended Matrix column: Select a Propagation Model Enter a Radius and Resolution.

g. Close the table. 4. Right-click the object either in the Explorer window or on the map. The context menu appears. 5. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. The Study Types dialogue lists the studies available. They are divided into Standard Studies, supplied with Atoll, and Customised Studies. Unless you have already created some customised studies, the Customised Studies list will be empty. 6. Select Coverage by Signal Level and click OK. The coverage prediction Properties dialogue appears. 7. You can configure the following parameters in the Properties dialogue: General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient:

Size of the Coverage Prediction

City Centre City County State Country

Display Resolution
5m 20 m 50 m 100 m According to the size of the country

Note:

If you create a new coverage prediction from the context menu of either the Transmitters or Predictions folder, you can select the sites using the Group By, Sort, and Filter buttons under Configuration. Because you already selected the target sites, however, only the Filter button is available.

Condition tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel (see Figure 6.111). At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range or Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range. In Figure 6.111, a Specified Reception Threshold less than or equal to -105 dBm will be considered. Under Server, select "All" to consider all servers. If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select which TRX type to consider by selecting it from the Reception from Subcells list.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

217

Atoll User Manual

Figure 6.111: Condition settings for a signal level coverage prediction Display tab: You can modify how the results of the coverage prediction will be displayed. Under Display Type, select "Value Intervals." Under Field, select "Best signal level." Selecting "All" or "Best signal level" on the Conditions tab will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best signal level" necessitates, however, the longest time for calculation. You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 32. You can create a tooltip 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 tooltip. 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 might make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results.

Note:

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined simulation and run it immediately OK: Click OK to save the defined simulation without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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 on the Data tab. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button ( ) beside the coverage prediction in the Predictions ). ), Atoll only calculates unlocked coverage predictions (

6.2.10

Studying Base Stations

When you make a coverage prediction on a group of base stations, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. The computation zone is the area covered by the rectangle defined by the calculation radius. When you set the propagation model, you can define the calculation radius. For information on setting the propagation model and defining the calculation radius, see "Assigning a Propagation Model" on page 221. Figure 6.112 gives an example of a computation zone. In Figure 6.112, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction.

218

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.112: An example of a computation zone Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main propagation model with a shorter radius (displayed with a blue square in Figure 6.112) and a higher resolution and an extended propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower resolution path loss matrices outside the area covered by the main propagation model. In this section, the following are explained: "Path Loss Matrices" on page 219 "Assigning a Propagation Model" on page 221 "The Calculation Process" on page 223 "Creating a Computation Zone" on page 223 "Setting Transmitters as Active" on page 224 "Signal Level Coverage Predictions" on page 225 "Analysing a Coverage Prediction" on page 233 "Printing and Exporting Coverage Prediction Results" on page 241.

6.2.10.1

Path Loss Matrices

Path loss is caused by diffraction, scattering and reflection in the transmitter-receiver path and is calculated using the propagation model. In Atoll, the path loss matrices are needed for all base stations that are active, filtered, and whose propagation zone intersects a rectangle containing the computation zone (for an explanation of the computation zone, see "Studying Signal Level Coverage" on page 216). The path loss matrices must be calculated before predictions and simulations can be made.

Storing Path Loss Matrices

Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. in the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

219

Atoll User Manual When you save the path loss matrices to an external directory, Atoll creates: One file per transmitter with the extension LOS for its main path loss matrix A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.

To set the storage location of the path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss matrices and the location for the shared path loss matrices: Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are loading path loss matrices from a shared location, where you store your changes to shared path loss matrices. Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally. Note: Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private Directory.

Caution:

When you save the path loss files externally, the external files are updated as soon as calculations are performed and not only when you save the Atoll document. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it if you have updated the path loss matrices.

Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the common path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual.

5. Click OK.

Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check if the path loss matrices are valid: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The Available Results table lists the following information for the path loss matrix for each transmitter: 5. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 6. Select one of the following display options: Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.

The Available Results table lists the following information for each displayed path loss matrix: Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a boolean field indicating whether or not the path loss matrix is valid. Origin of Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed. Tuned: If the Tuned check box has been selected, the initial path loss matrix obtained by the propagation model has been tuned by the use of real measurement points. See ""Tuning Path Loss Matrices Using Measurement Data" on page 173" for more information.

7. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 6.113) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.

220

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.113: Path loss matrix statistics

6.2.10.2

Assigning a Propagation Model

In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 222, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 222, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 221, this is the propagation model that will be used for all transmitters, except for those to which you will assign a propagation model either individually or as part of a group. Important: 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. 3. If you have assigned a default propagation model for coverage predictions, as described in "Assigning a Default Propagation Model for Coverage Predictions" on page 223, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following methods of assigning a propagation model are explained: "Assigning a Propagation Model to All Transmitters" on page 221 "Assigning a Propagation Model to a Group of Transmitters" on page 222 "Assigning a Propagation Model to One Transmitter" on page 222 "Assigning a Default Propagation Model for Coverage Predictions" on page 223. Note: If you are modelling multi-band transmitters, you can assign a different propagation model to each frequency band. For more information, see "Advanced Modelling of Multi-Band Transmitters" on page 415.

Assigning a Propagation Model to All Transmitters

In Atoll, you can choose a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

221

Atoll User Manual 6. If desired, under Extended Matrix: Select a Propagation Model Enter a Radius and Resolution.

7. Click OK. The selected propagation models will be used for all transmitters. Note: If you set a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 222 after having assigned a propagation model to all transmitters, you will override this entry.

Assigning a Propagation Model to a Group of Transmitters

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

4. Click the Expand button (

) to expand the Transmitters folder.

5. Right-click the group of transmitters to which you want to assign a main and extended propagation model. The context menu appears. 6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected group. For each transmitter, you can set the propagation model parameters in the following columns: Main Propagation Model Main Calculation Radius (m) Main Resolution (m) Extended Propagation Model Extended Calculation Radius (m) Extended Resolution (m)

7. To enter the same values in one column for all transmitters in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

Assigning a Propagation Model to One Transmitter

If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previously made globally. The propagation model settings apply to all the subcells on the same transmitter. For example, if the BCCH is a 900 MHz subcell, the same propagation model is also assigned to a TCH_INNER 1800 MHz subcell. By defining a multi-band transmitter, you can assign propagation model-related settings that are optimised to the frequency band of each subcell when more than one frequency band is used on a transmitter. For more information on multi-band transmitters, see "Advanced Modelling of Multi-Band Transmitters" on page 415. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears.

222

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 5. Click the Propagation tab. 6. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

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

8. Click OK. The selected propagation models will be used for the selected transmitter.

Assigning a Default Propagation Model for Coverage Predictions

You can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters whose main propagation model is "(Default model)." To assign a default propagation model for coverage predictions: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Predictions tab. 5. Select a Default Propagation Model from the list. 6. Enter a Default Resolution. When you create a new coverage prediction, the default resolution is the value you enter here.

Tip:

By making the necessary entry in the atoll.ini file, if you clear the value entered in the Resolution box when you create a coverage prediction, Atoll will calculate the coverage prediction using the currently defined default resolution. That way, if you have many coverage predictions, you can change their resolution by changing the default resolution and recalculating the coverage predictions. Atoll will then calculate them using the updated resolution. For information on changing entries in the atoll.ini file, see the Administrator Manual.

7. Click OK. The selected propagation model will be used for coverage predictions for all transmitters whose main propagation model is "(Default model)."

6.2.10.3

The Calculation Process

When you create a coverage prediction and run it, either by clicking the Run button on the coverage prediction properties dialogue or by clicking the Calculate button ( ), Atoll follows the following process: 1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. For information on what can affect the validity of calculated path loss matrices, see the Technical Reference Guide. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button ( ). ) beside the coverage prediction 3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( in the Predictions folder. Notes: You can stop any calculations in progress by clicking the Stop Calculations button ( the toolbar. ) in

When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.

6.2.10.4

Creating a Computation Zone

To create a computation zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Computation Zone folder. The context menu appears. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

223

Atoll User Manual 4. Select Draw from the context menu. 5. Draw the computation zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. The computation zone is delimited by a red line. If you clear the computation zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a computation zone using one of the following methods: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and selecting Use as > Computation Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a computation zone the size of the map window by selecting Fit to Map Window from the context menu.

Once you have created a computation zone, you can use Atolls polygon editing tools to edit it. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44. Note: You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: Saving the computation zone in the user configuration: For information on exporting the computation zone in the user configuration, see "Exporting a User Configuration" on page 79. Exporting the computation zone: You can export the computation zone by rightclicking the Focus Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

6.2.10.5

Setting Transmitters as Active

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Before you define a coverage prediction, you must ensure that all the transmitters on the sites you wish to study have been activated. In the Explorer window, active transmitters are indicated with a red icon ( ) in the Transmitters folder and with the defined colour on the map and inactive transmitters are indicated with an empty icon ( )in the Transmitters folder and on the map. You can set an individual transmitter as active from its context menu or you can set several transmitters as active by activating them from the Transmitters context menu, by activating the transmitters from the Transmitters table, or by selecting the transmitters with a zone and activating them from the zones context menu. To set an individual transmitter as active: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter you want to activate. The context menu appears. 4. Select Active Transmitter from the context menu. The transmitter is now active. To set more than one transmitter as active using the Transmitters context menu: 1. Click the Data tab of the Explorer window. 2. Select the transmitters you want to set as active: To set all transmitters as active, right-click the Transmitters folder. The context menu appears. To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and right-click the group of transmitters you want to set as active. The context menu appears. Note: For information on grouping data objects, see "Grouping Data Objects" on page 69.

3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one transmitter as active using the Transmitters table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears.

224

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 3. Select Open Table. The Transmitters table appears with each transmitters parameters in a second row. 4. For each transmitter that you want to set as active, select the check box in the Active column. To set transmitters as active using a zone: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder.

3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. Note: If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 41.

4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll. Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects. Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the Atoll computing server application on other workstations or on servers. Once the computing server application is installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on the network. For information on distributed calculations, see the Administrator Manual.

6.2.10.6

Signal Level Coverage Predictions

Atoll offers a series of standard coverage predictions that are common to all radio technologies. Coverage predictions specific to GSM/GPRS/EDGE are covered in "Interference Coverage Predictions" on page 320 and "Packet-Specific Coverage Predictions" on page 328. 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 study which will appear in the Study Types dialogue. You can also select Duplicate from the coverage predictions context menu to create a copy. By duplicating an existing prediction that has the parameters you wish to study, you can create a new coverage prediction more quickly. 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 import 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 "Exporting a User Configuration" on page 79. The following standard coverage predictions are explained in this section: "Making a Coverage Prediction by Signal Level" on page 225 "Making a Coverage Prediction by Transmitter" on page 227 "Making a Coverage Prediction on Overlapping Zones" on page 232.

6.2.10.6.1

Making a Coverage Prediction by Signal Level

A coverage prediction by signal level allows you to predict the best signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by signal level: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Signal Level and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.114). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

225

Atoll User Manual In Figure 6.114, a Specified Reception Threshold less than or equal to -105 dBm will be considered. Under Server, select "All" to consider all servers. If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select which TRX type to consider by selecting it from the Reception from Subcells list.

Figure 6.114: Condition settings for a coverage prediction by signal level 7. Click the Display tab. If you choose to display the results by best signal level, the coverage prediction results will be in the form of thresholds. If you choose to display the results by signal level, the coverage prediction results will be arranged according to transmitter. For information on adjusting the display, see "Display Properties of Objects" on page 32. 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. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 6.115).

Figure 6.115: Coverage prediction by signal level

226

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Note:

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 230.

6.2.10.6.2

Making a Coverage Prediction by Transmitter

A coverage prediction by transmitter allows you to predict which server is the best at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. The type of server you base the coverage prediction on determine the type of coverage prediction by transmitter you make. In this section, the following scenarios are explained: "Making a Coverage Prediction by Transmitter Based on the Best Signal Level" on page 227 "Making a Coverage Prediction by Transmitter Based on the Best Signal Level by HCS Layer" on page 228 "Making a Coverage Prediction by Transmitter on HCS servers" on page 229 "Making a Coverage Prediction by Transmitter for Highest Priority HCS Server" on page 230 "Making a Coverage Prediction by Transmitter Based on the Best Idle Mode Reselection Criterion (C2)" on page 230.

Making a Coverage Prediction by Transmitter Based on the Best Signal Level

When you base a coverage prediction by transmitter on the best signal level, Atoll will consider the best signal level on each pixel. A coverage prediction by transmitter based on the best signal level is more suitable for a network that does not have HCS layers. If the network has HCS layers, a coverage prediction by transmitter based on the best signal level can give misleading results as the best signal on any pixel will usually be on a macro layer, although not all users will necessarily connect to it. To make a coverage prediction by transmitter based on the best signal level: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Transmitter and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.116). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range. In Figure 6.116, a Specified Reception Threshold less than or equal to -105 dBm will be considered. 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 400). Enter a hand-over margin in the With a Margin text box. The default value is "4 dB." If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select which TRX type to consider by selecting it from the Reception from Subcells list.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

227

Atoll User Manual

Figure 6.116: Condition settings for a coverage prediction by transmitter 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Note: You can also predict which server is the second best server on each pixel by selecting "Second Best Signal Level" on the Conditions tab and setting "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. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Transmitter and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. Under Configuration on the General tab, click the Click the Group By button. The Group dialogue appears. Select "HCS Layers" in the Available Fields list and click in this order list. Click OK to close the Group dialogue. to move it to the Group these fields

6. Click the Condition tab (see Figure 6.116). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

228

Chapter 6: GSM/GPRS/EDGE Networks Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range. In Figure 6.116, a Specified Reception Threshold less than or equal to -105 dBm will be considered. 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 400). Enter a hand-over margin in the With a Margin text box. The default value is "4 dB." If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select which TRX type to consider by selecting it from the Reception from Subcells list.

7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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 Note: You can also predict which server is the second best server per HCS layer on each pixel by selecting "Second Best Signal Level per HCS Layer" on the Conditions tab and setting "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. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Transmitter and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.116). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range. In Figure 6.116, a Specified Reception 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 400). Enter a HO margin in the With a Margin text box. The default value is "4 dB." If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select which TRX type to consider by selecting it from the Reception from Subcells list.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

229

Atoll User Manual 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Transmitter and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.116). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range. In Figure 6.116, a Specified Reception Threshold less than or equal to -105 dBm will be considered. 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 400). Enter a hand-over margin in the With a Margin text box. The default value is "4 dB." If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select which TRX type to consider by selecting it from the Reception from Subcells list.

7. 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 "Display Properties of Objects" on page 32. 8. Click OK to save your settings. 9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. 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)

230

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Transmitter and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.117). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all BCCH subcells as the lower end of the signal level range. In Figure 6.117, a Specified Reception Threshold less than or equal to -105 dBm will be considered. 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. You can select the Indoor Coverage check box to add indoor losses.

Figure 6.117: Condition settings for a coverage prediction by transmitter based on Best C2 7. 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 be displayed with the same colour as that defined for each transmitter. For information on defining transmitter colours, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

231

Atoll User Manual

6.2.10.6.3

Making a Coverage Prediction on Overlapping Zones

Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction of overlapping zones on the signal level, path loss, or total losses within a defined range. To make a coverage prediction on overlapping zones: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Overlapping Zones and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.118). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range. In Figure 6.118, a Specified Reception 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 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 400). Enter a HO margin in the With a Margin text box. The default value is "4 dB." If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select which TRX type to consider by selecting it from the Reception from Subcells list.

Figure 6.118: Condition settings for a coverage prediction on overlapping zones 7. Click the Display tab. For a coverage prediction on overlapping zones, the Display Type "Value Intervals" based on the Field "Number of servers" is selected by default. Each overlapping zone will then be displayed in a colour corresponding to the number of servers received per pixel. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately

232

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Note: By changing the parameters selected on the Condition tab and by selecting different results to be displayed on the Display tab, you can calculate and display information other than that which has been explained in the preceding sections.

6.2.10.7

Analysing a Coverage Prediction

Once you have completed a study, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 7. of "Studying Signal Level Coverage" on page 216). If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which studies to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following tools are explained: "Displaying the Legend Window" on page 233 "Displaying Coverage Prediction Results Using Tooltips" on page 233 "Using the Point Analysis Reception Tab" on page 233 "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 234 "Viewing Coverage Prediction Statistics" on page 236 "Comparing Coverage Predictions: Examples" on page 237.

6.2.10.7.1

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

6.2.10.7.2

Displaying Coverage Prediction Results Using Tooltips

You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltips. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 7. of "Studying Signal Level Coverage" on page 216). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined in the Display tab of the coverage prediction properties (see Figure 6.119).

Figure 6.119: Displaying coverage prediction results using tooltips

6.2.10.7.3

Using the Point Analysis Reception Tab

Once you have calculated the coverage prediction, you can use the Point Analysis tool. 1. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 6.120). The predicted signal level from different transmitters is reported in the Reception tab 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

233

Atoll User Manual 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 tooltip. At the top of the Reception tab, you can select the Subcell and the HCS Layer to be analysed. If you select nothing from the HCS Layer list, the signals from all HCS layers will be studied.

Figure 6.120: Point Analysis Window - Reception tab 3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue appears. Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select the Indoor Coverage check box to add indoor losses.

6.2.10.7.4

Creating a Focus or Hot Spot Zone for a Coverage Prediction Report

The focus and hot spot zones define an area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spot zones in addition to the focus zone. Focus and hot spot zones are taken into account whether or not they are visible. It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the area where Atoll computes path loss matrices, coverage studies, etc., while the focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones. To define a focus zone or hot spot zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. Select Draw from the context menu. 5. Draw the focus or hot spot zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the focus or hot spot zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot zone by right-clicking it and selecting Use as > Focus Zone or Use as > New Hot Spot from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot spot zones, you can import the name given to each zone as well. Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map Window from the context menu.

Once you have created a focus or hot spot zone, you can use Atolls polygon editing tools to edit it. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44.

234

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Notes: You can save the focus zone or hot spot zones, so that you can use it in a different Atoll document, in the following ways: Saving the focus zone in the user configuration: For information on exporting the focus zone in the user configuration, see "Exporting a User Configuration" on page 79. - Exporting the focus zone or hot spot zones: You can export the focus zone or hot spot zones by right-clicking the Focus Zone or the Hot Spot Zones folder on the Data tab of the Explorer window and selecting Export from the context menu.. You can include population statistics in the focus or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113.

6.2.10.7.5

Displaying a Coverage Prediction Report

Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage predictions Properties dialogue. The coverage prediction report is displayed in a table. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 58. Atoll bases the report on the area covered by the focus zone and hot spot zones; if no focus zone is defined, Atoll will use the computation zone. Using a focus zone enables you to create a report without the border effect. In other words, the results of a coverage prediction are delimited by the computation zone; results close to the border are influenced by fact that no calculations have been made outside the computation zone. Basing a report on a focus zone that is smaller than the computation zone eliminates the border effect. By using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot zone must be defined before you display a report; it is not necessary to define it before computing coverage. The focus or hot spot zone does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 234. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. The Open dialogue appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the focus zone if available or on the hot spot zones and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. to move it up or

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

235

Atoll User Manual 4. 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. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. The Open dialogue appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. 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 spot zone: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. 2. Display the report as explained above. 3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears. 4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the population map: "Population" (Population): The number of inhabitants covered. "Population" (% Population): The percentage of inhabitants covered. "Population" (Population [total]): The total number of inhabitants inside the zone. Note: Depending on display settings, you can create a report showing population thresholds, as well. to move it up or

Atoll saves the names of the columns you select and will automatically select them the next time you create a coverage prediction report. 5. Click OK. If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be value data (revenue, number of customers, etc.) or density data (revenue/km, number of customer/km, etc.). Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable Versus Non Integrable Data" on page 129.

6.2.10.7.6

Viewing Coverage Prediction Statistics

Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage study colours, interval steps, and shading as defined in the Display tab of the coverage predictions Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spot zones are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before computing coverage. The focus zone does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 234.

236

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To display the statistics on a coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction whose statistics you want to display. The context menu appears. 4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined by the focus zone (see Figure 6.124). Under Histogram Based on Covered Areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Detailed Results section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics Based on Study Conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.

Figure 6.121: Histogram of a coverage prediction by signal level

6.2.10.7.7

Comparing Coverage Predictions: Examples

Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison study coverage in one of the following ways: Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both studies 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 one of the two predictions with another colour and pixels covered only by the second prediction with a third colour (for example, pixels covered by both studies are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).

To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

237

Atoll User Manual 6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage between them. In this section, the following examples are explained: "Example 1: Studying the Effect of a New Base Station" on page 238 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 240.

Example 1: Studying the Effect of a New Base Station

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how you can verify if a newly added base station improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 225. The results are displayed in Figure 6.122. An area with poor coverage is visible on the right side of the figure.

Figure 6.122: Signal level coverage prediction of existing network A new base station is added, either by creating the site and adding the transmitters, as explained in "Creating a GSM/ GPRS/EDGE Base Station" on page 192, or by placing a station template, as explained in "Placing a New Station Using a Station Template" on page 203. Once the new site base station been added, the original coverage prediction can be recalculated, but then it will be impossible to compare the two predictions. Instead, the original signal level coverage prediction can be copied by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new site (see Figure 6.123).

238

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.123: Signal level coverage prediction of network with new base station Now you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the Display tab, you can choose how you want the results of the comparison to be displayed. You can choose among: Intersection Union Difference

In order to see what changes adding a new base station made, you should choose Difference. 5. Click OK to create the comparison. The comparison in Figure 6.124, shows clearly the area covered only by the new base station.

Figure 6.124: Comparison of both signal level coverage predictions

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

239

Atoll User Manual

Example 2: Studying the Effect of a Change in Transmitter Tilt

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 227. The results are displayed in Figure 6.125. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated with a red oval in the figure.

[ Figure 6.125: Coverage prediction by transmitter of existing network You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue. Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it will be impossible to compare the two predictions. Instead, the original coverage prediction by can be copied by selecting Duplicate from its context menu. The copy is then calculated to show how modifying the antenna tilt has affected coverage (see Figure 6.126).

[ Figure 6.126: Coverage prediction by transmitter of network after modifications As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change in propagation, you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the Display tab, you can choose how you want the results of the comparison to be displayed. You can choose among: Intersection Union Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

240

Chapter 6: GSM/GPRS/EDGE Networks 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 6.127, shows clearly the increase in coverage due to the change in antenna tilt.

[ Figure 6.127: Comparison of both transmitter coverage predictions

6.2.10.8

Printing and Exporting Coverage Prediction Results

Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. 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 65. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 46. 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 49.

6.2.11

Planning Neighbours
You can set neighbours for each transmitter manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you set. When allocating neighbours, the transmitter to which you are allocating neighbours is referred to as the reference transmitter. The transmitters that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours automatically to all active and filtered transmitters, Atoll allocates neighbours only to the transmitters within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbours only to the transmitters within the computation zone. The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo tab in the Explorer window is selected. Usually, you will allocate neighbours globally during the beginning of a radio planning project. Afterwards, you will allocate neighbours to base stations or transmitters as you add them. You can automatically allocate neighbours to all the transmitters in the document, or you can define a group of transmitters either by using a focus zone or by grouping transmitters in the Explorer window and automatically allocate neighbours to the defined group. For information on creating a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 234. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 69. Atoll supports the following neighbour types in a GSM/GPRS/EDGE network: Intra-technology neighbours: Intra-technology neighbours are transmitters defined as neighbours that also use GSM/GPRS/EDGE. Inter-technology neighbours: Inter-technology neighbours are transmitters defined as neighbours that use a technology other than GSM/GPRS/EDGE.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

241

Atoll User Manual In this section, the following are explained: "Importing Neighbours" on page 242 "Defining Exceptional Pairs" on page 242 "Configuring Importance Factors for Neighbours" on page 242 "Allocating Neighbours Automatically" on page 243 "Checking Automatic Allocation Results" on page 245 "Allocating and Deleting Neighbours per Transmitter" on page 248 "Calculating the Importance of Existing Neighbours" on page 250 "Checking the Consistency of the Neighbour Plan" on page 251 "Exporting Neighbours" on page 252.

6.2.11.1

Importing Neighbours
You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Data tab of the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 63.

6.2.11.2

Defining Exceptional Pairs

In Atoll, you can define neighbour constraints that can be taken into consideration during the automatic allocation of neighbours. Exceptional pairs can be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table from the context menu. The Transmitters table appears. 4. Right-click the transmitter for which you want to define neighbour constraints. The context menu appears. 5. Select Record Properties from the context menu. The transmitters Properties dialogue appears. 6. Click the Intra-technology Neighbours tab. 7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( a. Select the transmitter from the list in the Neighbours column. b. In the Status column, select one of the following: Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell. ):

8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table by right-clicking the Transmitters folder and selecting Neighbours > Intra-Technology Exceptional Pairs.

6.2.11.3

Configuring Importance Factors for Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible intra-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. On the Intra-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency Factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 243.

242

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 243.

5. Click OK.

6.2.11.4

Allocating Neighbours Automatically

Atoll can automatically allocate intra-technology neighbours in a GSM/GPRS/EDGE network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. To automatically allocate intra-carrier GSM/GPRS/EDGE neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. On the Neighbours tab, you can set the following parameters: Max. Inter-site Distance: Set the maximum distance between the reference transmitter and a possible neighbour. Max. Number of Neighbours: Set the maximum number of intra-carrier neighbours that can be allocated to a transmitter. This value can be either set here for all transmitters, or specified for each transmitter in the Transmitters table, in which case the value in the Transmitters table is used. Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of transmitters for automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum signal level which must be provided by reference cell A and possible neighbour cell B. Handover Start: 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 transmitter (see Figure 6.128). Handover End: Enter the signal level which indicates 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 candidate neighbours (see Figure 6.128). 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 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.
Minimum signal level

Handover start

Handover end

candidateB referenceA Best server area of referenceA Best server area of candidateB

SA SB

[ Figure 6.128: The handover area between the reference transmitter and the potential candidate Take into account: You can define whether Atoll selects potential candidates by whose handover zone shared with the reference transmitter has the greatest surface area or greatest circuit traffic. The importance of this parameter can be defined in step 6. Select one of the following options: Covered Area: If you select Covered Area, Atoll will select the potential candidates whose handover zone shared with the reference transmitter has the greatest surface area. Covered Traffic: If you select Covered Traffic, Atoll will select the potential candidates whose handover zone shared with the reference transmitter covers the most circuit traffic (Erlangs). Atoll considers the traffic maps used for the default traffic analysis to calculate the covered traffic.

% Min. Covered Area: Enter, in percentage, the amount of covered area or traffic of the reference transmitters coverage that another transmitter must cover to be considered as a potential candidate. The % Min. Covered Area is the percentage of the area described by S A S B in Figure 6.128. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

243

Atoll User Manual 5. Select the desired calculation parameters: Force co-site transmitters as neighbours: Select the Force co-site transmitters as neighbours check box if you want transmitters located on the same site as the reference cell to be automatically considered as neighbours. The importance of this parameter can be defined in step 6. Force adjacent transmitters as neighbours: Select the Force adjacent transmitters as neighbours check box if you want transmitters that are adjacent to the reference transmitter to be automatically considered as neighbours. A transmitter is considered adjacent if there is at least one pixel in the reference transmitters coverage area where the possible neighbour transmitters is the best server, or where the possible neighbour transmitter is the second best server (respecting the handover margin). The importance of this parameter can be defined in step 6. Force neighbour symmetry: Select the Force neighbour symmetry check box if you want neighbour relations to be reciprocal. In other words, a reference transmitter will be a possible neighbour to all of the transmitters that are its neighbours. If the neighbour list of any transmitter is full, the reference transmitter will not be added as a neighbour and that transmitter will be removed from the list of neighbours of the reference transmitter. Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 242. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.

6. Click the Importance Weighting button to set the relative importance of possible neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide): Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: If you have selected the Force adjacent transmitters as neighbours check box in step 5., set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. Co-site Factor: If you have selected the Force co-site transmitters as neighbours check box in step 5., set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter.

7. Click Run. Atoll begins the process of allocating intra-technology neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. Transmitter: The name of the reference transmitter. Number: The total number of neighbours allocated to the reference transmitter. Maximum Number: The maximum number of neighbours that the reference transmitter can have. Neighbour: The transmitter that will be allocated as a neighbour to the reference transmitter. Importance (%): The importance as calculated with the options selected in step 6. Neighbours are ranked from the most to the least important. Cause: The reason Atoll has allocated the possible neighbour transmitter, as identified in the Neighbour column, to the reference transmitter, as identified in the Transmitter column. Co-site Adjacency Symmetry Coverage Existing

Coverage: The amount of reference transmitters coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neighbour transmitter is best server or second best server.

8. Select the Commit check box for each neighbour you want to assign to a transmitter. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. At this point you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations,

244

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference transmitters. Neighbours are listed in the Intra-technology Neighbours tab of each transmitters Properties dialogue. Notes: A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint on the forbidden neighbour will be ignored by the algorithm because the neighbour already exists. When the options Force exceptional pairs and Force symmetry are selected, Atoll considers the constraints between exceptional pairs in both directions in order to respect symmetry. On the other hand, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event Viewer. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Exporting a User Configuration" on page 79.

6.2.11.4.1

Allocating Neighbours to a New Base Station

When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the transmitters of the new base station and other transmitters whose coverage area intersects with the coverage area of the transmitters of the new base station. To allocate neighbours to a new base station: 1. On the Data tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects" on page 69. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 243.

6.2.11.4.2

Allocating Neighbours to a New Transmitter

When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the transmitter and other transmitters whose coverage area intersects with the coverage area of the new transmitter. To allocate neighbours to a new transmitter: 1. Click the Data tab of the Explorer window. 2. In the Transmitters folder, right-click the new transmitter. The context menu appears. 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 243.

6.2.11.5

Checking Automatic Allocation Results

You can verify the results of automatic neighbour allocation in the following ways: "Displaying Neighbour Relations on the Map" on page 245 "Displaying the Coverage of Each Neighbour of a Transmitter" on page 247.

6.2.11.5.1

Displaying Neighbour Relations on the Map

You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference transmitter and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a transmitter on the map: 1. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

2. Select Display Options from the context menu. The Visual Management dialogue appears. 3. Under Intra-technology Neighbours, select the Display Links check box. 4. Click the Browse button ( ) beside the Display Links check box.

5. The Intra-technology Neighbour Display dialogue appears. 6. From the Display Type list, choose one of the following:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

245

Atoll User Manual Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a transmitter with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the transmitters neighbour links according to a value from the Intra-technology Neighbours table, or according to the neighbour cell type, the neighbour HCS layer, or the neighbour frequency band. Value Intervals: Select "Value Intervals" to colour the transmitters neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a transmitters neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

Tip:

You can display the number of handoff attempts for each transmitter-neighbour pair by first 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 along with "Value Intervals" as the Display Type. For information on adding a new field to a table, see "Adding a Field to an Object Types Data Table" on page 54.

Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you can display or hide neighbour link display types individually. For information on changing display properties, see "Display Properties of Objects" on page 32. 7. Select the Add to Legend check box to add the displayed neighbour links to the legend. 8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each neighbour link. 9. Click OK to save your settings. 10. Under Advanced, select which neighbour links to display: Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations where the selected transmitter is the reference transmitter and where the neighbour relation is not symmetric. Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations where the selected transmitter is neighbour and where the neighbour relation is not symmetric. Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the selected transmitter and the neighbour.

11. Click OK to save your settings. 12. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

13. Select Neighbours from the menu. The neighbours of a transmitter will be displayed when you select a transmitter. 14. Click a transmitter on the map to display the neighbour relations. When there is more than one transmitter with the same azimuth on the site, clicking the transmitter in the map window opens a context menu allowing you to select the transmitter you want (see "Selecting One of Several Transmitters" on page 31). Atoll displays the following information (see Figure 6.129) on the selected transmitter: The symmetric neighbour relations of the selected (reference) transmitter are indicated by a line. The outward neighbour relations are indicated by a line with an arrow pointing to the neighbour (e.g., see Site1_2(0) in Figure 6.129.). The inward neighbour relations are indicated by a line with an arrow pointing to the selected transmitter (e.g., see Site9_3(0) in Figure 6.129.).

In Figure 6.129, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward neighbour links have the same colour of the corresponding neighbour transmitters and the inward neighbour link has the same colour as the reference transmitter because it is a neighbour of Site9_3(0).

246

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

[ Figure 6.129: Neighbours of Site 22 In Figure 6.130, neighbour links are displayed according to the neighbour frequency band. You can view 900-900 and 900-1800 neighbour links. Here, all neighbour relations are symmetric.

Figure 6.130: 900-900 and 900-1800 Neighbours of Site 22_3(0) Note: You can use the same procedure to display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

6.2.11.5.2

Displaying the Coverage of Each Neighbour of a Transmitter

By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage areas of a transmitters neighbours and colour them according to any neighbour characteristic available in the Neighbours table. To display the coverage of each neighbour of a transmitter: 1. Create, calculate, and display a "Coverage by transmitter" prediction, with the Display Type set to "Discrete Values" and the Field set to Transmitter (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 227). 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

3. Select Display Options from the context menu. The Visual Management dialogue appears. 4. Under Intra-technology Neighbours, select the Display Coverage Areas check box. 5. Click the Browse button ( ) beside the Display Coverage Areas check box.

6. The Intra-technology Neighbour Display dialogue appears. 7. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage areas of a transmitters neighbours with a unique colour.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

247

Atoll User Manual Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the coverage areas of a transmitters neighbours according to a value from the Intra-technology Neighbours table. Value Intervals: Select "Value Intervals" to colour the coverage areas of a transmitters neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a transmitters neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each coverage area. 9. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

10. Select Neighbours from the menu. The neighbours of a transmitter will be displayed when you select a transmitter. 11. Click the Visual Management button ( ) in the Radio toolbar.

12. Click a transmitter on the map to display the coverage of each neighbour. When there is more than one transmitter with the same azimuth on the site, clicking the transmitter in the map window opens a context menu allowing you to select the transmittter you want (see "Selecting One of Several Transmitters" on page 31). 13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( Radio toolbar. ) in the

6.2.11.6

Allocating and Deleting Neighbours per Transmitter

Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Intra-Technology Neighbours tab of the Transmitter Properties dialogue. This section explains the following: "Allocating or Deleting Neighbours Using the Intra-Technology Neighbours Tab of the Transmitter Properties Dialogue" on page 248 "Allocating or Deleting Neighbours Using the Neighbours Table" on page 249 "Allocating or Deleting Neighbours on the Map" on page 249.

Allocating or Deleting Neighbours Using the Intra-Technology Neighbours Tab of the Transmitter Properties Dialogue
To allocate or delete GSM/GPRS/EDGE neighbours using the Intra-Technology Neighbours tab of the transmitters Properties dialogue: 1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Intra-Technology Neighbours tab. 4. If desired, you can enter the maximum number of neighbours in the Max Number of Neighbours text box. 5. To allocate a new neighbour: a. Under List, select the transmitter from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." 6. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the transmitter in the Neighbour column and the transmitter in the Transmitter column. 7. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the transmitter in the Neighbour column and the transmitter in the Transmitter column is deleted. 8. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 9. Click OK.

248

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Allocating or Deleting Neighbours Using the Neighbours Table

To allocate or delete GSM/GPRS/EDGE neighbours using the Neighbours table: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. Note: For information on working with data tables, see "Working with Data Tables" on page 53.

4. To allocate a neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." 5. To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the transmitter in the Neighbour column and the transmitter in the Transmitter column. 6. To make several neighbour relations symmetric: a. Click in the left margin of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each row separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. 7. To take all exceptionnal pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete some forced neighbours or some forbidden neighbours using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table, select the exceptional pairs, right-click the table and select Force Exceptional Pairs from the context menu. ), select a reference transmitter in the Transmitter column.

8. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the transmitter in the Neighbour column and the transmitter in the Transmitter column is deleted. 9. To delete several symmetric neighbour relations: a. Click in the left margin of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour.

Allocating or Deleting Neighbours on the Map

You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 245.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

249

Atoll User Manual To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters to the intra-technology neighbours list. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitters from the intra-technology neighbours. To add an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the intra-technology neighbour list of the reference transmitter. To remove an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the intra-technology neighbours list of the reference transmitter. To add an inward neighbour relation: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the intra-technology neighbours list of the reference transmitter. Notes: When there is more than one transmitter with the same azimuth on a site, clicking the transmitter in the map window opens a context menu allowing you to select the transmitter you want (see "Selecting One of Several Transmitters" on page 31). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

6.2.11.7

Calculating the Importance of Existing Neighbours

After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This weight is used by the AFP. If you have only partial importance values, you can use Atoll in order to complete this partial information. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 242): Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference transmitters when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.

5. Coverage Conditions: Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum signal level which must be provided by the reference transmitter and the neighbour.

250

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Handover Start: 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 transmitter (see Figure 6.128). Handover End: Enter the signal level which indicates the end of the handover margin. The handover end must exceed the value entered for the Handover Start (see Figure 6.128). The higher the value entered for the Handover End, the longer the list of candidate neighbours (see Figure 6.128). 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 desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability.

6. Click OK to save your modifications and close the Coverage Conditions dialogue. 7. Under Coverage Conditions, you can select whether Atoll defines the importance of neighbours by the size of the handover zone shared with the reference transmitter or by the amount of circuit traffic. Select one of the following options: Covered Area: If you select Covered Area, Atoll defines importance according to the size of the handover zone shared with the reference transmitter Covered Traffic: If you select Covered Traffic, Atoll defines importance according to the amount of circuit traffic (in Erlangs).

Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. Notes: You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

8. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. Transmitter: The name of the reference transmitter. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 4. Cause: The reason Atoll has allocated value in the Importance column. Co-site Adjacency Symmetry Coverage

Coverage: The amount of reference transmitters coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neighbour transmitter is best server or second best server. Distance: The distance in kilometres between the reference cell and the neighbour.

The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

6.2.11.8

Checking the Consistency of the Neighbour Plan

You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Intra-technology Neighbours tab. 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Which cells having the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Transmitters table. Lists > Max Number: Which cells having more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Transmitters table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

251

Atoll User Manual Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per transmitter for the plan audited. Empty Lists: x/X; x number of transmitters out of a total of X having no neighbours (or empty neighbours list) Syntax: |TRANSMITTER|

Full Lists (default max number = Y): x/X; x number of transmitters out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |TRANSMITTER| |NUMBER| |MAX NUMBER|

Lists > Max Number (default max number = Y): x/X; x number of transmitters out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax: Note: |TRANSMITTER| |NUMBER| |MAX NUMBER| If the field Maximum number of intra-technology neighbours in the Transmitters table is empty, the Full Lists check and the Lists > Max Number check use the Default Max. Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |TRANSMITTER| |NEIGHBOUR|

Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |TRANSMITTER| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |TRANSMITTER| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |TRANSMITTER| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |TRANSMITTER| |NEIGHBOUR| |DISTANCE|

6.2.11.9

Exporting Neighbours
The neighbour data of an Atoll document is stored in a series of tables. You can export the neighbour data to use it in another application or in another Atoll document. To export neighbour data: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours and then select the neighbour table containing the data you want to export from the context menu: Intra-Technology Neighbours: This table contains the data for the intra-technology neighbours in the current Atoll document. Inter-Technology Neighbours: This table contains the data for the inter-technology neighbours in the current Atoll document. Intra-technology Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document. Inter-technology Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs (forced and forbidden) in the current Atoll document.

4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files" on page 61.

252

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.3

Studying Network Capacity

In Atoll, you can study the network capacity of a GSM/GPRS/EDGE network in two major ways: You can either import OMC traffic data after re-scaling in order to transform it from served traffic into demanded traffic, Or you can import traffic demand information using traffic maps and transform this information into traffic demand by creating a traffic capture.

A traffic capture is based on a macroscopic description of traffic as defined by one or more traffic maps. In the 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 traffic can be treated as a traffic demand for each, or the traffic can be treated as a traffic demand for only one of the two, taking into consideration the maximum speed defined per layer (traffic with a mobility type with a high speed will not be allocated to a micro layer), frequency bands, etc.

The results 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 (Max 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 Condition tab for the traffic capture. Alternatively, the traffic demand, which is a prerequisite for dimensioning a GSM/GPRS/EDGE network can directly be imported in the Traffic data part of the subcells table. In this section, the following are explained: "Importing OMC traffic data into the subcell traffic view" on page 253 "Using Subcell Data in Network Capacity Analysis" on page 253 "Defining Multi-service Traffic Data" on page 254 "Creating a Traffic Map" on page 254 "Calculating and Displaying a Traffic Capture" on page 262 "Dimensioning a GSM/GPRS/EDGE Network" on page 266.

6.3.1

Importing OMC traffic data into the subcell traffic view

As explained in "Subcell Definition" on page 196, 3 levels of information can be displayed from the subcells table. The subcell traffic view is a display mode of the subcell table which permits to define the traffic demand per traffic zone. In most cases, there is only one traffic zone per transmitter. Nevertheless, in the case of concentric cells, there might be two traffic zones corresponding to the underlay / overlay zones. The traffic view of the subcells table displays the most important result of a traffic analysis: the load and the effective rate of traffic overflow. It also contains permits you to enter the following major inputs: The voice demand in number of Erlangs, The Packet switched demand in number of timeslots, The Half-rate traffic ratio, The target rate of overflow.

The table can be populated as any other table as explained in "Working with Data Tables" on page 53.

6.3.2

Using Subcell Data in Network Capacity Analysis

Dimensioning process and Quality Indicator Calculation can be either based of a traffic capture (referring to traffic maps) but can also use the information contained in the traffic view of the subcells table. The AFP may also extracts its traffic information from the subcell table. This traffic information may also be used for the neighbour evaluation and in interference studies. 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 chapters below. The traffic capture will analyse the radio conditions at each point, figuring out the coding schemes, modulation and bit rates, in order to find out how many timeslots are required for a demands of X Kbits. Note: It is very common to use traffic maps based on OMC data per transmitter in order to only get interference matrices based on traffic. The best mode to work with an AFP is to used 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 283.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

253

Atoll User Manual

6.3.3

Defining Multi-service Traffic Data

The first step in studying network capacity is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: 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. Packet-switched services can be distributed into two types : 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 GSM/GPRS/EDGE Services" on page 418. 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 "Creating or Modifying a GSM/GPRS/EDGE Mobility Type" on page 419. 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 "Creating or Modifying a GSM/GPRS/EDGE Terminal" on page 419.

6.3.4

Creating a Traffic Map

The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atoll provides three types of traffic maps for GSM/GPRS/EDGE projects. Sector traffic map User profile traffic map User density traffic map (number of users per km2)

These maps can be created using different types of traffic data sources as follows: Sector traffic maps can be used if you have live traffic data from the OMC (Operation and Maintenance Centre). The OMC (Operations and Maintenance Centre) collects data from all cells in a network. This includes, for example, throughput and Erlangs 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 Erlangs for circuit-switched services or constant bit rate packet-switched services and Kbps for maximum bit rate packetswitched services. For more information, see "Creating a Sector Traffic Map" on page 254. User profile traffic maps can be used if you have marketing-based traffic data. User profile traffic maps, where each vector (polygon, line, or point) describes subscriber densities (or numbers of subscribers for points) with user profiles and mobility types, and user profile environment based traffic maps, where each pixel has an assigned environment class. For more information, see "Importing a User Profile Traffic Map" on page 257, "Importing a User Profile Environment Based Traffic Map" on page 258, and "Creating a User Profile Environment Based Traffic Map" on page 259. User density traffic maps (number of users per km2) can be used if you have population-based traffic data, or 2G network statistics. Each pixel has a user density assigned. The value either includes all activity statuses, or it corresponds to a particular activity status. For more information, see "Importing a User Density Traffic Map" on page 260, "Creating a User Density Traffic Map" on page 260, "Converting 2G Network Traffic" on page 261 and "Exporting Cumulated Traffic" on page 261.

6.3.4.1

Creating a Sector Traffic Map

This section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demand or Erlangs. A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 227. To create a sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector Traffic Map. 5. Click the Create button. The Sector Traffic Map dialogue appears with a table for the amount of traffic (in Erlangs) for each circuit-switched service or constant bit rate packet-switched service (such as VoIP) and throughputs for each maximum bit rate packet-switched service by transmitter.

254

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Note:

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.

6. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 7. In the row marked with the New Row icon ( ), select the name of the transmitter from the TX_ID list.

8. For the transmitter in the TX_ID column, enter for each service in the appropriate column: For circuit services (voice), enter a value in Erlangs. For packet services (maximum bit rate), enter the minimum throughput in Kbps. For packet services (constant bit rate, such as VoIP), enter a value in Erlangs. Erlangs are internally transformed into Kbps by multiplying the value by the service-guaranteed bit rate per user. Note: You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 63.

9. Click OK. The Sector Traffic Map Properties dialogue appears. 10. Select the Traffic tab. Enter the following: a. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. b. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. c. Under Clutter Distribution, for each clutter class, enter a weight to spread the traffic over the clutter classes. 11. 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 the sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 5. Select the Traffic tab. 6. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 7. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 8. Under Clutter Distribution, for each clutter class, enter a weight to spread the traffic over the clutter classes. 9. Click OK. Atoll saves the traffic map with its modifed values. You can update the information, throughput demands and Erlangs, on the map afterwards. You can update traffic per sector maps 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. For more information, see "Making a Coverage Prediction by Transmitter" on page 227. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Update from the context menu. The Sector Traffic Map dialogue appears. 5. Select the updated coverage prediction by transmitter and define traffic values for the new transmitter(s) listed at the bottom of the table. Deleted or deactivated transmitters are automatically removed from the table. 6. Click OK. The Sector Traffic Map Properties dialogue appears. If desired you can update the values under Terminals (%), Mobilities (%), and Clutter Distribution. 7. Click OK. The traffic map is updated on the basis of the selected coverage prediction by transmitter. If you want to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic map, you can create user density traffic maps from sector traffic maps. For more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 261.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

255

Atoll User Manual

6.3.4.2

Creating a User Profile Traffic Map

The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There can also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments. A user profile models the behaviour of different subscriber categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for circuit-switched or constant bit rate packet-switched calls) or downlink volume (for max bit rate packet-switched calls). Environment classes are used to describe the distribution of subscribers on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km). The sections "Importing a User Profile Traffic Map" on page 257, "Importing a User Profile Environment Based Traffic Map" on page 258 and "Creating a User Profile Environment Based Traffic Map" on page 259 describe how to use traffic data from the marketing department in Atoll to model traffic. In this section, the following are explained: "Modelling User Profiles" on page 256 "Modelling Environments" on page 256.

Modelling User Profiles

You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user might be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create a user profile: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. Note: 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.

5. You can modify the following parameters: Service: Select a service from the list. For information on services, see "Modelling GSM/GPRS/EDGE Services" on page 418. Terminal: Select a terminal from the list. For information on terminals, see "Modelling GSM/GPRS/EDGE Terminals" on page 419. Calls/Hour: For circuit-switched services and packet-switched services (Constant Bit Rate), 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 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. Note: 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 and packet-switched services (Constant Bit Rate), enter the average duration of a call in seconds. For packet-switched services, this field is left blank. DL Volume: For packet-switched services (Max Bit Rate), enter the average downlink volume per session in kilobytes.

Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you can assign a weight to each clutter class for each environment class.

256

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To create or modify a GSM/GPRS/EDGE environment: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

3. Right-click the Environments folder. The context menu appears. 4. Select New from the context menu. The Environments New Element Properties dialogue appears. Note: You can modify the properties of an existing environment by right-clicking the environment in the Environments folder and selecting Properties from the context menu.

5. Click the General tab. 6. Enter a Name for the new GSM/GPRS/EDGE environment. 7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility combination that this GSM/GPRS/EDGE environment will describe: User: Select a user profile. Mobility: Select a mobility type. Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination of user profile and mobility type.

8. Click the Clutter Weighting tab. 9. For each clutter class, enter a weight that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

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.

6.3.4.2.1

Importing a User Profile Traffic Map

User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscriberskm, or polygons with a number of subscriberskm) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Densities from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 259.

7. Select the file to import. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps Properties dialogue appears. 11. Select the Traffic tab (see Figure 6.131). Under Traffic Fields, you can specify the user profiles to be considered, their mobility type (kmh), and their density. If the file you are importing has this data, you can define the traffic

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

257

Atoll User Manual characteristics by identifying the corresponding fields in the file. If the file you are importing does not have data describing the user profile, mobility, or density, you can assign values. When you assign values, they apply to the entire map.

Figure 6.131: Traffic map Properties dialogue - Traffic tab Define each of the following: User Profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the GSM/GPRS/ EDGE Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the GSM/GPRS/EDGE Parameters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points. Important: 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 GSM/GPRS/EDGE Parameters folder of the Data tab. If the imported user profile or mobility does not match, Atoll will display a warning. 12. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

13. Click OK to finish importing the traffic map.

6.3.4.2.2

Importing a User Profile Environment Based Traffic Map

Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears.

258

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 259.

7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, JPEG 2000, BIL, IST, BMP, PlaNET, GRC Vertical Mapper, or Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps Properties dialogue appears. 11. Select the Description tab. In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the Code column. 12. For each Code, select the environment it corresponds to from the Name column. The environments available are those available in the Environments folder, under GSM/GPRS/EDGE Parameters on the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 256. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 32.

6.3.4.2.3

Creating a User Profile Environment Based Traffic Map

Atollenables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 6.132).

Draw Map

Delete Map

Figure 6.132: Environment Map Editor toolbar 7. Select the environment class from the list of available environment classes. 8. Click the Draw Polygon button ( 9. Click the Delete Polygon button ( ) to draw the polygon on the map for the selected environment class. ) and click the polygon to delete the environment class polygon on the map.

10. Click the Close button to close the Environment Map Editor toolbar and end editing.

6.3.4.2.4

Displaying Statistics on a User Profile Environment Traffic Map

You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface area) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

259

Atoll User Manual The Statistics window lists the surface (Si in km) and the percentage of surface (% of i) for each environment Si class "i" within the focus zone. The percentage of surface is given by: % of i = ------------- 100 Sk

You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.

6.3.4.3

Creating User Density Traffic Maps (No. Users/km2)

User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or based on 2G traffic statistics. User density traffic maps provide the number of connected users per unit of surface, i.e., the density of users, as input. In this section, the following ways of creating a user density traffic map are explained: "Importing a User Density Traffic Map" on page 260 "Creating a User Density Traffic Map" on page 260.

User density traffic maps may be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. for more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 261.

6.3.4.3.1

Importing a User Density Traffic Map

The user density traffic map defines the density of users per pixel. For a traffic density of X users per km, Atoll will consider x users per pixel during traffic analyses, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined on the Traffic tab of the traffic maps properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (No. Users/km2). 5. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 259.

6. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP, PlaNET, TIF, JPEG 2000, ISTAR, and Erdas Imagine. 7. Click Open. The File Import dialogue appears. 8. Select Traffic from the Data Type list. 9. Click Import. Atoll imports the traffic map. The traffic maps Properties dialogue appears. 10. Select the Traffic tab. 11. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 12. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 13. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal 100. 14. Click OK. Atoll creates the traffic map in the Traffic folder.

6.3.4.3.2

Creating a User Density Traffic Map

Atoll enables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears.

260

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 4. Select User Density Traffic Map (Number of users per km2). 5. Click the Create button. The traffic maps properties dialogue appears. 6. Select the Traffic tab. 7. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 8. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 9. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal 100. 10. Click OK. Atoll creates the traffic map in the Traffic folder. 11. Right-click the traffic map. The context menu appears. 12. Select Edit from the context menu. 13. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit contours, see "Editing Polygons, Lines, and Points" on page 46. Atoll creates an item called Density values in the User Density Map folder. 14. Right-click the traffic map in the Traffic folder. The context menu appears. 15. Select Open Table from the context menu. 16. In the table, enter a traffic density value (i.e., the number of users per km2) for each contour you have drawn. 17. Right-click the traffic map in the Traffic folder. The context menu appears. 18. Select Edit from the context menu to end editing.

6.3.4.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. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map from which you want to create user density traffic maps. The context menu appears. 4. Select Create density maps from the context menu. Atoll creates as many user density traffic maps as the number of services present in the sector traffic map. The user density map files use the resolution of the coverage prediction used for the sector traffic map and are embedded in the document.

6.3.4.4

Converting 2G Network Traffic

Atoll can cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as traffic maps per user density into your GSM/ GPRS/EDGE document. These maps can then be used in traffic captures like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 261, and for information on importing traffic maps per user density, see "Importing a User Density Traffic Map" on page 260. To import a 2G traffic map into a GSM/GPRS/EDGE document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating live data traffic maps, see "Creating a Sector Traffic Map" on page 254. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 261. 3. Import the traffic exported in step 2 to your GSM/GPRS/EDGE document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 260.

6.3.4.5

Exporting Cumulated Traffic

Atoll allows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user density. The cumulated traffic is exported in 32-bit BIL, ArcView Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

261

Atoll User Manual map can then be imported as a user density traffic map and used for traffic analysis. For more information on traffic analysis, see "Calculating and Displaying a Traffic Capture" on page 262. To export the cumulated traffic: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: The Entire Project Area: This option allows you to export the cumulated traffic over the entire project. The Computation Zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible.

7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains at "0" and no data will be exported. 8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic data to be exported. Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal. Service: Select the service that will be exported, select "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.

9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the cumulated traffic. 10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.

6.3.5

Exporting a Traffic Map

To export a traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save. If you are exporting a raster traffic map, you have to define: The Export Region: Entire Project Area: Saves the entire traffic map. Only Pending Changes: Saves only the modifications made to the map. Computation Zone: Saves only the part of the traffic map inside the computation zone.

An export Resolution.

6.3.6

Calculating and Displaying a Traffic Capture

In Atoll, you can create a traffic capture from an existing traffic map to analyse traffic at the transmitter level. When you calculate a traffic capture, the traffic from the selected maps is distributed to all transmitters according to the criteria defined for each transmitter, as well as the GSM/GPRS/EDGE parameters: services, mobility types, terminals, and user profiles. For example, an GPRS/EDGE-enabled transmitter will be allocated the data user traffic whereas a transmitter not capable of GPRS/EDGE will only carry GSM voice traffic. Similarly, a user using a GSM900-band mobile phone will not be allocated to a transmitter that only functions on the DCS1800 band. By creating different traffic captures using different criteria to represent different conditions, you can analyse network traffic under the various situations. One of the traffic captures is the default traffic capture and can be used: to dimension a GSM/GPRS/EDGE network to calculate KPI to calculate interference matrices to allocate neighbours according to overlapping traffic.

262

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Alternatively to a default traffic capture, the actual traffic of a real network can directly be imported in the Traffic data part of the subcells table (See "Dimensioning a GSM/GPRS/EDGE Network" on page 266 for more information). In this section, the following are explained: "Prerequisites for a Traffic Capture" on page 263 "Creating a Traffic Capture" on page 263 "GSM/GPRS/EDGE Traffic Capture Results" on page 264 "Estimating a Traffic Increase" on page 265 "Modifying a GSM/GPRS/EDGE Traffic Capture" on page 265.

6.3.6.1

Prerequisites for a Traffic Capture

To successfully create a traffic capture, you must ensure that you have the following information: A valid traffic map (see "Creating a Traffic Map" on page 254) Correct GPRS-related parameters (see "Creating or Modifying a Base Station Element" on page 201), including: GPRS/EDGE capacity selected GPRS/EDGE-capable configuration selected Correct packet traffic-related parameters

Target rate for traffic overflow defined for subcells (see "Subcell Definition" on page 196) Correctly defined service zones (see "Creating a Traffic Capture" on page 263) Correctly defined HCS layers (see "Setting HCS Layers" on page 400).

6.3.6.2

Creating a Traffic Capture

To create a traffic capture: 1. Click the Data tab of the Explorer window. 2. Right-click the Traffic Analysis folder. The context menu appears. 3. Select New from the context menu. A traffic capture Properties dialogue appears. 4. Click the General tab. You can change the following: Name: By default, Atoll names traffic captures sequentially. You can change the assigned name. Comments: You can enter comments in this field if you wish. Filter: You can select the transmitters to be considered in the traffic capture by clicking the Filter button. For information on using the Filter dialogue, see "Advanced Data Filtering" on page 75.

5. Click the Source Traffic tab. You can enter the following: Global Scaling Factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). For information on using the global scaling factor, see "Estimating a Traffic Increase" on page 265. 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 Definition" on page 196 and in Figure 6.103 on page 199. 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 "Creating a Traffic Map" on page 254. 6. Click the Condition tab. The parameters on the Condition 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 400). Enter a hand-over margin in the With a Margin text box. 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. You can select the Indoor Coverage check box to add indoor losses.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

263

Atoll User Manual

Note:

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, 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. You can even select interference coming from an external project using another technology. For more information, see "Modelling Inter-Technology Interference" on page 662. If you want Atoll to take interference due to intra-technology third order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422. 11. 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 user-defined or as calculated during dimensioning.

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. After the traffic capture has been completed, two new tabs appear on the traffic capture Properties dialogue with the results. For a detailed explanation of the results, see "GSM/GPRS/EDGE Traffic Capture Results" on page 264.

6.3.6.3

GSM/GPRS/EDGE Traffic Capture Results

After you have calculated a GSM/GPRS/EDGE traffic capture, as described in "Creating a Traffic Capture" on page 263, two new tabs, Results per Transmitter and Results per Subcell, appear on the traffic capture Properties dialogue: 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 half-rate 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 circuitswitched 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.

264

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Tip: 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 254) based on a best server coverage prediction (HCS server option with 0 dB HO 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 HO margin) where the traffic of each map is assigned to its respective layer (see "Creating a Traffic Capture" on page 263). 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 servcies cannot be treated in that way since their input traffic is stated in Erlangs whereas the corresponding demand is evaluated in Kbps as any other packet-switched service. For more information on how the results are calculated and on the formulas used, see the Technical Reference Guide.

6.3.6.4

Estimating a Traffic Increase

When you create a traffic capture, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increased traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a traffic capture by: Creating a new traffic capture as explained in "Creating a Traffic Capture" on page 263. Modify an existing traffic capture by right-clicking a traffic capture in the Traffic Analysis folder of the Data tab of the Explorer window and selecting Properties from the context menu.

2. Click the Source Traffic tab of the Properties dialogue. 3. Enter a Global Scaling Factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).

6.3.6.5

Modifying a GSM/GPRS/EDGE Traffic Capture

Atoll offers several options to modify a traffic capture once you have created it as explained in "Creating a Traffic Capture" on page 263. As well, you can use a traffic capture for one of several calculations. You can access these options using the traffic captures context menu: To access the options for a traffic capture: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic Analysis folder.

3. Right-click the traffic capture. The context menu appears. 4. Select one of the following from the context menu: Properties: Select Properties to open the traffic captures Properties dialogue. 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 264. For information on the parameters available, see "Creating a Traffic Capture" on page 263. Default: Select Default to set the current traffic capture as the default traffic capture. The default traffic capture ( ) is the one used to: to dimension a GSM/GPRS/EDGE network (see "Dimensioning a GSM/GPRS/EDGE Network" on page 266) - to calculate KPIs (see "Calculating Key Performance Indicators of a GSM/GPRS/EDGE Network" on page 344) - to calculate interference matrices (see "Interference Matrices" on page 280) - to allocate neighbours according to overlapping traffic (see "Allocating Neighbours Automatically" on page 243) Calculate: Select Calculate to calculate a new traffic capture (i.e., one that you created but closed without calculating) or to recalculate an existing traffic capture to which you have made changes. Delete: Select Delete to delete the current traffic capture. Caution: The traffic capture is deleted immediately; there is no opportunity to confirm or cancel the action.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

265

Atoll User Manual Rename: Select Rename to rename the current traffic capture.

6.3.7

Dimensioning a GSM/GPRS/EDGE Network

The dimensioning process allows you to calculate the number of TRXs required to meet the traffic needs of a GSM/GPRS/ EDGE network. Dimensioning is carried out : either on the default traffic capture based on one or more traffic maps or on the actual traffic data present in the subcells table,

and using the parameters defined in the selected dimensioning model. 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: "Defining a GSM/GPRS/EDGE Dimensioning Model" on page 266 "Dimensioning a GSM/GPRS/EDGE Network" on page 267.

6.3.7.1

Defining a GSM/GPRS/EDGE Dimensioning Model

The dimensioning model is the definition of the parameters that will be used during the dimensioning process. You can modify an existing dimensioning model or you can create a new dimensioning model. To create or modify a dimensioning model: 1. If you are creating a new dimensioning model: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

c. Right-click the Dimensioning Models folder. The context menu appears. d. Select New from the context menu. The Dimensioning Models New Element Properties dialogue appears (see Figure 6.98 on page 193). 2. If you are modifying the properties of an existing dimensioning model: a. Click the Data tab in the Explorer window. b. Click the Expand button ( c. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder. ) to expand the Dimensioning Models folder.

d. Right-click the dimensioning model you want to modify. The context menu appears. e. Select Properties from the context menu. The Properties dialogue 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 dialogue (see "Subcell Definition" on page 196).

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 packet-switched 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 dialogue. 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.

266

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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. Note: 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. Note: 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. You can modify or replace the quality graphs with graphs generating using a third-party simulator. Caution: If the quality graphs are modified incorrectly, the dimensioning and quality analysis results that are based on the quality graphs will also be incorrect.

Notes 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.

6.3.7.2

Dimensioning a GSM/GPRS/EDGE Network

You can dimension a GSM/GPRS/EDGE network once you have the necessary information: Either a default traffic capture (for information on creating a traffic capture, see "Calculating and Displaying a Traffic Capture" on page 262) or alternatively a populated traffic data part of the subcells table (see "Subcell Definition" on page 196). Note: 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 266).

To dimension a GSM/GPRS/EDGE network: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Traffic > Dimensioning from the context menu. The Dimensioning/KPIs dialogue appears (see Figure 6.133).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

267

Atoll User Manual

Figure 6.133: The Dimensioning dialogue: The Dimensioning/KPI dialogue 4. Under Dimensioning Parameters, select the dimensioning model from the Model list. 5. Under Traffic (Circuit and Packet Demand), select if the dimensioning has to be based on the traffic demand computed in the default traffic capture of from the actual values (circuit and packet demands) in the subcells table. If you have selected "From subcell table", you will have to 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 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 Services (%), enter the percentage of each service used in the map. For each type of service (circuit or packet switched, assuming packet is made of max bit rate and constant bit rate packet services), the percentages must equal 100.

6. Click Calculate to dimension the network. The output of the dimensioning appears in the Dimensioning dialogue, under Results. Some columns are hidden by default. You can select which columns to display by clicking the Displayed Columns button and selecting or clearing the check box of the columns. The following results are given for each transmitter in the Transmitter column: 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 packet-switched 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

268

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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 user selection for the traffic demand source. 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 circuit-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 user selection for the traffic demand source. It is assigned to subcell pools when committing the results of dimensioning. 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 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 (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 user-defined depending on the traffic demand source 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

269

Atoll User Manual

6.4

Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs

The allocation of resources is an important part of planning and optimising a GSM network. The resources in question are frequencies, BSICs, the HSNs, and the MAIOs. The allocation of resources can be done manually, automatically or interactively. In this section, the allocation process is defined first, followed by an explanation of the various elements of allocating resources. By beginning with the manual allocation process, where each element can be dealt with individually, the more complex automatic allocation process is easier to understand. When the manual allocation process is too time-consuming or when there are too many variables to co-ordinate, you probably need to use Automatic Frequency Planning (AFP) . The AFP can perform an enhanced optimisation of your 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 permits interactive allocation 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 letting you select 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. For more information on the optional Atoll AFP module, see "The Atoll AFP Module" on page 425. In this section, the following are explained: "Definition of the Resource Allocation Process" on page 270 "Defining Resource Ranges" on page 271 "Allocating Frequencies and BSICs Manually" on page 274 "AFP Prerequisites (IM, Separations, Traffic, etc.)" on page 279 "Automatic Resource Allocation Using an AFP Module" on page 299.

6.4.1

Definition of the Resource Allocation Process

The main resources that must be allocated are similar in certain ways. For example, there is only a limited amount of each resource to be allocated, consequently each resource will have to be used more than once, but each instance of that resource can not be used close to an identical instance of the same instance. The resources differ, however, on the following points: 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 BSIC is allocated at the cell level and the BSIC-BCCH pair is used to identify the transmitters in the network.

In Atoll's GSM/GPRS/EDGE module, frequencies are managed on three different levels: frequency bands, domains, and groups. BSICs and HSNs, on the other hand, are managed on two different levels: domains and groups. For frequencies, the highest level is the frequency band. The frequency band 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. 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. 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. 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.

270

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.4.2

Defining Resource Ranges

In Atoll, when you allocate resources such as frequencies and BSICs, you do so using domains and groups. The domains and groups define the range of resources that can be used by the transmitter, subcell, or TRX. Using defined ranges of resources facilitates both allocation and management of resources. In this section, the following are explained: "Defining Frequency Bands, Domains, and Groups" on page 271 "Defining BSIC Domains and Groups" on page 272 "Defining HSN Domains and Groups" on page 273

6.4.2.1

Defining Frequency Bands, Domains, and Groups

In GSM/GPRS/EDGE projects, you can manage frequencies by defining frequency domains and groups based on standard frequency bands. A frequency domain consists of one or several frequency groups. The frequency domain in turn belongs to a frequency band. A frequency group is a set of channels. A frequency group can belong to one or several frequency domains. Frequency planning, both manual and automatic, is based on the frequency domains assigned to the TRX types in defined cell types. In this section, the following are explained: "Defining Frequency Bands" on page 271 "Defining Frequency Domains and Groups" on page 271.

6.4.2.1.1

Defining Frequency Bands

Frequency bands represent the defined frequency that frequency domains and groups refer to. In a GSM/GPRS/EDGE project, the frequency bands are usually fixed items, whereas domains and groups can be defined and modified to respond to the needs of the project. The properties of frequency bands can be accessed from the Frequency Bands table. To define a frequency band: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Bands. The Frequency Bands table appears. 4. In the row marked with the New Row icon ( ), enter the following parameters to define a frequency band (for information on working with data tables, see "Working with Data Tables" on page 53): Name: Enter a name for the frequency, for example, "GSM 1900." This name will appear in other dialogues 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. Note: You can also modify the properties of a frequency band using its Properties dialogue. You can open the frequency band Properties dialogue by selecting the frequency band in the Frequency Bands table and clicking the Properties button. The frequency band Properties dialogue 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 user-defined 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

6.4.2.1.2

Defining Frequency Domains and Groups

In a GSM/GPRS/EDGE project, the frequency bands are usually fixed items, whereas domains and groups can be defined and modified to respond to the needs of the project. Frequency domains are linked to TRX types. Frequency groups are used in frequency allocation.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

271

Atoll User Manual To define frequency domains and groups: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Domains. The Frequency Domains table appears. 4. In the row marked with the New Row icon ( ), enter the following parameters to define a frequency domain (for information on working with data tables, see "Working with Data Tables" on page 53): Name: Enter a name for the frequency domain, for example, "GSM 1900 domain." This name will appear in other dialogues when you select a frequency domain. Frequency Band: Select the frequency band the domain will belong to from the list.

5. Select the row containing the frequency domain and click the Properties button. The frequency domains Properties dialogue appears. In the frequency domains Properties dialogue, you can modify the properties of the frequency domain and create frequency groups. 6. 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 "Working with Data Tables" on page 53): Name: Enter a name for the frequency group, for example, "GSM 1900 domain Group1." This name will appear in other dialogues 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.

7. Click OK to close the frequency domains Properties dialogue. 8. Click Close to close the Frequency Domains table. Notes: You can associate frequency groups to frequency domains using the Frequency Groups table. You can open the Frequency Groups table by right-clicking the Transmitters folder and selecting Network Settings > Frequencies > Groups from the context menu. Although each group name in a single frequency domain must be unique, you can use the same group name in different frequency domains.

6.4.2.2

Defining BSIC Domains and Groups

In GSM/GPRS/EDGE, the Base Station Identity Code (BSIC) is assigned to a BCCH to identify the transmitter on which the BCCH is located. BSICs are made available according to country and area. The mobile uses the BSIC, which can be in either decimal or octal format, to distinguish one BCCH from BCCHs on nearby transmitters. The BSIC is composed of a Network Colour Code (NCC) and a BTS Colour Code (BCC). BSICs are modelled using domains and groups which can be defined and modified: A domain consists of one or more groups. A group is a defined set of BSICs. A BSIC group can belong to one or more BSIC domains.

In this section, the following are explained: "Defining the BSIC Format" on page 272 "Defining BSIC Domains and Groups" on page 273.

6.4.2.2.1

Defining the BSIC Format

The BSIC is composed of a Network Colour Code (NCC) combined with a BTS Colour Code (BCC). Both the NCC and the BCC are integers from 0 to 7, making a total of 64 possible BSICs. They are broken down into 8 groups (one group for each possible NCC) of 8 BSICs. For each NCC-BCC pair, the resulting BSIC number can be in either decimal or octal format. 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.

272

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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. Important: 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. To define the BSIC format for a GSM/GPRS/EDGE document: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > BSICs > Format and select one of the following: Decimal Octal

6.4.2.2.2

Defining BSIC Domains and Groups

BSICs are modelled using domains and groups which can be defined and modified. A domain consists of one or more groups. You must assign a BSIC domain to each transmitter. A group is a defined set of BSICs. A BSIC group can belong to one or more BSIC domains. Groups are used during automatic BSIC allocation. To define frequency domains and groups: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > BSICs > Domains. The BSIC Domains table appears. The BSIC Domains table contains a default domain called "ALL BSICs;" it contains all 64 BSICs divided into 8 groups. 4. In the row marked with the New Row icon ( ), enter the name of the new BSIC domain.

5. Select the row containing the BSIC domain and click the Properties button. The BSIC domains Properties dialogue appears. In the BSIC domains Properties dialogue, you can modify the properties of the BSIC domain and create BSIC groups. 6. 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 "Working with Data Tables" on page 53): Important: When defining the BSIC group, ensure that the entered values are consistent with the defined BSIC format (see "Defining the BSIC Format" on page 272). Name: Enter a name for the BSIC group. This name will appear in other dialogues 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.

7. Click OK to close the BSIC domains Properties dialogue. 8. Click Close to close the BSIC Domains table. Note: You can associate frequency groups to frequency domains using the BSIC Groups table. You can open the BSIC Groups table by right-clicking the Transmitters folder and selecting Network Settings > BSICs > Groups from the context menu.

6.4.2.3

Defining HSN Domains and Groups

In Atoll, both base band hopping (BBH) and synthesised frequency hopping (SFH) are supported in GSM/GPRS/EDGE projects. BBH and SFH are modelled using the hopping sequence number (HSN) along with other parameters such as the MAL and the MAIOs.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

273

Atoll User Manual The HSN describes the frequency hopping sequence. It can have one of 64 different values (from 0 to 63). Frequency sequences are pseudo-random, except for HSN "0," where frequencies are used one after the other (cyclic hopping). In Atoll, HSNs are modelled in the form of HSN domains and groups: A domain consists of one or more HSN groups. A group is a defined set of HSNs. A HSN group can belong to one or more HSN domains.

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. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > HSNs > Domains. The HSN Domains table appears. The HSN Domains table contains a default domain called "ALL HSNs;" it contains all 64 HSNs. 4. In the row marked with the New Row icon ( ), enter the name of the new HSN domain.

5. Select the row containing the HSN domain and click the Properties button. The HSN domains Properties dialogue appears. In the HSN domains Properties dialogue, you can modify the properties of the HSN domain and create HSN groups. 6. 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 "Working with Data Tables" on page 53): Name: Enter a name for the HSN group. This name will appear in other dialogues when you select a HSN group. Min.: Enter the first HSN in this HSN group. Max.: Enter the last HSN in this HSN group. Step: Enter the value interval between HSNs in this HSN group. Excluded: Enter the HSNs that you do not want to use in this HSN group. You can enter or paste a list of HSNs; the values must be separated with either a comma, or a semi-colon, or a space. You can also enter a range of HSNs to be excluded from this group, by entering the first and last HSN 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 HSNs, outside the first and last HSNs of the group, that you want to use in this HSN group. You can enter or paste a list of HSNs; the values must be separated with either a comma, or a semicolon, or a space. You can also enter a range of HSNs to be excluded from this group, by entering the first and last HSN of the range separated by a hyphen. For example, entering 0-5 corresponds to entering 0 1 2 3 4 5.

7. Click OK to close the HSN domains Properties dialogue. 8. Click Close to close the HSN Domains table. Note: You can associate frequency groups to frequency domains using the HSN Groups table. You can open the HSN Groups table by right-clicking the Transmitters folder and selecting Network Settings > HSNs > Groups from the context menu.

6.4.3

Allocating Frequencies and BSICs Manually

Normally, when you allocate frequencies and BSICs for an entire project, you will allocate them automatically. However, Atoll enables you to allocate frequencies and BSICs manually, for example, when you add new base stations or when you modify frequencies or BSICs that have already been allocated. When you allocate frequencies or BSICs, you first define a range of frequencies or BSICs for the transmitter. You will then assign frequencies or BSICs that respect the defined range. In Atoll, ranges of frequencies and BSICs are modelled using domains and groups. For information on creating or modifying frequency or BSIC domains and groups, see "Defining Resource Ranges" on page 271. In this section, setting a range of frequencies or BSICs is explained, as well as manually assigning frequencies or BSICs from the defined range: "Assigning BSIC Domains to Transmitters" on page 274 "Assigning BSICs to Transmitters Manually" on page 275 "Defining Frequency Domains for Transmitters" on page 275 "Assigning Frequencies to Subcells" on page 276.

6.4.3.1

Assigning BSIC Domains to Transmitters

Before you assign a BSIC to a transmitter, you define the range of possible BSICs for that transmitter by assigning a BSIC domain. For information on creating or modifying BSIC domains and groups, see "Defining BSIC Domains and Groups" on page 273.

274

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To assign a BSIC domain to a transmitter: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign a BSIC domain. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter in the map window and selecting Properties from the context menu.

5. Select the TRXs tab. 6. Under Identification, select the BSIC Domain from the list. You can click the Browse button ( properties of the selected BSIC domain. 7. Click OK. ) to access the

6.4.3.2

Assigning BSICs to Transmitters Manually

Normally, you will allocate Base Station Identity Codes (BSICs) automatically for an entire project. However, you can allocate BSICs manually, for example, when you add new base stations or when you modify BSICs that have already been allocated. The BSIC is composed of the Network Colour Code (NCC) and the BTS Colour Code (BCC). Both the NCC and BCC must be whole numbers from 0 to 7. The combination of the BSIC and BCCH (in other words, the frequency of the BCCH) permit to precisely identify a transmitter. Over greater distances, a BSIC-BCCH pair can be repeated. To allocate a BSIC to a transmitter manually: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign a BSIC. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter in the map window and selecting Properties from the context menu.

5. Select the TRXs tab. 6. Under Identification, select the BSIC from the list. The BSICs available in the list will be those available in the defined BSIC domain. Note: You can enter a value in the BSIC field, however, it must be a BSIC that is part of the selected BSIC Domain and in the correct BSIC format (for information on the BSIC format, see "Defining the BSIC Format" on page 272). As well, you can enter a BSIC in the format of a NCC-BCC. When you click OK or Apply, Atoll will convert it into the single-digit BSIC format.

Once you have selected the BSIC, the NCC-BCC is displayed. 7. Click OK.

6.4.3.3

Defining Frequency Domains for Transmitters

Before you assign a frequency to a transmitter, you define the range of possible frequencies for that transmitter by assigning a frequency domain to the transmitters subcells. In Atoll, you define the range of frequencies that can be assigned to a transmitter by assigning frequency domains to the transmitters subcells. By default, a transmitters subcells, based on the selected cell type (for information, see "Applying a New Cell Type" on page 202), already have an assigned frequency domain. However, you can change a subcells frequency domain. If you select a different cell type after having modified any of the parameters of a subcell, Atoll offers you the choice of keeping current parameters or resetting them to those found in the cell type. For information on creating or modifying frequency domains and groups, see "Defining Frequency Domains and Groups" on page 271. To change the frequency domain assigned to a transmitter: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

275

Atoll User Manual 3. Right-click the transmitter to which you want to assign a frequency domain. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter in the map window and selecting Properties from the context menu.

5. Select the TRXs tab. 6. Under Subcells, select "Standard" from the Display list. The standard table lists each TRX group defined in the cell type selected under Cell Type on the TRXs tab. 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. Note: 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. Note: 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 69) 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 "Working with Data Tables" on page 53.

6.4.3.4

Assigning Frequencies to Subcells

In a GSM/GPRS/EDGE project, frequencies are modelled using channels. The channels are assigned to the TRXs of each subcell. If your Atoll document represents an existing network, frequencies might already have been assigned to many of the transmitters. You can then import the existing frequency list into your current Atoll document. You can also export the frequency list from the current Atoll document. In this section, the following are explained: "Importing a Frequency List" on page 276 "Adding New TRXs to a Document" on page 277 "Displaying the Frequency Plan" on page 277 "Exporting the Frequency List" on page 277.

6.4.3.4.1

Importing a Frequency List

If your Atoll document represents an existing GSM/GPRS/EDGE network, frequencies can already have been assigned to many of the transmitters. You can import the existing frequency list into your current Atoll document. You can then complete the data for new TRXs either manually or using the AFP. The frequency list you import must be a TXT or CSV file and the data must be arranged in a manner compatible with Atoll. The imported file must contain the transmitter name and the TRX type to identify the TRX to which the frequencies will be assigned. When you import a frequency list for a network with non-hopping or base-band hopping only, you only need to import the channels and the TRX types. If the network has synthesized frequency hopping, even if not all subcells use synthesized frequency hopping, you will also have to import the MAIO, the HSN, and the synchronisation. When Atoll imports the data, it will add TRXs that do not yet exist in the Atoll document to existing transmitters. If some sites and transmitters do not yet exist in the Atoll document, you must create them before you import the frequency list. For information on creating sites and transmitters, see "Creating a GSM/GPRS/EDGE Base Station" on page 192. To import an existing frequency list: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > TRXs Table from the context menu. The TRXs table appears. 4. Import the file as explained in "Importing Tables from Text Files" on page 63. The file imported must contain, at a minimum, the transmitter name and TRX type to identify the TRX to which the frequencies will be assigned, and the channels, identifying the frequencies. In the case of SFH, the channels will constitute the MAL. Additionally, if the hopping mode is SFH, the file imported must also contain the MAIO. If the hopping mode is BBH or SFH, continue with step 5. 5. Right-click the Transmitters folder. The context menu appears. 6. Select Subcells > Subcells Table: Standard Data from the context menu. The Subcells table appears.

276

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 7. Import the file as explained in "Importing Tables from Text Files" on page 63. The file imported must contain, at a minimum, the transmitter name and TRX type to identify the TRX. When the hopping mode is BBH or SFH, file must also contain the synchronisation and the HSN. Note: 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 dialogue. For information, see "Subcell Definition" on page 196.

6.4.3.4.2

Adding New TRXs to a Document

You can add TRXs to existing transmitters either by using the TRXs tab of the transmitter Properties dialogue, or by using the TRXs table. If you are adding TRXs to a single transmitter, it is easier to use the transmitter Properties dialogue. To add TRXs using the TRXs tab of the transmitter Properties dialogue: 1. In the map window, select the transmitter to which you want to add a TRX. Note: You can also select the transmitter in the Transmitters folder on the Data tab of the Explorer window.

2. Right-click the transmitter. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the TRXs tab. 5. Under TRXs, in the row marked with the New Row icon ( on page 200. 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. Click the Data tab of the Explorer window. 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 ( ). ), enter the parameters described in "TRX Definition"

5. In the Transmitter column, select the transmitter to which the TRXs will be added. 6. Enter the parameters described in "TRX Definition" on page 200.

6.4.3.4.3

Displaying the Frequency Plan

You can display or modify the network frequency plan, that is the channels allocated to each TRX, by opening the TRXs table. To open the TRXs table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > TRXs Table from the context menu. The TRXs table appears. If you wish, you can export the frequency plan. For information on exporting the frequency plan, see "Exporting the Frequency List" on page 277.

6.4.3.4.4

Exporting the Frequency List

You can export the network frequency list, that is the channels allocated to each TRX, using the TRXs table. The exported file must contain the transmitter name and the TRX type to identify the TRX to which the frequencies are assigned. To export an existing frequency list: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > TRXs from the context menu. The TRXs table appears. 4. Export the file as explained in "Exporting Tables to Text Files" on page 61. If the hopping mode is BBH or SFH, continue with step 5. 5. Right-click the Transmitters folder. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

277

Atoll User Manual 6. Select Subcells > Subcells Table: Standard Data from the context menu. The Subcells table appears. 7. Export the file as explained in "Exporting Tables to Text Files" on page 61. The file exported must contain, at a minimum, the transmitter name and TRX type to identify the TRX to which the frequencies are assigned, the HSN and the synchronisation.

6.4.3.4.5

Assigning Frequencies Manually Using the Map

Using Atoll, you can allocate frequencies manually, visualising the results directly on the map. When allocating frequencies using this method, you must ensure that neighbours have already been allocated. For information on allocating neighbours, see "Planning Neighbours" on page 241. To allocate frequencies manually using the map: 1. Create and display a coverage prediction by transmitter based on the best signal level and set the display to discrete values by transmitter. For more information, see "Making a Coverage Prediction by Transmitter Based on the Best Signal Level" on page 227. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

3. Select Neighbours from the context menu. Note: If you display the coverage areas of the neighbours, you can see not only the neighbours on the map but their coverage as well. This will enable you to see more clearly where frequencies used by the neighbours could cause interference. You can display the coverage areas of neighbours by clicking the arrow ( ) next to the Visual Management button and selecting Display Options from the menu. In the Neighbourhood Display dialogue that appears, you can select the Display Coverage Areas option. 4. Select View > Search Tool. The Search Tool appears. 5. On the Channel tab, enter a channel that you would like to allocate to the selected transmitter and click the Search button. The map window displays the coverage areas with the selected channel along with coverage areas using adjacent channels. 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.

Figure 6.134: Scanning for frequencies

278

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks On the other hand, channel 14 would be a good choice and could be allocated. Neither channel 14 nor either of the adjacent channels (13 and 15) are allocated to neighbours of the selected transmitter.

Figure 6.135: Scanning for frequencies

6.4.4

AFP Prerequisites (IM, Separations, Traffic, etc.)

In Atoll, you can use an Automatic Frequency Planning (AFP) module to allocate frequencies and BSICs, as well, as the MAL, MAIO, and HSN. The Automatic Frequency Planning (AFP) module assigns frequencies according to traffic demand (as indicated by the number of required TRXs) and respecting quality requirements with the aim of reducing interference. Atoll allows the use of an optional Atoll AFP module as well as the use of third-party AFP tools. The AFP attempts to allocate resources in an optimal fashion, i.e., it attempts to allocate resources in a way that minimises interference and complies with a set of user-defined constraints. The two main types of constraints are separation constraints and interference. The AFP assigns a cost to each constraint and then uses a cost-based algorithm to evaluate possible frequency plans and find the frequency plan with the lowest costs. Although you can run the AFP without an interference matrix, allocation will be calculated without taking interference into consideration, i.e., without considering one of the two important constraints. When you assign frequencies manually, you do not need an interference matrix, or traffic or separation rules. When you assign frequencies manually, you will be using your knowledge of the network, so manual allocation is more straightforward. On the other hand, when you assign frequencies automatically (or interactively) you need to supply the additional information to the AFP.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

279

Atoll User Manual

Figure 6.136: Input data for the AFP In this section, the AFP input elements are explained. Additionally, for each element, how to find the necessary information is explained, with both a quick method and a longer process designed to give more accurate information. The AFP is very sensitive to the quality of the input; therefore it is very important to understand and properly prepare the input before running the AFP. The most important aspect of using the AFP is choosing the level of complexity that corresponds to the desired accuracy of the results. The following AFP input elements are explained in this section: "Interference Matrices" on page 280 "Defining Required Channel Separations" on page 290 "Traffic" on page 295 "Network and Transmitter Settings" on page 298.

6.4.4.1

Interference Matrices
In Atoll, the probability of interference between pairs of subcells is stored in an interference matrix. The most important part of the interference matrix is a double array of C/I distributions. An interference matrix can be thought of as the probability that a user connected to an interfered sub-cell will receive a given C/I level where the only interference ("I"), is the interference coming from the interferer sub-cell. You can use more than one interference matrix in a single Atoll document. Interference matrices can be created using the data from a variety of sources: propagation, OMC data, drive tests, or other planning tools). They can be calculated individually or globally, they can be activated or deactivated, and they can have different resolutions. The set of active interference matrices will be combined by the AFP to provide interference estimations for each pair of subcells. The ability to combine different types of interference matrices with various individual interference matrices is an advanced capability based on the fact that an integral part of each interference matrix is its scope and context. The scale of sophistication related to the interference matrices is therefore rich: Level 1: You can work without an interference matrix. (the AFP is based on neighbour relations), Level 2: You can calculate an interference matrix based on surface integration, Level 3: You can calculate an interference matrix based on clutter weighting integration, 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. In this section, the following are explained: "Calculating a Simple Interference Matrix" on page 280 "Calculating Interference Matrices for Large Networks" on page 282 "Calculating an Interference Matrix Based on Clutter Weighting" on page 283 "Interference Matrixes Based on OMC Statistics" on page 284 "Importing and Exporting Interference Matrices" on page 284 "Defining Type-Dependant Quality Indicators on Interference Matrices" on page 285 "Analysing Interference Matrices" on page 287 "Generating Reports on Interference Matrices" on page 289 "Selecting Interference Matrices for the Frequency Allocation Process" on page 289.

6.4.4.1.1

Calculating a Simple Interference Matrix

Simple interference matrices are highly recommended as a background constraint system. They can be calculated on nation wide scale.

280

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To calculate an interference matrix: 1. Click the Data tab of the Explorer window. 2. Right-click the Interference Matrices folder. The context menu appears. 3. Select Create from the context menu. The Interference Calculation dialogue appears. 4. In the Interference Calculation dialogue, set the following options under Service Zone: start here 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 400. With a Margin: Enter a handover margin in the With a Margin text box. 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: by which you can set your IM to be stronger or weaker" on page 281). We recommend the usage of shadowing.

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.

6. Click OK to start the calculation. The results of the calculation can be found in a new item in the Interferences Matrices folder on the Data tab of the Explorer window. By default, the new interference matrix is active.

Caution:

Changing certain transmitter or subcell properties, such as power reduction, reception threshold, transmitter power or EIRP will make interference matrices invalid. If you change transmitter or subcell properties, you will have to recalculate the interference matrices.

Reliability Recommendations: by which you can set your IM to be stronger or weaker

You might occasionally get the impression that the constraints imposed on the AFP are not strong enough. Some indications of this are: The unlocked part of the AFP cost is 0 and, because of this, the AFP stops. Frequencies appear to be reused in too close proximity to each other in the resulting frequency plan. The distribution of frequency usage is not even and some frequencies are seldom used.

When you notice these or similar conditions, this means that the constraints were not strong enough and the AFP consequently had created an unacceptable distribution of frequencies. To correct this, you will have to create a more demanding interference matrix, thereby putting more constraints on the AFP. The best way to accomplish this is to increase the cell edge reliability 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 lower C/I for each given "reuse" and therefore less probability of achieving the required C/I target, and consequently more interference. You should also verify that the standard deviation's default value is properly defined and that it is properly defined in all clutter classes. Verifying the standard deviation is more important for Atoll documents converted from older versions or connected to a database.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

281

Atoll User Manual

Figure 6.137: The first computation zone Notes: Mean power control gains are not taken into account when calculating interference matrices. They are only applied when interference matrices are read in order to be 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 299.

6.4.4.1.2

Calculating Interference Matrices for Large Networks

Calculating interference matrices is very resource intensive. If you have a very large network, calculating an interference matrix that covers the entire network can require more computer resources than are available. It is more efficient to create a low resolution interference matrix on a nation-wide scale, possibly splitting the network into partial interference matrices if necessary. Once you have a low resolution interference matrix that covers the entire network, you can add high resolution interference matrices that cover the cities. If necessary in order to properly optimise the frequency plan, you can then add clutterweighted interference matrices calculated over the difficult areas so that they are carefully modelled. Last but not least, you can add some idle mode IMs to model the behaviour of packet switched data. The entire collection of IMs will be merged in the AFP and loaded into memory only when needed by the AFP. The first step is reducing the time and memory consumption so that the interference matrices can be calculated efficiently. To reduce resource consumption: 1. Use a path loss resolution and size appropriate for the interference matrices. Use a resolution that is the double of path loss data. Two important global parameters have a very strong influence on the IM calculation process. These parameters are the resolution and the interference reception threshold. a. Click the Data tab of the Explorer window. b. Right-click the Predictions folder. The context menu appears. c. Select Properties from the context menu. d. In the first page you will find these two very important parameters. The resolution is the resolution used during the IM integration calculation. This parameter is memorized in the IM so that the IM (and later the AFP) knows with which resolution the IM has been created. Do not hesitate to mix high resolution IMs (for city centre) with low resolution IMs (rural). The AFP will seamlessly perform the merge (Merging IMs does not slow down Atolls AFP). The interference reception threshold defines the level from which all interferers are ignored. If you increase it to -115 dB or even -110 dB, you will lose very little interference information, but your calculation will be much faster.

2. Define a large handover margin, for example, 2 to 4 dB. 3. Save IMs and coverage predictions, etc., externally, if possible, and delete unnecessary coverage predictions to reduce resource consumption. 4. If you have multiband transmitters, keep in mind that the multiband pathloss option (See "Advanced Modelling of Multi-Band Transmitters" on page 415) creates a lot of overhead when the interference matrix is calculated. For more information, see the Administrator Guide. Note: For more information on reducing resource consumption, refer to "Performance and Memory Issues in Big Projects" in the Administrator Guide.

282

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks If you have more than 20 000 transmitters in yout network, you might need to split your Interference matrice calculation into 2 or 4 calculations. To calculate interference matrices for a large network: 1. Create a computation zone that covers part of the network. For information on creating a computation zone, see "Creating a Computation Zone" on page 223. In Figure 6.138, the computation zone is indicated by the red outline.

Figure 6.138: The first computation zone 2. Calculate an interference matrix for the area covered by the computation zone as explained earlier. 3. Create a new computation zone that partly overlaps the area covered by the first computation zone. In Figure 6.139, the area covered by the first computation zone is indicated by the black outline.

Figure 6.139: The second computation zone 4. Calculate an interference matrix for the area covered by the computation zone. 5. Repeat step 1. to step 4. until have created interference matrices for the entire network, as shown in the following figures.

Note:

The computation zones do not need to overlap as indicated in the figures because the AFP scope extends beyond the computation zone. For more information, refer to "The Scope of the AFP and the Scope of the Interference Matrix" on page 299

6.4.4.1.3

Calculating an Interference Matrix Based on Clutter Weighting

Calculating an interference matrix based on clutter weighting is a straight-forward process that delivers a large increase in quality. However, you should be aware that this process is relatively time-consuming and therefore not suited for nationwide calculations. It is better suited to local frequency allocations where frequency allocation is difficult. By default, Atoll gives a higher priority to this type of interference matrix when combining interference matrices, so an interference matrix based on clutter weighting can be used with other interference matrices that are less precise. When you evaluate a frequency plan created with a clutter weighted IM, you should use a clutter-weighted evaluation method; otherwise, you will not perceive the improvement in the frequency plan. The first step in creating an interference matrix based on clutter weighting is creating temporal traffic model.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

283

Atoll User Manual To create a temporal traffic model: 1. Create a user profile for an active user with voice service, with calls lasting a total of 3600s per hour (i.e., 1 Erlang). For information on creating a user profile, see "Modelling User Profiles" on page 256. 2. Create an environment using this user profile with a density of 1 and pedestrian mobility type. For information on creating an environment, see "Modelling Environments" on page 256. 3. Assign appropriate clutter weighting to the environment. 4. On the Geo tab, create a new user profile traffic map based on user profile environments. From the list on the drawing toolbar, select the environment created earlier, click the polygon button and draw a polygon encompassing the computation zone. This raster map now appears in the Traffic folder. Name the map "Temporal IM map." "Creating a User Profile Environment Based Traffic Map" on page 259. The second step in creating an interference matrix based on clutter weighting is creating a traffic capture using this traffic map. You should seet this traffic capture to be the default traffic capture. For information on creating a traffic capture, see "Calculating and Displaying a Traffic Capture" on page 262. The third step in creating an interference matrix based on clutter weighting is calculating the interference matrix. When calculating the interference matrix, select the option Traffic spreading based on the maps used in the default traffic capture in the IM calculation dialogue.

6.4.4.1.4

Interference Matrixes Based on OMC Statistics

An OMC interference matrix is an interference matrix created using a statistical analysis of the RXLEV measurements performed by the mobiles in the network. Atoll's AFP can fully exploit this type of interference matrix. The main advantage of an interference matrix based on OMC statistics is that, in many cases, the OMC database is the only reliable source of network information. However, an OMC-based IM also has a certain number of inherent. 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 important 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 important limitation, applicable to all OMC-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 yet have the same BCCH, their interference will not be present in the OMC interference matrix. The last limitation can be avoided by adding the BCCH plan to the IM scope. This way Atoll's AFP is aware that certain interference entries, (or more precisely none interference entries) have 0 likelihood, and will supplement the information with propagation interference information.

6.4.4.1.5

Importing and Exporting Interference Matrices

You can import interference matrices from and export them to the following formats: IM0: One matrix per line IM1: One CI threshold and probability pair per line for each interfered/interfering subcell pair. IM2: Only co-channel and adjacent channel interference values. CLC: One value per line. The accompanying dictionary (DCT) file gives the correspondence between the transmitter identifiers and the transmitter names. Other: Forsk provides import macros for other simple IM formats. For information on these IM formats, or on others you might want to import, please contact Support.

For more information on the interference matrix file formats, see the Technical Reference Guide. In this section, the following are explained: "Importing Interference Matrices" on page 284 "Storing Interference Matrices Externally" on page 285 "Exporting Interference Matrices" on page 285.

Importing Interference Matrices

Atoll supports IM0, IM1, IM2, and CLC interference matrix files. Atoll also supports a simplified format that gives the interfered subcell, the interfering subcell, the co-channel interference probability, and the adjacent channel probability. For more information on the simplified format, see the Technical Reference Guide. When you import several interference matrices that describe the same interfered-interferer pairs, Atoll only takes the first description of the pair. When descriptions of the same interfered-interferer pair are found in subsequent files, the description is ignored. 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.

284

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To import interference matrices: 1. Click the Data tab of the Explorer window. 2. Right-click the Interference Matrices folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the file type from the Files of Type list. 5. Select the file to import. If you are importing a CLC file, Atoll looks for the associated DCT file in the same directory. When this file is unavailable, Atoll assumes that the transmitter identifiers in the CLC file are the same as the transmitter names. 6. Click Open. A message appears asking whether Atoll should merge the imported interference matrix into the GSM/GPRS/EDGE document: 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 285. Click No to store the interference matrix externally, but linked to the GSM/GPRS/EDGE document.

7. The interference matrices are imported into the current Atoll document and appear as new items in the Interference Matrices folder. Note: 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 399).

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. Since 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 too big. To store an interference matrix externally: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the 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 dialogue appears. 5. Under Interference Matrices Storage, on the General tab, click the Externalise button. A confirmation message appears. 6. Click Yes to confirm, No to cancel. The Save As dialogue 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. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the 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 dialogue 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.

6.4.4.1.6

Defining Type-Dependant Quality Indicators on Interference Matrices

As explained in "Interference Matrices" on page 280, you can calculate several individual interference matrices for large networks with the intention of recombining them as unique C/I probabilities. In the same way, you can combine several interference matrices of different types according to their quality indicators and the strategy defined by the AFP module used. For more information on how the optional Atoll AFP module combines the data from more than one interference matrix, see "The Atoll AFP Module" on page 425.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

285

Atoll User Manual You can create or import 9 different types of interference matrices: 1. Interference matrices based on path loss (propagation data) matrices Their reliability depends on the accuracy and correctness of network and geo data. 2. Interference matrices based on reselection statistics from the OMC Their reliability is usually low due to the difference between the locations where mobiles are switched on and where they are actually used to access the network. 3. Interference matrices based on handover statistics from the OMC Their reliability is usually low due to the fact that interference is measured only among existing neighbours (which might not be correctly assigned). This type of interference matrix is highly correlated with the neighbour relations. It can be used to remove excessive neighbour constraints. However, it can not be used to complete any missing neighbour 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. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the 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 dialogue 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: 1. For matrices based on path loss (propagation data) matrices: The standard deviation The resolution Whether the interference information (probabilities) correspond to traffic or surface area.

286

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Note:

Matrices based on propagation can store addtional information, such as server selection or the HO margin value, if shadowing has been taken into account for their calculation and, if so, the cell edge coverage probability. This information can then be used by the AFP for some calculations. For more information, see "The Atoll AFP Cost Tab" on page 433 and "The Atoll AFP Advanced Tab" on page 442.

2. For matrices based on reselection statistics from the OMC: The statistic duration Whether the interference information (probabilities) correspond to traffic or surface area.

3. For matrices based on handover statistics from the OMC: 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.

4. For matrices based on RXLEV statistics from the OMC: The statistic duration Whether the interference information (probabilities) correspond to traffic or surface area.

5. For matrices based on drive test data: The standard deviation, depending on the equipment quality and measurement post-processing The average number of points collected at each matrix calculation point.

6. For matrices based on CW measurements: 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.

7. For matrices based on scan data drive tests: 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.

6.4.4.1.7

Analysing Interference Matrices

Atoll includes an interactive frequency planning tool that enables you to analyse interference matrices for different transmitters and their TRXs. For any selected transmitter and its TRX, you can use the AFP module to display the lists of interfering and interfered transmitters, their TRXs, and the corresponding costs calculated. The AFP module also displays the interference relations between transmitters in the map window. Co-channel and adjacent channel interferences are separately treated. You can display all or strongly interfered and interfering transmitters, and interfered and interfering neighbour transmitters. To analyse interference matrices: 1. Click View > Interactive Frequency Planning Tool. The Interactive Frequency Planning Tool window appears. 2. Select the Interference Matrix Analysis tab. 3. Select a transmitter from the Transmitter list. Note: You can also select a transmitter by clicking its symbol in the map window.

4. Select the TRX type from the TRXs list. 5. Select an AFP module from the AFP Module list. 6. If you want to modify parameters that will influence frequency planning before running the tool, click General Parameters button and select one of the following options from the menu: AFP Module Properties: For information on the options, see "The Atoll AFP Module" on page 425. AFP Parameters: In the AFP Launching Parameters dialogue, 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. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

287

Atoll User Manual 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 "Defining Required Channel Separations" on page 290. Exceptional Pairs: For information on the options, see "Defining Required Channel Separations" on page 290. Intra-Technology Neighbours: For information on the options, see "Planning Neighbours" on page 241.

7. Click Run. 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 Interference Matrices folder on the Data tab of the Explorer window. If the interference matrices in the Interference Matrices folder are inactive or 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 Filter 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.

The following figures illustrate the display of interference information.

Figure 6.140: Displaying interference information

288

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.140: Displaying interference information

6.4.4.1.8

Generating Reports on Interference Matrices

You can generate reports on one or all of the interference matrices in the Interference Matrices folder. In this section, the following are explained: "Generating a Report on a Single Interference Matrix" on page 289 "Generating a Report on All Interference Matrices" on page 289.

Generating a Report on a Single Interference Matrix

To generate a report on a single interference matrix: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Interference Matrices folder.

3. Right-click the interference matrix on which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Interference Matrix Scope dialogue appears with the report details: 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.

Generating a Report on All Interference Matrices

In order to generate a report on all the interference matrices in the Interference Matrices folder: 1. Click the Data tab of the Explorer window. 2. Right-click the Interference Matrices folder. The context menu appears. 3. Select Generate Report from the context menu. The Interference Matrix Scope dialogue appears with the report details: 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.

6.4.4.1.9

Selecting Interference Matrices for the Frequency Allocation Process

When you allocate frequencies automatically or interactively using the AFP in GSM/GPRS/EDGE, the allocation process uses interference matrices. You can select which interference matrices the automatic or interactive frequency allocation process will be based on. When you use more than one interference matrix, the AFP combines the data. For more information on how the optional Atoll AFP module combines the data from more than one interference matrix, see "The Atoll AFP Module" on page 425. To activate an interference matrix to be used for an automatic frequency allocation: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Interference Matrices folder.

3. Right-click the interference matrix you want to use in an automatic frequency allocation. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

289

Atoll User Manual 4. Select Activate from the context menu. The selected interference matrix is now active and will be used the next time you use an AFP. You can deactivate the interference matrix by right-clicking it and selecting Deactivate from the context menu. Note: When you have several active interference matrices in a project, only those intersecting the AFP scope will be loaded, in order to avoid consuming more memory than necessary during the AFP process. The "RAM Consumption" field in the interference matrix properties dialogue indicates how much memory the interference matrix will take. For embedded matrices, the AFP loads them only during the AFP process, so the "RAM Consumption" field will always be zero. For external matrices, the AFP reads them to check their scope and then decides whether they are to be loaded into memory or not, so, the "RAM Consumption" field will always be a non-zero value (after running the AFP). As a result, it is recommended to embed interference matrices as long as the document file size is lower than 2 Gb.

6.4.4.2

Defining Required Channel Separations

Channel separations define how many channels should separate different TRXs under set circumstances. Channel separations are necessary if you are using automatic frequency planning. Carefully defining channel separations will help you increase the efficient use of channels in your network. Defining channel separations is a three-step process in Atoll. In step 1, you set general separation rules that define the channel separation that should exist between TRXs on the same transmitter, same site, or between neighbours. In step 2, you define separation rules for the TRXs of specific pairs of transmitters. During automatic frequency planning, the separation rules can be overridden by the specific entries in the Exceptional Separation Constraints table. You can edit constraints directly from the AFP output dialogue. The Exceptional Separation Constraints table is automatically updated with any changes you make in the AFP output dialogue. In step 3, you ensure that your neighbour relation constraints are correctly weighted by the neighbour importance. In this section, creating separation rules and exceptional separation constraints is explained. As well, displaying and modifying exceptional separation constraints on the map is explained: "Defining Separation Rules" on page 290 "Importing Separation Rules" on page 290 "Defining Exceptional Frequency Separations" on page 290 "Displaying Exceptional Frequency Separations on the Map" on page 291 "Adding or Removing Exceptional Frequency Separations Using the Mouse" on page 292.

6.4.4.2.1

Defining Separation Rules

You can define separation rules that set the channel separation that should exist between pairs of TRXs on the same transmitter, same site, or between neighbours after a frequency allocation. To define separation rules: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Separation Rules from the context menu. The Separation Rules table appears. 4. In the row marked with the New Row icon ( to define: ), 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.

6.4.4.2.2

Importing Separation Rules

If you have an existing set of separation rules, you can import them into your GSM/GPRS/EDGE document. To import separation rules: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Separation Rules from the context menu. The Separation Rules table appears. 4. Import the file as explained in "Importing Tables from Text Files" on page 63.

6.4.4.2.3

Defining Exceptional Frequency Separations

The separation rules apply to the entire network. However, in a few cases, the separation rules might not apply to specific pairs of TRXs. In this case, you can set exceptional frequency separations to define channel separations that apply to

290

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks specific pairs of TRXs. During automatic frequency planning, the separation rules are first considered, but they can be overridden by specific entries in the Exceptional Separation Constraints table. To define exceptional frequency separations: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Exceptional Pairs from the context menu. The Exceptional Separation Constraints table appears. 4. In the row marked with the New Row icon ( to define: ), 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. Note: 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 volation. See "The Results of the Automatic Frequency Allocation" on page 307 for more information.

6.4.4.2.4

Displaying Exceptional Frequency Separations on the Map

You can display the exceptional frequency separations defined in the Exceptional Separation Constraints table on the map. To display the exceptional frequency separations: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Display Options from the context menu. The Separation Constraint Display dialogue appears. 4. Select the Transmitter 1 TRX Type and the Transmitter 2 TRX Type to display. Note: 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 Visual Management button (

) in the Radio toolbar. The menu appears.

6. Select Exceptional Pairs (AFP) from the context menu. 7. Click the Visual Management button ( ) in the Radio toolbar.

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 6.141): 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.

Figure 6.141: Displaying exceptional frequency separations

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

291

Atoll User Manual 9. In order to restore colours and cancel the neighbour display, click the Visual Management icon ( ) again.

Tip:

You can define exceptional pairs directly on the map. For information, see "Adding or Removing Exceptional Frequency Separations Using the Mouse" on page 292.

6.4.4.2.5

Adding or Removing Exceptional Frequency Separations Using the Mouse

You can add and remove define exceptional frequency separations directly on the map. To define an exceptional frequency separation on the map: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Display Options from the context menu. The Separation Constraint Display dialogue appears. 4. In Transmitter 1 TRX Type list and Transmitter 2 TRX Type list, select the TRX type for which you want to define separation constraints. 5. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

6. Select Exceptional Pairs (AFP) from the context menu. 7. Click the Visual Management button ( ).

8. Click the reference transmitter on the map. Atoll displays the existing exceptional frequency separations for this transmitter. You can do the following: To add an exceptional frequency separation: Press CTRL and click on the second transmitter. A dialogue 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. ) again.

9. In order to restore colours and cancel the neighbour display, click the Visual Management icon (

Tip:

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 Visual Management button ( ) in the Radio toolbar. For more information, see "Displaying the Coverage of Each Neighbour of a Transmitter" on page 247.

6.4.4.2.6

Adjusting the Relative Importance of Neighbours

In many cases, neighbour relations are the strongest constraints on the AFP. The neighbour importance field of the Neighbours table enables the AFP to partially ignore weak or distant neighbours and concentrate more on the more important neighbours. Neighbour importance can be: Either calculated by Atoll Or imported, based on OMC statistics. Or imported and completed by a calculation performed in Atoll

This section describes the use of this feature in various scenarios.

Tip:

Take a look your neighbour allocation before running the AFP. Often poorly defined neighbour relations cause poor defined frequency plan.

Example 1: Automatic Neighbour Allocation

Neighbour importance has two major roles in Atoll: It is used to weight the neighbour relation in the AFP. It is used to rank the neighbours so that Atoll can select the N most important neighbours.

The following configuration is recommended if you intend to use the neighbour importance in the AFP. Coverage Factor: 1% to 81% Adjacency Factor: 20% to 90% Co-site Factor: 70% to 100%

292

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Notes: The default values for calculating importance values are: Coverage Factor: 1% to 30% Adjacency Factor: 30% to 60% Co-site Factor: 60% to 100%

Changing the default values changes the priority definitions of the neighbour allocation algorithm. For more information, see the Technical Reference Guide.

Figure 6.142: Automatic neighbour allocation You can run the AFP once the neighbour allocation has run and the results have been committed.

Example 2: Importing Neighbour Importance

There are several different sources of neighbour importance: OMC HO statistics Test mobile data measurements (which ignore interference between non-neighbours) Other.

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.

Example 3: Completing or updating the neighbour importace information

After adding new sites, or in order to resolve handover problems, you might need to run a new automatic neighbour allocation. However, when you run an automatic neighbour allocation, Atoll recalculates all existing neighbour relations and overwrites existing relation weights. If the changes to the network were only minimal, you can assume that the existing neighbour relations and weights were accurate. You can also assume that the newly calculated neighbour relations and weights are less important, because they are only minor modifications to a working system. You can preserve the existing neighbour relations and weights while at the same time creating neighbour relations for the new sites, by first exporting the existing neighbour relations, running an automatic neighbour allocation to create neighbour relations along with their weights, and then re-importing the original neighbour relations and weights. Atoll will then replace the newly calculated neighbour relations and weights with the original values, where they exist. To extend an existing neighbour relation: 1. Export the current intra-technology neighbour relations once to a file called AllCurrentNei.txt using the Export command on the Neighbours table's context menu. For information on exporting the neighbour relations, see "Exporting Tables to Text Files" on page 61. 2. Export the intra-technology neighbour relations a second time to a file called AllCurrentNei_Importance.txt, this time selecting the neighbour relations with a reliable neighbour importance.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

293

Atoll User Manual 3. Import the AllCurrentNei.txt file into the Exceptional Pairs of Intra-technology Neighbours table. This will set all existing neighbour relations to forced, which is a pre-requisite to extending an existing allocation. For information on importing the neighbour relations, see "Importing Tables from Text Files" on page 63. 4. Set the importance weighting in the Neighbour Importance Weighting dialogue in order to keep the values assigned for importance below a certain value. For example, if you want all importance values to be under 50%, you can set the Max Importance values as indicated in Figure 6.143. For information on setting the importance weighting, see "Configuring Importance Factors for Neighbours" on page 242. 5. Run an automatic neighbour allocation to allocate neighbours to new sites and assign importance to neighbour relations that do not already have an importance assigned. For information on defining and running an automatic neighbour allocation, see "Allocating Neighbours Automatically" on page 243.

Figure 6.143: Setting neighbour importance weighting As you can see in Figure 6.143, the importance assigned to all new neighbour relations will be weak. 6. Commit the allocation. 7. Import the AllCurrentNei.txt file into the Neighbours table. When Atoll prompts you to delete existing neighbours, click No. In Figure 6.144, you can see that neighbour relations now include old neighbour relations with a higher importance and new neighbour relations with a lower importance automatically calculated by Atoll.

Figure 6.144: Neighbours table

Example 4: Importing Partial Sources of Neighbour Importance

You can import partial sources of neighbour importance. The data, in the form of a probability from 0 to 1, are imported into the Importance column of the Neighbours. If your network statistics do not provide you with the importance of neighbours, you can calculate neighbour importance using other statistics. Then, you can import this calculated importance into Atoll where it can be used by the AFP. For example, if you have statistics on the number of handovers between two sectors, you can calculate the importance of the different neighbours of each cell using these statistics. For example, if you have two sectors, A and B, and you use X to represent the "Average Activity of a Relationship" in the network, i.e., the sum of all handovers for all sectors divided by

294

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks the number of neighbour relationships. If the number of handovers from sector B (neighbour of sector A) is Y, the importance of sector B for sector A can be calculated using the following equation:

This way, when a relationship has more than the average number of handovers, its importance will be the highest it can be in Atoll, i.e., 100%. Otherwise, its importance will be less than the average

6.4.4.3

Traffic
When allocating frequencies, information from the interference matrix is often used along with AFP traffic. In Atoll, these two elements are not correlated. For more information on why interference matrices and AFP traffic are not correlated in Atoll, see "Various tips and tricks" on page 459. The AFP uses traffic to differentiate between heavily loaded TRXs (which would generate a high cost if they are interfered) and TRXs with a low load (which can be interfered without generating a high cost). In other words, the AFP traffic model is basically a weighting system. In more advanced AFP use, AFP traffic can be used, for example, to optimise the number of TRXs and estimate blocking. AFP traffic input will be described in this section. It is one of the most important AFP inputs because: 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 proportionate to the traffic load. In case of frequency hopping, the interference caused by a given interferer usually increases when its traffic load increases. In its most advanced use, Atoll's AFP can optimise the tradeoffs 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. These methods are explained from the simplest to the most advanced.

Method 1: All Traffic Loads Are Set to 1

The amount of traffic is therefore exclusively determined by the number of required TRXs. As a result, all TRXs are considered equally. This method has to be used in any case where the only information you have is the number of required TRXs.

Method 2: Traffic Loads Are Entered Manually

In this method of providing traffic information to the AFP, the AFP traffic is determined by the manually entered traffic load values, and by the manually entered number of required TRXs. The disadvantage of this method is that this information must usually be calculated and entered manually; it is not easy to obtain automatically. If you have access to this information, you can use this method.

Method 3: Traffic Loads Are Imported from OMC Data

This method is recommended for use with Atoll's AFP, however, it is not supported by all external AFP suppliers. Using this method, the AFP considers the number of required TRXs as a recommendation only. The actual traffic demand is taken from the Subcells table, where the data has been updated using traffic demands supplied by the OMC (See "Importing OMC traffic data into the subcell traffic view" on page 253). If you want the AFP to use the traffic information that you have set in the subcell table, you must go thrrough the following 3 steps: Step 1: On the Cost tab of the Atoll AFP Module Properties dialogue, select the option Based on the traffic demand (from subcell table or default traffic capture) (see Figure 6.145). For more information on the Atoll AFP Module Properties dialogue, see "The Atoll AFP Module" on page 425.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

295

Atoll User Manual

Figure 6.145: Setting the option on the Cost tab Step 2: On the Global Parameters tab of the third AFP wizard dialogue, select the option From subcell table under Traffic (Subcell load, demand and target rate of traffic overload). (see Figure 6.146). For more information on the Atoll AFP Module Properties dialogue, see "The Atoll AFP Module" on page 425.

Figure 6.146: Setting the option on the Global Parameters tab of the AFP dialogue Step 3: On the AFP Model and Allocations tab of the first AFP wizard dialogue, select the option Optimisation of the number of TRXs under Strategies (see Figure 6.146). For more information on the Atoll AFP Module Properties dialogue, see "The Atoll AFP Module" on page 425.

296

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.147: Setting the option for the optimisation of the numbers of TRXs

Method 4: Traffic is extracted from Traffic maps

In this method, you use traffic maps, but rely on external dimensioning to determine the number of required TRXs. This method also requires the calculation of a traffic capture before launching the AFP. The traffic capture will transform the traffic maps into the load estimates that are required for the AFP. The traffic model is a map, and therefore gives probabilistic traffic estimation per pixel. The AFP needs either traffic demands or loads. In both case, it needs this information at the subcell or cell level. The traffic capture is responsible for this conversion. In order to use this option, you must do the following: In the AFP dialogue, you must redirect the traffic source to be the traffic capture as shown in Figure 6.148.

Figure 6.148: Selecting the default traffic capture results as the source of traffic

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

297

Atoll User Manual Using a traffic model is an enhanced use of Atoll. You must be sure that your traffic modelling is correct and compatible with the service zone modelling. You must also be aware of mobility compatibilities, service compatibilities, mobile compatibilities, and layer definitions. The inherent complexities of working with a traffic model discourage many users from working with a traffic model, even though theoretically this is the best way of planning a GSM network. It is even possible to restrict the usage of a certain map (or set of maps) to a certain HCS layer. We highly recommend the usage of this feature since it reduces this complexity (See "Creating a Traffic Capture" on page 263).

Method 5: Using a Traffic Model with Dimensioning

In this method you use a traffic model along with dimensioning (see "Dimensioning a GSM/GPRS/EDGE Network" on page 267). Usually the number of required TRXs is an input. The number of required TRXs can be strict or lightly modified. If you decide to use Atoll's dimensioning model to determine the number of required TRXs: Thoroughly test your traffic model and network. Carry out the dimentioning, check its result, and commit it.

By commiting the required number of TRXs you have already commited the load and the demand information to the cells or subcells. You are now ready to use the AFP.

6.4.4.4

Network and Transmitter Settings

There are several different approaches that you can use in order to correctly model layers and subcells. These approaches offer different levels of accuracy and can help you to increase the spectral efficiency of your network. Approach 1: The simplest approach is to use only one HCS layer and only two TRX types (i.e., BCCH and TCH) for all transmitters. Approach 2: The second approach involves modelling HCS layers in a more complete fashion. HCS layers play several roles in Atoll. Their most important role is related to the way Atoll manages traffic maps. Different layers have different priorities and mobility limitations. You also have the possibility to manage traffic overflow by allowing traffic to flow from one layer to another. The objective of these options is to model the behaviour of a real network, where two potential servers that do not belong to the same layer usually do not compete for the best server. When calculating an interference matrix, or when making an interference study, HCS layers are used to create service zone maps which are the basis of these calculations. If two transmitters belong to different layers, they can both serve the same pixel even if the received signal of one is much stronger than the received signal of the other. For equal 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 study also increase. When using this approach, 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. Approach 3: In this approach 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: Whether transmission power is maximum or average Whether reception is managed by reception level or by distance Scheduling priority Whether the subcell handles packet-switched or circuit-switched traffic Quality requirement for high bit-rate coding schemes. Spectral restrictions (often present with the GSM extended frequencies) Frequent use of high bit rate modulations Whether the BCCH is multi-band or single BCCH.

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 404. With this approach, there is more than one method of improving the accuracy of modelling the network. The common point among these methods 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 through accurate definition of 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. Approach 4: With this approach, 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. 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 276.

298

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 3. Create a traffic capture and calculate it. For information on creating a traffic capture, see "Calculating and Displaying a Traffic Capture" on page 262. 4. Perform a KPI calculation and commit it. For more information on KPI calculation, see "Calculating Key Performance Indicators of a GSM/GPRS/EDGE Network" on page 344. 5. Adjust the traffic coefficient in the traffic capture so that the average level of traffic loads is correct. 6. Study the cases were 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.

6.4.5

Automatic Resource Allocation Using an AFP Module

As with other resource allocation methods described in this section, automatic allocation can be made in various ways, from simple to complicate. In "The Atoll AFP Module" on page 425, these different methods of automatically allocating resources are explained. What you will find in this section is the very basic information, of which you must be aware, regardless of the level of optimization you need. The Automatic Frequency Planning (AFP) tool is a component designed to perform large-scale and small-scale resource allocation. It can add or remove TRXs, and assigning them frequencies or MAL lists, as well as MAIOs. The AFP can also assign the HSN, the BSIC, various KPIs, and even preferred group names. When the AFP assigns resources, it takes traffic demand, separation constraints, and interference limitations into consideration. Atoll allows the use of third-party AFP tools, as well as the use of an optional Atoll AFP module. The AFP attempts to create an optimal resource allocation, i.e., an allocation that minimises interference and complies with a set of user-defined constraints. Most AFPs assign a cost to the various constraints and then use cost-based algorithms to 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 Atoll's AFP module is described in "The Atoll AFP Module" on page 425. In "AFP Prerequisites (IM, Separations, Traffic, etc.)" on page 279, you could see how different levels of preparation often provide a different optimisation quality. In this section, the same rule applies, although in a slightly different form: The basic level will be covered in this section since it is common to all AFP models that work with Atoll. Advanced use of the AFP requires an understanding of the cost function, the algorithm, and the parameters specific to the AFP model. Therefore, advanced use of the AFP is explained in "The Atoll AFP Module" on page 425, when Atoll's AFP model is explained. You will need a bit of additional basic information to use the AFP: You must understand what the scope of the AFP is (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 299. You must understand that a network validation process takes place before the AFP starts. For more information, see "The Network Validation Process" on page 301. You must understand the concept of the target calculation time since this is the "convergence criterion" of the AFP. For more information, see "The AFP's Target Calculation Time" on page 302. You must have a working understanding of the AFP dialogue. For more information, see "Running an Automatic Frequency Allocation" on page 302 A dialogue with detailed information on the output of the AFP helps you understand the AFP results so that you can assess the proposed frequency plan before committing the frequency plan. For more information, see "The Results of the Automatic Frequency Allocation" on page 307.

6.4.5.1

The Scope of the AFP and the Scope of the Interference Matrix
The message in Figure 6.149 is an example of the type of message Atoll displays before launching the AFP. You can see that in this message we are informed that 472 subcells were selected for the AFP, although 758 subcells were loaded. The AFP cost calculation will therefore be performed for the TRXs of 758 subcells. This subset of subcells is the AFP scope. Whatever TRX or subcell that is not in the AFP scope is totally ignored.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

299

Atoll User Manual

Figure 6.149: AFP validation messages In Figure 6.149, the 472 subcells selected for the AFP process have many potential interferers, neighbours, neighbours of neighbours, or transmitters with exceptional separation constraints with them. No AFP can perform a good allocation for these 472 subcells without also referring to the surrounding part of the network. The AFP considers the portion of the network that is external to the AFP that is referred to as "locked". The precise definition of the AFP scope is based on 4 groups of subcells: (ALL, NET, SEL, and RING): ALL = All the transmitters in the project. NET = Active transmitters that are not filtered, neither by the main Transmitters folder nor by the main Sites folder. SEL = A subset of NET containing transmitters that belong to any folder from which the AFP was launched and that are located inside the focus zone and the computation zone. RING = Transmitters belonging to NET but not belonging to SEL yet having relationship with at least one of the transmitters in SEL: If the "load all interferers propagating in focus zone" option is checked (an option in the AFP wizard), all transmitters whose calculation radii intersecting the calculation radii of any transmitter in SEL will be included in RING. For large calculation radii (20 km for example), a single site can have a very large RING loaded. Neighbours of SEL transmitters are always included in RING. If one transmitter of an exceptional pair is included in SEL and the other is not, then the other will be included in RING as well. If BSIC assignment is required, then all the second order neighbours (neighbours of a neighbour) will be included in RING as well.

Both the RING and the SEL parts of the network are loaded and form the AFP scope. The RING part is locked for all parameters that can be assigned (BSIC, HSN, MAL, MAIO, and channels). The SEL part can be assigned some parameters but only the ones specified checked in the AFP wizard. The locked part of the network is not only the part that belongs to RING and not to SEL. There are other locking options available: Individual transmitters can be locked for channel (and MAL), HSN or BSIC assignment. Individual TRXs can be locked for channel (and MAL) assignment. Individual subcells can be locked for HSN assignment.

Therefore, even subcells that are in SEL can be locked. Note: In Atoll's AFP, the cost calculated for locked TRXs is reported as locked, however, the cost of locked TRXs can be modified by the AFP even if the TRX itself cannot be. The reason is that a bad relation with another TRX which is not locked can appear. Atoll's AFP reports to the user which part of the cost can be modified and which part.

The Scope of the Interference Matrix

There are three types of interference matrix scope: A global scope, used when generating a report for the entire interference matrix folder. The global report considers all the active matrices in the folder. This scope is simply "NET" as defined above. The private scope of each interference matrix. For more information on the definition of the interference matrx, see "Interference Matrices" on page 280.

300

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks The scope of the newly calculated interference matrix. This scope consists on the AFP scope for an AFP launched on the main transmitter folder. When calculating this IM, All the interferers of this scope (SEL + RING) are invoked into the calculation, therefore it is not possible to perform small IM calculation without a filtering zone.

6.4.5.2

The Network Validation Process

When you launch the AFP, you start with the process of setting the parameters. After setting the parameters of the AFP, AFP verifies the data and optimises data storage. All this is aimed at providing fast access to data needed by the AFP. Since the AFP allocation process is long and complex, if it can detect a problem before it starts, it can case you time; it will be much harder to detect a problem after the AFP starts. The validation process might generate many warnings or errors that must be taken into consideration. These warnings and errors are displayed in the Event Viewer (see Figure 6.150). It is recommended to use these messages to correct the network data and to continue with the AFP process only once all the messages have been taken into consideration and all the data has been corrected. If any message is not clear, you can contact Forsk's technical support for more information.

Figure 6.150: Warnings and errors during network validation phase When you double-click a message in the Event Viewer, Atoll displays the message in a separate dialogue (see Figure 6.151).

Figure 6.151: Message from Event Viewer The message in Figure 6.151 means that the value entered in the AFP weight column ("COST_FACTOR" in the database) of the Subcells table for the TCH of transmitter BRU067_G3 is invalid. A value of -2 for the cost factor means that the AFP should generate the worst assignment possible for the transmitter. Atoll automatically resets this value to 1 in order to avoid such calculation errors.You might want to find out where this mistake came from in order to avoid possible errors in the future. The following table contains a few examples of the AFP range checks:

Limitation
Lowest/Highest possible HSN Limitation on the number of different frequency domains Lowest BSIC/Highest BSIC Maximum required channels at a subcell Lowest/Highest value of AFP weight Default value of AFP weight Lowest/Highest value of min C/I Default value of min C/I

Value
0 - 63

Comments

10,000

Each exclusion of frequencies at a transmitter might create a new domain

0 - 77 62

0 - 100 Used if the AFP weight is out of domain

1 2 - 25 12

Used if the parameter is out of range

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

301

Atoll User Manual

Limitation
Maximum power offset Highest value of Reception threshold Lowest value of Reception threshold Default value of Reception threshold Limitation on separation requirements Limitation on the actual number of TRXs in a transmitter

Value
25 -50

Comments

-116 Used if the parameter is out of range Will be eliminated in the future

-102

Must be <= 7

50

6.4.5.3

The AFP's Target Calculation Time

In Atoll, one of the last parameters to set before running the AFP is the target calculation time. In theory, an exhaustive AFP calculation could last indefinitely; therefore, when you run the AFP, you must define a convergence criterion. In Atoll, this convergence criterion is the target calculation time (TCT). The advantage of having a target calculation time is that it is a concept that is easily understood: you set a time (for example, 12 hours) by which the AFP must calculate the optimal frequency plan. Once the target calculation time has expired, the AFP stops. If you are satisfied with the frequency plan, you can stop the AFP before the TCT has been reached. Once the target calculation time (TCT) has expired, (or even before, if you are satisfied with the cost reduction), you can stop the AFP. The AFP will continue after the end of the TCT, attempting a few additional solution, however, Atoll took the TCT into consideration when making its calculations, so there will be very little improvement after the TCT has expired, so you can safely stop the AFP. The quality of the final results is defined by the TCT and the size of the network. For example, if you are working with a medium to large-sized network of about 5000 transmitters, 12000 TRXs, 50 frequencies, and an interference matrix with 500,000 entries, with Atoll's AFP: Use a TCT of 1 hour if you want the most basic Frequency Plan Quality, (FPQ) Use a TCT of 12 hours (over night) if you want a good FPQ Use a TCT of 48 hours (week-end) if you want the best possible FPQ.

Atoll's AFP is tested systematically with big network environments as well as with small networks. A test network of 33000 transmitters (100000 TRXs, IM with 6000000 entries) requires a few hours for completing its first solution. On the other hand, small networks are calculated much faster and can generate many solutions each minute. The number of solutions can help you to estimate if the AFP will fully use its optimization potential. If you run the AFP, and if only one are two solutions are provided after 5% of the target computation time, one can guess the time is too small. When the network it very large, such as 20000 transmitters or even more, and you cannot run the AFP for more than a week end, you must calibrate the AFP over a representative sample. This help to achieve optimal performance within the weekend or over-night time-frame.

6.4.5.4

Running an Automatic Frequency Allocation

Atoll provides an AFP interface that can be used with the optional Atoll AFP module or with a third-party AFP module; the options you select in the AFP interface are valid for either. You can perform automatic frequency planning on all transmitters or only on a group of transmitters. All the transmitters involved, including potential interferers and transmitters involved in separation constraints, are taken into account but allocation is performed only on the non-locked items (subcells or TRXs) of the selected transmitters. To run an AFP session: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder or click the Expand button ( click a group of transmitters. The context menu appears. ) to expand the Transmitters folder and right-

3. Select Frequency Plan > Automatic Allocation from the context menu. The AFP dialogue appears with the AFP Selection tab (see Figure 6.152).

302

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.152: The AFP dialogue

4. Under AFP Model and Allocations, select "Atoll AFP Module" from the AFP Module list. You can click the Browse button ( Note: ) to access the properties of the selected AFP module.

If you are using an AFP module other than Atoll's AFP module, please refer to that AFP module's documentation for information.

When the AFP first starts, Atoll first ensures that the selected AFP module is correctly installed and following which Atoll ascertains the capabilities of the AFP module. It is the capabilities of the AFP module which determine which resources you can use the AFP to allocate. a. Under Resources to Allocate, select the check boxes of the resources you want to allocate. The selections you make will depend on the hopping mode of your network: Note: 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 in this case. 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 in this case. 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 in this case. 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.

5. Under Strategies, select the check boxes corresponding to the allocation strategies you want the AFP to use: Azimuth-oriented allocation (Pattern 1/X): The azimuth-oriented allocation strategy consists of allocating a preferred frequency group to the group-constrained subcells. This allocation is aligned with the main azimuth directions. If the frequency groups are correctly configured, (i.e., if X comparably sized groups exist), then this option will give a 1/X pattern assignment Optimisation of the number of TRXs: When subcells have weak traffic loads and at the same time are located in a zone of heavy spectral congestion, there might be an important advantage in the possibility of reducing the number of TRXs to assign. Conversely, for subcells with high traffic loads, the AFP might increase the number of TRXs compared to what is required in order to reduce the blocked traffic. For more information on these allocation strategies, see start here XREF.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

303

Atoll User Manual 6. Under Indicators to allocate, select the check boxes corresponding to the indicators you want the Atoll AFP to allocate: TRX Rank: The AFP can calculate the TRX rank of each TRX. The TRX rank gives the quality of the allocated frequency for each TRX, from the TRX with the lowest AFP cosst to the TRX with the highest TRX cost. Subcell Indicators: AFP cost, congestion, blocking and separation cost can be estimated by the AFP model per pool of subcells (e.g., a BCCH, TCH pool). These indicators are a way to precisely estimate the allocation quality at the subcell level and provide some directions to improve the plan, if necessary.

7. Under AFP Model and Allocations, select the Load all interferers propagating in the focus zone check box if you want the AFP scope to extend 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 299. 8. Click Next. The next page of the AFP dialogue appears (see Figure 6.154). On this page of the AFP dialogue, you can see and 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 290. For more information on the exceptional pairs, see "Defining Exceptional Pairs" on page 242.

Figure 6.153: The second page of the AFP dialogue: separation constraints 9. Click Next. The next page of the AFP dialogue appears (see Figure 6.153). On this page of the AFP dialogue, you can define the global parameters.

Figure 6.154: The third page of the AFP dialogue

304

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 10. Under Allocation of subcells of type, select the check boxes corresponding to the subcells for which resources will be allocated to TRXs. Note: Missing TRXs will not be created for any subcell not selected under Allocation of subcells of type.

11. Under Locking of existing TRXs of type, select the check boxes corresponding to the subcells for which you want the number of TRXs to be locked during allocation. No TRXs will be added or removed from the selected subcells. Note: 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 dialogue of each transmitter.

12. 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: Note: The information could have been entered manually The information could have come from dimensioning The information could have come from a KPI calculation. If the traffic information in the Subcells table is the result of a KPI calculation you must be aware that, during a KPI calculation, Atoll divides the captured traffic by the timeslot capacity of the existing number of TRXs, whereas the AFP requires the traffic to be divided by the timeslot capacity of the required number of TRXs.

Based on default traffic capture results.

13. Click Okay. The AFP validates the parameters you have defined. The AFP dialogue that appears (see Figure 6.155) gives a summary of the validation process as well as any messages displayed in the Event Viewer.

Figure 6.155: The final AFP dialogue 14. Enter a Target Calculation Time in minutes (See "The AFP's Target Calculation Time" on page 302 and "The Atoll AFP Execution Tab" on page 438). 15. If desired, enter a Generator Initialisation. If you set the generator initialisation to "0," the calculations will be random. If you set the generator initialisation to any value other value, the results will be deterministic, i.e., using the same value again will result in the same results with the same document.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

305

Atoll User Manual Note: All AFP calculations are deterministic at the start, even if the generator initialisation is set to "0." The effect of the random seed can only be observed after a certain time (5 to 15% of the target calculation time). If you want to the automatic allocation process to show the effect of random allocation, you must let the AFP calculate until the target calculation time has elapsed.

16. Click Run. The AFP Progress dialogue appears (see Figure 6.156). Note: Read the messages in the Event Viewer carefully before clicking Run. There might be issues that you need to addresss before you can successfully run an AFP.

Figure 6.156: The AFP Progress dialogue For information on the AFP Progress dialogue and on the process of allocating frequencies and resources, see "The AFP Progress Dialogue" on page 306.

6.4.5.5

The AFP Progress Dialogue

When running an AFP, the first step, explained in "Running an Automatic Frequency Allocation" on page 302, is defining the parameters that the AFP will use. When you have finished defining the parameters, and clicked Run on the final dialogue, the AFP begins its calculations and the AFP Progress dialogue The AFP Progress dialogue has the following sections: Progress: Under Progress, you will find information on the current progress of the AFP, with the elapsed time in comparison, the target calculation time, and the number of solutions evaluated to that point. General Information and Interference Matrix Report: Under General Information and Interference Matrix Report, the current status of the AFP process or the interference matrix report is displayed. You can switch the display between general information and the interference matrix report by clicking the button ( ) in the top-right corner of this section. Event Viewer: The Event Viewer displays a description of each event along with the time it occurred. Best Frequency Plan Costs: The Best Frequency Plan Costs section displays the costs and components of the best solution found so far. You can select what information is displayed in the table by clicking the Display Options button. The following options are available: Summed Costs Modifiable Costs Locked Costs

for each component of the cost (total, separation, intermodulation, blocking, additional, taxes, spectrum modification, etc.). Comparison with Initial Plan: In the Comparison with Initial Plan section you 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 Detailed Results list.

306

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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 Results dialogue appears. For information on the Results dialogue, see "The Results of the Automatic Frequency Allocation" on page 307. You can continue the AFP process, if you want, by clicking the Resume button on the Results dialogue.

6.4.5.6

The Results of the Automatic Frequency Allocation

When the AFP process has completed, or when you have stopped the process by clicking the Pause/Stop button, the frequency plan proposed by the AFP is displayed in the Results dialogue (see Figure 6.157). Because the Results dialogue opens in a separate window, you can return to your Atoll document while it is displayed. This allows you to verify your network data while you resolve separation constraint violations and before you commit the automatic frequency allocation. Transmitters located within the focus zone are listed in the results dialogue. If the focus zone is not available, the results are displayed for all the transmitters within the computation zone. The Results dialogue is composed of three tabs: "The Summary Tab" on page 307 "The Allocation Tab" on page 307 "The Subcells Tab" on page 310.

6.4.5.6.1

The Summary Tab

The Summary tab (see Figure 6.157) 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 Progress dialogue (see Figure 6.156).

Figure 6.157: Summary tab of the AFP results dialogue

6.4.5.6.2

The Allocation Tab

The Allocation tab (see Figure 6.158) shows the results of the allocation and provides various editing functionalities for the frequency plan delivered by the AFP. It permits you the removal of unacceptable TRXs.

The results are displayed by transmitter, TRX type, and TRX and are coded by colour: Light blue: The resource is locked and has not been modified. Red: The resource has been modified but there is a separation constraint violation. Green: The resource has been modified respecting separation constraints. Black: The resource has been not modified. Blue: The resource has been created respecting separation constraints. Purple: The resource has been created but there is a separation constraint violation. Brown: The resource has not been modified but there is still a separation constraint violation.

Additionally, in the case the AFP been able to remove some resources such as TRXs with a view to obtain the lowest blocking cost, the initial resource value is displayed but its corresponding line is hatched. For such lines, when the plan is Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

307

Atoll User Manual committed (See "Committing and Saving the Frequency Plan" on page 312), the corresponding resources (e.g. TRXs) are deleted from the TRXs table.

Figure 6.158: Allocation tab of the AFP results dialogue When you move the pointer over a resource in the table, a tooltip displays gives the reason for the status indicated by the colour (see Figure 6.159).

Figure 6.159: Details on the modified resource are given in a tooltip Under Display, for each transmitter (in the Transmitter column), subcell (in the TRX Type column), TRX (in the Index column) combination, Atoll displays the following columns, depending on the resources you selected to allocate (see "Running an Automatic Frequency Allocation" on page 302): 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 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. You can hide the TRX Rank column by clicking the Display Options button and deselecting Display the AFP Indicators. Any separation constraint violations are listed in the Separation column. You can display details about separation constraint violations in the following ways: By right-clicking the separation constraint violation and selecting Separation Constraint Violations from the context menu. A message box appears displaying details about the separation constraint violation (see Figure 6.160). Additionally, you can define the pair currently in violation as an exceptional pair. Since separation constraints between exceptional pairs have more weights than default separation constraints, you will be able to re-run the AFP and force it to try to avoid this violation.

308

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.160: Separation violations The bottom of the Results window displays the messages related to the last solution (which might not be the best solution) as well as potential related allocation problems.

Defining the Display of the Allocation Tab

You can define how the information on the Allocation tab is displayed sorting the contents of the table, by using the context menu, or by selecting an option displayed by clicking the Display Options button. Be default, the content of the table under Display is 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 content 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 quickly display only a selection of data. To filter the contents of the table: 1. Right-click the cell in the table containing the data on which you want to filter the content of the table. The context menu appears. 2. Select one of the following options from the context menu: Filter by Selection: When you select Filter by Selection, all records with the selected value or values are displayed. Filter Excluding Selection: When you select Filter Excluding Selection, all records without the selected value or values are displayed. Advanced Filter: When you select Advanced Filter, the Filter dialogue appears. Using the Filter dialogue, 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 75.

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 appears: You can select one or more of the following columns to appear in the table: Cells Subcells TRXs

You can display the 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 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 Allocated Transmitters Only. You can define how violations are displayed: Display Detailed Constraint Violations: When you select Display detailed constraint violations, the following additional columns are displayed: With the TRX: The TRX with which this separation constraint violation occurs is indicated in the With the TRX column in the form of a button. Clicking the button brings you to that TRX in the table. Co-channel: The probability of collision with the same channel on the TRX indicated in the With the TRX column. Adjacent: The probability of collision with an adjacent channel on the TRX indicated in the With the TRX column.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

309

Atoll User Manual Display Violations Only: When you select Co-Transmitter Violations, Atoll filters out resources which do not have co-transmitter separation violations. Co-transmitter Violations: When you select Co-Transmitter Violations, Atoll filters out resources which do not have co-transmitter separation violations. Co-Site Violations: When you select Co-Site Violations, Atoll filters out resources which do not have cosite separation violations. Neighbour Violations: When you select Neighbour Violations, Atoll filters out resources which do not have neighbour separation violations. Exceptional Pair Violations: When you select Exceptional Pair Violations, Atoll filters out resources which do not have exceptional pair separation violations.

You can select one of the following plans to appear in the table: -

6.4.5.6.3

The Subcells Tab

The Subcells tab (see Figure 6.161) 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 grid indicates the initial and final results. When commiting them, they are assigned to the corresponding subcells. This tab can also indicate the preferred groups assigned to subcells if the AFP has been run with the azimuth-oriented allocation strategy.

Figure 6.161: Subcell tab of the AFP results dialogue

Resolving Separation Constraint Violations

In the Results dialogue, you can resolve the displayed separation constraint violations using the Channel Assignment column. The Channel Assignment column displays whether the value assigned is a new value or the initial value. The Channel Assignment column enables you resolve separation constraint violations by re-assigning the values from the original frequency plan, returning to the AFP-assigned value, or deleting the TRX. To resolve separation constraint violations: Click the entry in the Channel Assignment column corresponding to the TRX where the separation constraint violation occurs and select one of the following: New Value: The value assigned by the AFP process. By default, only new values are displayed in the results window. This option is not available if the value was not changed during the AFP process. Initial Value: The value before running the AFP or after changing the assigned value. Delete the TRX: The TRX will be deleted when you click the Commit button.

When you select one of options in the Channel Assignment column, Atoll updates not only the TRX affected, but also the separation constraint violations of all other TRXs affected by the change. As you modify the current frequency allocation plan, you can display the AFP plan as it appeared before modifications or the initial frequency plan, if there was one. To change the displayed plan: Click the Display Options button and select one of the following: Display the Current Plan: 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.

310

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Display the 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.

You can cancel all the modifications you have made to the current AFP plan. To cancel all the modifications you have to the current AFP plan: Clicking the Actions button and select Reset channel allocations.

You can automatically resolve separation constraint violations by clicking the Actions button and selecting Constraint Violations Resolution. For more information, see "Resolving Separation Constraint Violations Automatically" on page 311.

Resolving Separation Constraint Violations Automatically

You can also resolve the 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 and select Constraint Violations Resolution. The Constraint Violations Resolution dialogue appears (see Figure 6.162). 2. Under TRXs to take into account, select one of the following: 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 that AFP that do not respect the separation constraints.

3. Under Violation types to consider, select the check boxes corresponding to the separation constraint violations that you want Atoll to take into consideration: Co-Transmitters: TRXs on the same transmitter. Co-Sites: TRXs on the same site. Neighbours: TRXs on neighbouring transmitters. Exceptional Pairs: TRXs on transmitters that are part of an exceptional pair.

4. Under Collision Probabilities, select the collision probability you want Atoll to take into consideration: If you want Atoll to take into consideration all co-channel and adjacent channel collision probabilities, select All. If you want Atoll to take into consideration co-channel collision probabilities greater than or equal to a defined value, select If the co-channel probability is >= and enter a value. If you want Atoll to take into consideration co-channel and adjacent collision probabilities greater than or equal to a defined value, select If the co- or adjacent channel probability is >= and enter a value.

5. 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 check box, control channel TRXs (i.e., BCCH TRXs) will be deleted. Apply to other TRXs: If you select this check box, TRXs on non-control channel TRX types (i.e., TCH, TCH_EGPRS or TCH_INNER) will be deleted.

6. Click OK. Atoll deletes the TRXs that are involved in the separation constraint violations and that respond to set criteria.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

311

Atoll User Manual

Figure 6.162: Constraint Violation Resolution

Committing and Saving the Frequency Plan

Once you have made the necessary modifications to the frequency plan, you can commit the frequency plan. To commit the currently displayed frequency plan: 1. Ensure that the currently displayed frequency plan is the one you want to commit by clicking the Display Options button and selecting the desired frequency plan Display the Current Plan: 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 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.

2. Click Commit. You can also export the currently displayed frequency plan. To export the currently displayed frequency plan: 1. Ensure that the currently displayed frequency plan is the one you want to export by clicking the Display Options button and selecting the desired frequency plan: Display the Current Plan: 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 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.

2. Click the Actions button and select Export Results. The Export dialogue appears. 3. Export the frequency plan as explained in "Exporting Tables to Text Files" on page 61. Note: 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.

6.4.5.6.4

AFP-Relevant Parameters in the Network

Many of the parameters used by the AFP are read directly from subcell settings made in the GSM/GPRS/EDGE network. You can modify these parameters globally or for individual transmitters before running the AFP. Other parameters are calculated when you dimension the GSM/GPRS/EDGE network. Before you can use the AFP tool, you need to know the number of required TRXs. You can dimension the network to let Atoll automatically calculate and update the required number of TRXs needed per subcell for each transmitter of the network, or you can enter the information manually. For information on letting Atoll automatically calculate and update the

312

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks required number of TRXs needed per subcell, see "Dimensioning a GSM/GPRS/EDGE Network" on page 266. For information on adding TRXs manually, see "Creating or Modifying a TRX" on page 203. 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 dialogue. The parameters are displayed on 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 404. For information on modifying transmitter properties, see "Creating or Modifying a Transmitter" on page 201. The following are the most important AFP-relevant parameters under Subcells on the TRXs tab of the transmitters Properties dialogue: 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 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). 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 packetswitched 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 dialogue 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 (Synthesized 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 "Synthesized Hopping mode (SFH)." If frequency hopping is not supported, select "Non Hopping." The Hopping Mode is found in the Standard table. Note: 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 "The Atoll AFP Module" on page 425.

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

313

Atoll User Manual 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 dialogue, you can set the weight to be used for the selected transmitter during the AFP: 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. The AFP Weight is found in the Standard table.

If certain resources have already been allocated, on the AFP tab of a transmitters Properties dialogue 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 the Lock Channels and MAIO check box is 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 the Lock HSN check box is selected, the transmitters currently assigned HSN is kept when a new AFP session is started. On the TRXs tab, under Subcell (TRX Groups) Settings, you can lock the HSN for individual subcells assigned to the transmitter. Lock BSIC: When the Lock BSIC check box is selected, the transmitters currently assigned BSIC is kept when a new AFP session is started.

Under Exceptional separation constraints with other transmitters, on the AFP tab of a transmitters Properties dialogue, 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 290.

6.4.5.7

Interactive Frequency Allocation

Atoll has an Interactive Frequency Planning (IFP) tool. This tool allows you to verify the frequency allocation of transmitters one by one, and interactively improve an existing frequency plan by letting you select the most appropriate channels to assign to TRXs. The IFP tool uses an AFP module to calculate the costs associated with the current and modified frequency plans. For more information on the optional Atoll AFP module, see "The Atoll AFP Module" on page 425. Whereas an automatic frequency planning module (AFP) provides the final solution in terms of allocated channels, i.e., the best 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. In Figure 6.163, you can see that the TCH frequency 32 is interfered by a TCH TRX belonging to BRU078. In Figure 6.164, you can see that the candidate replacement channel 19 is better, even if it is also interfered by BRU079_G2. The best candidate is therefore channel 16.

314

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.163: TCH channel 32 interfered by TCH of BRU078_G1

Figure 6.164: Candidate replacement channel 19

6.4.5.8

Allocating Frequencies Interactively

To allocate frequencies interactively using the IFP: 1. Click View > Interactive Frequency Planning Tool. The Interactive Frequency Planning Tool window appears. 2. Select the Channel Allocation and Analysis tab. 3. Select a transmitter from the Transmitter list.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

315

Atoll User Manual

Note:

You can also select a transmitter by clicking its symbol in the map window.

4. Select the TRX type from the TRXs list. 5. Select an AFP module from the AFP Module list. 6. If you want to modify parameters that will influence frequency planning before running the tool, click General Parameters button and select one of the following options from the menu: AFP Module Properties: For information on the options, see "The Atoll AFP Module" on page 425. AFP Parameters: In the AFP Launching Parameters dialogue, 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 interferers propagating in the focus zone 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 "Defining Required Channel Separations" on page 290. Exceptional Pairs: For information on the options, see "Defining Required Channel Separations" on page 290. Intra-Technology Neighbours: For information on the options, see "Planning Neighbours" on page 241.

7. Click Run. 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 Interference Matrices folder on the Data tab of the Explorer window. If the interference matrices in the Interference Matrices folder are inactive or 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 indicate the interference probability. Different information and options are available depending on the hopping mode of the selected transmitters TRXs: Non-hopping mode: The first column displays the number of existing and required TRXs and lists the existing TRXs of the selected type for the transmitter being studied along with the frequency assigned to them and the cost of the allocation. The second column displays the number of candidate channels available, and lists these channels along with the costs for the channels if they were allocated to the selected transmitter. The Filter column lets you select the interference information to be displayed in the fourth column, the Probability column. You can display the High Separation Violations, Separation Violations, Interference Violations, or the Neighbour Violations of the selected transmitter. You can choose more than one of these options by pressing and holding CTRL and clicking each option. The Probability column displays the interference probabilities between the TRX of the selected transmitter and the interfering TRXs using the selected options in the Filter column. Base band hopping mode: The first column displays the number of existing and required TRXs, and lists the existing TRXs of the selected type for the transmitter being studied along with the frequency and MAL assigned to them, and the cost of the allocation. The second column displays the number of candidate channels available, and lists these channels along with the MALs and costs if they were allocated to the selected transmitter. The Filter column lets you select the interference information to be displayed in the fourth column, the Probability column. You can display the High Separation Violations, Separation Violations, Interference Violations, or the Neighbour Violations of the selected transmitter. You can choose more than one of these options by pressing and holding CTRL and clicking each option. The Probability column displays the interference probabilities between the TRX of the selected transmitter and the interfering TRXs using the selected options in the Filter column. Synthesized hopping mode: The first column lists the existing TRXs of the selected transmitter, the frequencies used by these TRXs in SFH mode, the MAIO assigned to each TRX, and the cost of the allocation. The Filter column lets you select the interference information to be displayed in the fourth column, the Probability column. You can display the High Separation Violations, Separation Violations, Interference Violations, or the Neighbour Violations of the selected transmitter. You can choose more than one of these options by pressing and holding CTRL and clicking each option.

316

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks The Probability column displays the interference probabilities between the TRX of the selected transmitter and the interfering TRXs using the selected options in the Filter column. Using the IFP, you can create a new TRX and assign a channel to it, delete an existing TRX, and replace the current channel assigned to an existing TRX. To create a new TRX and assign a channel to it: 1. Select New TRX from the list of TRXs in the first column. 2. Select a channel from the list of candidate channels in the second column. 3. Click Create. A new TRX is created in the selected transmitter with the channel you selected. To delete an existing TRX: 1. Select the TRX that you want to delete from the list of TRXs in the first column. 2. Click Delete. The selected TRX is deleted from the transmitter. To replace the current channel assigned to an existing TRX: 1. Select the TRX to which you want to assign a different channel from the list of TRXs in the first column. 2. Select a channel from the list of candidate channels in the second column. 3. Click Replace. The candidate channel will be assigned to the existing TRX. The changes that you make are taken into account in real time and updated results are displayed.

6.5

Analysing Network Quality

When you are working on a GSM/GPRS/EDGE network, you can analyse the quality of the network using the coverage predictions provided in Atoll. For GSM/GPRS/EDGE networks, Atoll provides both circuit and packet-specific coverage predictions as well as quality indicator studies for both GSM and GPRS/EDGE. In this section, the following are explained: "Evaluating the Quality of a Frequency Plan" on page 317 "Interference Coverage Predictions" on page 320 "Packet-Specific Coverage Predictions" on page 328 "Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction" on page 335 "Studying Interference Between Transmitters" on page 337 "Auditing a GSM/GPRS/EDGE Frequency Plan" on page 338 "Checking Consistency Between Transmitters and Subcells" on page 340 "Displaying the Frequency Allocation" on page 341 "Calculating Key Performance Indicators of a GSM/GPRS/EDGE Network" on page 344

6.5.1

Evaluating the Quality of a Frequency Plan

Creating an AFP-compatible interference study is the most precise and objective way of evaluating the quality of the frequency plan. It is more precise than the AFP cost estimation because it is based on the calculated radio conditions at each point and not on interference matrices. It is also more objective because it does not depend on the AFP module used to create the frequency plan evaluated. When you create an AFP-compatible interference study, you must observe the following rules (for information on defining and calculating an interfered zones coverage prediction, see "Studying Interference Areas" on page 323: Select Interfered Zones as the coverage prediction from the Study Types dialogue. Use the same service area model when calculating the interfered zones coverage prediction that you used when calculating the interference matrices.

For example, if you calculate the interference matrices on the HCS servers with a margin of 4 dB, shadowing, and a cell edge coverage probability of 75% as shown in Figure 6.165, you should use the same settings when creating the interfered zones coverage prediction (see Figure 6.166).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

317

Atoll User Manual

Figure 6.165: Generating interference matrices

Figure 6.166: Defining the interfered zones coverage prediction Do not change the default setting of the interference and coverage definitions (as indicated by the text boxes outlined in green in Figure 6.166). Use the same DTX definition as when running the AFP (as indicated by the text boxes outlined in purple in Figure 6.166). Use the detailed results and the subcell traffic load (as indicated by the text boxes outlined in orange in Figure 6.166).

After defining and running the coverage prediction as explained in "Studying Interference Areas" on page 323, generate a report as explained in ""Displaying a Coverage Prediction Report" on page 235. When the Columns to Be Displayed dialogue appears, select the checkboxes corresponding to the following columns as shown in Figure 6.166: Served load (timeslots weighted by the AFP weight) Served load (timeslots weighted by the half rate traffic ratio).

318

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.167: Defining the report on the interfered zones coverage prediction The resulting report is shown in Figure 6.168.

Figure 6.168: The report on the interfered zones coverage prediction The report displays: the following: 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 in the report. In Figure 6.168, the interfered traffic for channel 44 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 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 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 parenthesis, 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 6.168. 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 6.168 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

319

Atoll User Manual

Figure 6.169: Considerations in frequency planning

6.5.2

Interference Coverage Predictions

The interference coverage predictions described in this section depend on the existence of a frequency plan. If you have not yet allocated frequencies, you must do so before carrying out any of the coverage predictions described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 270. Each of the interference coverage predictions described in this section can be carried out based on a fixed noise value or based on the settings for a particular terminal. For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 419. The following GSM-specific coverage predictions are explained in this section: "Making Quality Studies Based on CI or C(I+N)" on page 320 "Studying Interference Areas" on page 323.

You can also study interference areas by using the Point Analysis window: "Analysing Interference Areas Using a Point Analysis" on page 325 "Example of Analysing Interference Using a Point Analysis" on page 326.

Atoll also enables you to model interference coming from an external project. For more information, see "Modelling InterTechnology Interference" on page 424.

6.5.2.1

Making Quality Studies Based on CI or C(I+N)

In Atoll, you can make quality studies based on CI or C(I+N) levels once channels have been allocated. If you have not yet allocated frequencies, you must 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, and MAIOs" on page 270. The coverage by CI level study enables you to determine CI levels for transmitters sharing either an identical channel or an adjacent channel with other transmitters as a function of the carrier-to-interference ratio. If desired, you can limit the quality study to a specific channel. You can calculate the coverage by CI or by CI + N. "N" is the receiver total noise and is defined as the thermal noise (set to -121 dBm) + noise figure. When you calculate the coverage by CI + N, you can select whether the noise figure used is a fixed value or the noise value set for a selected terminal. If Detailed Results is selected on the Condition tab, the following results are displayed per pixel, depending on the hopping mode set for the subcells covered by the study: 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).

To make a coverage prediction by CI levels: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by C/I Levels and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.170). On the Condition tab, you can define the signals that will be considered for each pixel.

320

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.170: Condition settings for a coverage prediction by C/I levels 7. Under Signal Conditions, set the following parameters: Click the arrow button ( ) and select one of the following thresholds:

Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want 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 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 400). Enter a hand-over margin in the With a Margin text box. 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. You can select the Indoor Coverage check box to add indoor losses.

8. Under Interference Condition, set the following parameters: You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list. You can define a Channel for which Atoll will calculate interference in this quality study. When you define a channel, by default Atoll ignores all TRXs using baseband or synthesised hopping. If you clear the Non Hopping Only check box, all TRXs using the defined channel are considered 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. ) and select one of the following thresholds:

Note:

Click the arrow button ( -

Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for each subcell (including the defined power reduction) as the lower end of the CI range. Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for all subcells as the lower end of the CI range. ) and select one of the following thresholds:

Select either CI or C(I+N). Click the arrow button (

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

321

Atoll User Manual Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for each subcell (including the defined power reduction) as the upper end of the CI range. Specified C/I Threshold: Select Specified C/I Threshold if you want 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.

Notes:

Select whether you want the defined 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.

Note: -

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: 100%: The maximum traffic load (subcells entirely loaded). From subcell table: The subcell traffic load as defined or as calculated during dimensioning.

11. From the Interference Sources list, select whether 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. If you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422. 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.

13. Click the Display tab. For a coverage prediction by CI levels, the Display Type "Value Intervals" based on the Field "CI level (dB)" is selected by default. If you selected "HCS Servers" or "All" from the Server list on the Condition tab, there can be areas where several transmitters experience interference. On these pixels, several CI values are calculated. Therefore, you can base the results displayed on either the Field "Min. CI level (dB)" or "Max. CI level (dB)" as well as the "CI level (dB)" Field. For information on defining display properties, see "Display Properties of Objects" on page 32. 14. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

322

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Note:

By changing the parameters selected on the Condition tab and by selecting different results to be displayed on the Display tab, you can calculate and display information other than that which has been explained in the preceding sections.

6.5.2.2

Studying Interference Areas

In Atoll, you can study interference zones once channels have been allocated. If you have not yet allocated frequencies, you must do so before carrying out the interfered zones study. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 270. You can create an interfered zones study to predict areas where transmitters suffer interference caused by other transmitters using the same channel or an adjacent channel. Atoll calculates the CI level on each pixel where reception conditions are satisfied. Of these, Atoll calculates the coverage for pixels where the calculated CI is lower than the defined upper limit. The pixel is coloured according to the selected attribute of the interfered transmitter attribute. If Detailed Results is selected on the Condition tab, the following results are displayed per pixel, depending on the hopping mode set for the subcells covered by the study: 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).

To make a coverage prediction by interfered zones: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Interfered Zones and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.171). On the Condition tab, you can define the signals that will be considered for each pixel.

Figure 6.171: Condition settings for a coverage prediction by interfered zones 7. Under Signal Conditions, set the following parameters: Click the arrow button ( ) and select one of the following thresholds:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

323

Atoll User Manual Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range.

In Figure 6.170, a Specified Reception 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 400). Enter a hand-over margin in the With a Margin text box. 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. You can select the Indoor Coverage check box to add indoor losses.

8. Under Interference Condition, set the following parameters: You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list. You can define a Channel for which Atoll will calculate interference in this quality study. When you define a channel, by default Atoll ignores all TRXs using baseband or synthesised hopping. If you clear the Non Hopping Only check box, all TRXs using the defined channel are considered 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. ) and select one of the following thresholds:

Note:

Click the arrow button ( -

Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for each subcell (including the defined power reduction) as the lower end of the CI range. Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for all subcells as the lower end of the CI range. ) and select one of the following thresholds:

Select either CI or C(I+N). Click the arrow button ( Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for each subcell (including the defined power reduction) as the upper end of the CI range. Specified C/I Threshold: Select Specified C/I Threshold if you want 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: 100%: The maximum traffic load (subcells entirely loaded). From subcell table: The subcell traffic load as defined or as calculated during dimensioning.

11. 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. You can also select interferences coming from an external project using another technology. For more information, see "Modelling Inter-Technology Interference" on page 662. If you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422. 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. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

324

Chapter 6: GSM/GPRS/EDGE Networks 13. Click the Display tab. For a coverage prediction by interfered zones, the Display Type "Discrete Values" based on the Field "Transmitter" is selected by default. On the Data tab of the Explorer window, the coverage prediction results are arranged by interfered transmitter. You can also define the display to display the quality received on each interfered area: The quality received on each interfered area: Select "Value Intervals" as the Display Type and "C/I Level (dB)" as the Field. On the Data tab of the Explorer window, the coverage prediction results are first arranged by interfered transmitter and then by C/I level.

For information on defining display properties, see "Display Properties of Objects" on page 32. 14. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Notes: By changing the parameters selected on the Condition 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 "Displaying a Coverage Prediction Report" on page 235, you can display a prediction report on the interfered studies indicating the amount of correctly served traffic out of the total traffic covered by the study by selecting the options Served load (Timeslots weighted either by the AFP weight or by the Half rate traffic ratio) after having run 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.

6.5.2.3

Analysing Interference Areas Using a Point Analysis

In Atoll, you can study the interferers of a transmitter using the Point Analysis. If you have not yet allocated frequencies, you must do so before using the Point Analysis to study interferers. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 270. To make a point analysis to study interference areas: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Interference tab. The Interference tab 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: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

325

Atoll User Manual In Synthesised Frequency Hopping Mode, you can study the interference level on either a specific MALMAIO 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 6.172 on page 327 gives an example of the Interference tab. 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: If it uses synthesised frequency hopping mode (reduction due to fractional load) If it uses adjacent channels (reduction due to adjacent channel protection) If the subcell it is modelling is a TRX_INNER subcell (reduction due to lower offset).

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 tooltip along with information on the channel being interfered and the type of interference, i.e., co-channel or adjacent channel interference. If you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422. 5. You can change the following options at the top of the Interference tab: 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. TRXs: Select the subcell type (or ALL) to be analysed. 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. I: Select whether the interference should be calculated from adjacent channels, co-channels, or from both. Interference Method: Select whether the interference is calculated by CI or by C(I+N).

6. Right-click the Interference tab and select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. You can change the following: Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select Signal Level, Path loss, and Total losses from the Result Type list. You can select the Indoor Coverage check box to add indoor losses.

7. Click the Results tab. The Results tab displays the current position and height of the receiver, the clutter class it is situated on, and for each transmitter, its signal level, the total level of interferences (I) over its subcells, the elementary level of interference of each interferer, and the resulting total C/I (or C/I+N). 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. 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 on an arrow, the interference level received from the corresponding transmitter at the receiver location will be displayed in the tooltip along with information on the channel being interfered and the type of interference, i.e., co-channel or adjacent channel. If you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422. 8. You can change the following options at the top of the Results tab: TRXs: Select the subcell type to be analysed. HCS Layer: Select the HCS layer to be analysed. I: Select whether the interference should be calculated from adjacent channels, co-channels, or from both. 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. In addition, if you select the Sort by C/I check box, the transmitters will be sorted from the lowest to the highest C/I. 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.

6.5.2.4

Example of Analysing Interference Using a Point Analysis

When you use the Point Analysis to study the interferers of a transmitter, the Interference tab 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 signal levels from each interferer contributing to total interference. The bars representing the signal level of the transmitter or of the interferers consist of two parts: a solid part which indicates the received

326

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks signal or interference, and an outlined part which indicates the amount of signal or interference reduction. The signal level of the transmitter can be reduced due to subcell power reduction. For each interferer, interference can be reduced: If it uses synthesised frequency hopping mode (reduction due to fractional load) If it uses adjacent channels (reduction due to adjacent channel protection) If the subcell it is modelling is a TRX_INNER subcell (reduction due to lower offset).

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 82%. 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.

Figure 6.172: Point Analysis Tool - Interference tab The transmitters in this example are the following: Site10_3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 540 is assigned to the BCCH TRX. Site14_3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 540 is assigned to the TCH TRX. Site19_2 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 540 is assigned to the TCH TRX. Site12_3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 540 is assigned to the TCH TRX. Site17_1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 541 is assigned to the TCH TRX. Site16_2 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 540 is assigned to the TCH TRX. Site15_1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 539 is assigned to the TCH TRX. Site13_1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 540 is assigned to the BCCH TRX. Non-hopping mode is assigned to the BCCH TRXs of all transmitters. Base-band hopping mode is assigned to the TCH TRXs.

The Point Analysis gives the following results: The signal level of the transmitter Site10_3 is -95.61 dBm and is indicated by a red bar. It would have been -90.12 dB, but was decreased by 5.49 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 (-98.65 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 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. 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. If interference due to intra-technology third-order intermodulation is taken into consideration, Atoll also displays the interference level as a bar and the source in the format "Interferer Name: I3 (first channel, second channel)". At the top of the Interference tab, the name of the most interfered channel on Site10_3 is channel 540 and the C/I received is 3.03 dB. An analysis of the interferers gives the following information: The bars representing Site14_3, Site19_2, Site12_3, Site16_2, and Site13_1 are full. On four out of five transmitters, channel 540 is assigned to the TCH TRX of the transmitter. On the last transmitter, channel 540 is assigned to the BCCH TRX of the transmitter. They are, therefore, co-channel interferers. No power reduction is defined, therefore the interference is not reduced. The bars representing Site17_1 and Site15_1 are partly full. The bars are only partly full because the interference is reduced: on these transmitters, channel 540 is not assigned; channel 541 is assigned to the TCH TRX of Site17_1 and channel 539 is assigned to the TCH TRX of Site15_1. 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 Predictions folder properties). No power reduction is defined for this subcell. If a power reduction of 3 dB

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

327

Atoll User Manual 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.

6.5.3

Packet-Specific Coverage Predictions

The packet-specific coverage predictions described in this section can use an existing frequency plan. If you have not yet allocated frequencies, you can do so before carrying out any of the coverage predictions described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 270. The coverage predictions described in this section can only be made on transmitters that are packet-capable, in other words, GPRS or EDGE-capable transmitters. For information on defining packet capabilities on a transmitter, see "Creating or Modifying a Transmitter" on page 201. Each of the packet-specific coverage predictions described in this section can be carried out based on a fixed noise value or based on the settings for a particular terminal as well as the settings for a particular mobility. For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 419. For information on defining a mobility, see "Modelling GSM/GPRS/EDGE Mobility Types" on page 419. The following packet-specific coverage predictions are explained in this section: "Making a Coverage Prediction by GPRS/EDGE Coding Schemes" on page 328 "Making a Coverage Prediction by Packet Throughput" on page 330 "Making a BLER Coverage Prediction" on page 333

6.5.3.1

Making a Coverage Prediction by GPRS/EDGE Coding Schemes

In Atoll, you can make a coverage prediction of the GPRS/EDGE coding schemes, 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, and MAIOs" on page 270. 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 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 GSM/GPRS/EDGE Terminals" on page 419. 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 radio condition (i.e., C, C and C/I, with or without thermal noise). To make a coverage prediction by GPRS/EDGE coding schemes: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select GPRS/EDGE Coding Schemes and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.173). On the Condition tab, you can define the signals that will be considered for each pixel.

328

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.173: Condition settings for a coverage prediction by GPRS/EDGE coding schemes 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 400). Enter a hand-over margin in the With a Margin text box. 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. You can select the Indoor Coverage check box to add indoor losses.

8. Under Interference Condition, you can define how Atoll will calculate interference for the GPRS/EDGE coding scheme coverage prediction. Note: 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: 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. If you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422.

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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

329

Atoll User Manual 9. Under GPRS/EDGE, set the following parameters: 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.

10. Click the Display tab. For a coverage prediction by coding schemes, the Display Type "Discrete Values" based on the Field "Coding Schemes" is selected by default. If desired, you can base the display in "Value Intervals" the Field "Best Coding Schemes," in which case, Atoll displays the best coding scheme for each pixel. For information on defining display properties, see "Display Properties of Objects" on page 32. 11. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

6.5.3.2

Making a Coverage Prediction by Packet Throughput

In Atoll, you can make a coverage prediction of the packet throughput or quality, 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, and MAIOs" on page 270. You can calculate the following types of studies using the packet throughput and quality prediction: RLC/MAC throughput per timeslot: Based on the coding scheme used on each pixel (see "Making a Coverage Prediction by GPRS/EDGE Coding Schemes" on page 328) and the calculated quality, Atoll extracts the RLC/ MAC throughput as defined in the coding scheme configuration assigned to transmitters. Application throughput per timeslot for a selected service: Using the RLC/MAC throughput and the application throughput parameters (scaling factor and offset) defined for the selected service (see "Creating or Modifying a GSM/GPRS/EDGE Service" on page 418), Atoll evaluates the throughput per timeslot on the application layer. Max 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 and the number of simultaneous carriers (for EDGE evolution terminals) as defined in the terminal properties (see "Creating or Modifying a GSM/GPRS/EDGE Terminal" on page 419). For exemple, 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. User throughput 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 266) 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 coverage prediction of the packet throughput per timeslot 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 GSM/GPRS/EDGE Terminals" on page 419.

330

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To make a coverage prediction by packet throughput per timeslot: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Packet Throughput and Quality and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.174). On the Condition tab, you can define the signals that will be considered for each pixel.

Figure 6.174: Condition settings for a Packet Throughput coverage 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 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 400). Enter a hand-over margin in the With a Margin text box. 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. You can select the Indoor Coverage check box to add indoor losses. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

331

Atoll User Manual

Note:

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: 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. If you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422.

9. Under GPRS/EDGE, set the following parameters: 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 User Throughput, 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 "RLC/ MAC 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: RLC/MAC Throughput/Timeslot: Each layer shows the RLC/MAC throughput/timeslot that a transmitter can carry on one timeslot per pixel. Best RLC/MAC Throughput/Timeslot: The resulting coverage gives the best RLC/MAC throughput/timeslot per pixel from the previous display. Average RLC/MAC Throughput/Timeslot: Gives the average RLC/MAC throughput/timeslot that the transmitter can carry on one timeslot per pixel. If there are different coverage areas for different TRXs, this study will calculate the union of these coverages and display the average values over these coverage areas, whereas the other coverage predictions for RLC/MAC 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. Best Application Throughput/Timeslot: The resulting coverage gives the best application throughput/ timeslot per pixel for a particular service from the previous display. Average Application Throughput/Timeslot: The average application throughput/timeslot that the transmitter can carry on one timeslot per pixel for a particular service. If there are different coverage areas for different TRXs, this study will calculate the union of these coverages and display the average values over these

332

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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. Max Throughput: Each layer shows the throughput that a transmitter can provide to a selected terminal per pixel. Best Max Throughput: The resulting coverage gives the best throughput per pixel from the previous display. Average Max Throughput: Gives the average throughput that the transmitter can provide to a selected terminal per pixel. If there are different coverage areas for different TRXs, this study will calculate the union of these coverages and display the average values over these coverage areas, whereas the other coverage preditctions for throughput perform an intersection over these coverage zones keeping the minimum value of throughput per pixel. User Throughput: Each layer shows the throughput that a transmitter can provide to a user on a pixel, considering load reduction factors. Best User Throughput: The resulting coverage gives the user throughput per pixel from the previous display. Average User Throughput: The average throughput that the transmitter can provide to a user per pixel. If there are different coverage areas for different TRXs, this study 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 "Display Properties of Objects" on page 32. 12. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

6.5.3.3

Making a BLER Coverage Prediction

In Atoll, you can make a coverage prediction of the block error rate (BLER) measured per transmitter, 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, and MAIOs" on page 270. The BLER is determined after Atoll determines which coding scheme is to be selected for a given C or C and CI. When the coding scheme has been determined, 1 - BLER represents the efficiency factor applied to the maximum throughput of the coding scheme to obtain the served throughput. The BLER can be determined for each pixel. You can make a BLER 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 GSM/GPRS/EDGE Terminals" on page 419. To make a BLER coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Packet Throughput and Quality and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.175). On the Condition tab, you can define the signals that will be considered for each pixel.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

333

Atoll User Manual

Figure 6.175: Condition settings for a BLER coverage 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 400). Enter a hand-over margin in the With a Margin text box. 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. You can select the Indoor Coverage check box to add indoor losses. 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 CI for the BLER coverage prediction. Note: 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: 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.

334

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks If you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422. 9. Under GPRS/EDGE, set the following parameters: 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.

10. Click the Display tab. For a BLER coverage prediction, the Display Type "Value Intervals" is selected by default. Select one of the following values from the Field list: 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 "Display Properties of Objects" on page 32. 11. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

6.5.4

Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction

In Atoll, you can make a circuit quality indicator coverage prediction based on the bit error rate (BER), the frame erasure rate (FER), or the mean opinion score (MOS). The circuit quality indicator coverage predictions refer to the codec configuration assigned to a transmitter or, optionally, to a terminal. For information on using codec configuration in transmitters and terminals, see "Using Codec Configurations in Transmitters and Terminals" on page 410. The circuit quality indicator coverage prediction can use an existing frequency plan. If you have not yet allocated frequencies, you can do so before carrying out any of the coverage predictions described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 270. Each of the circuit-specific studies described in this section can be carried out based on a fixed noise value or based on the settings for a particular terminal as well as the settings for a particular mobility. For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 419. For information on defining a mobility, see "Modelling GSM/ GPRS/EDGE Mobility Types" on page 419. The circuit quality indicator coverage prediction displays the areas where the selected circuit quality indicator (BER, FER, or MOS) for the transmitter satisfies the user-defined criteria. The quality indicator is calculated using CN or CN and C(I+N) and the adaptation or quality thresholds defined for the codec configuration on each transmitter. Transmitters that have no codec configuration defined are not taken into consideration in this study. If a transmitter has a codec configuration, Atoll proceeds as follows: 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 each pixel. For a given quality or a given codec mode, lookup tables defined in codec configuration provide the circuit quality indicator (BER, FER, or MOS) displayed as a result.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

335

Atoll User Manual 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. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Circuit Quality Indicators and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 6.176). On the Condition tab, you can define the signals that will be considered for each pixel.

Figure 6.176: Condition settings BLER coverage 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 400). Enter a hand-over margin in the With a Margin text box. 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. You can select the Indoor Coverage check box to add indoor losses. 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. Note: 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:

336

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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: 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. You can also select interferences coming from an external project using another technology. For more information, see "Modelling Inter-Technology Interference" on page 662. If you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422.

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.

10. Click the Display tab. For a circuit quality indicator coverage prediction, the Display Type "Value Intervals" is selected by default. Select one of the following values from the Field list: 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 "Display Properties of Objects" on page 32. 11. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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.

6.5.5

Studying Interference Between Transmitters

In Atoll, you can use the Sector-to-Sector Interference Tool to study the effects of an interfering signal from one transmitter on the signal of any other transmitter within the computation zone. You can restrict the interference to a set threshold or you can base it on a selected coverage prediction. Using a coverage prediction enables you to compare the results of the Sector-to-Sector Interference Tool to the results of the selected coverage prediction. Note: You must have a computation zone defined to use the Sector-to-Sector Interference Tool. For information on creating a computation zone, see "Creating a Computation Zone" on page 223.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

337

Atoll User Manual To display interference between transmitters on the map: 1. Click View > Sector-to-Sector Interference Tool. The Sector-to-Sector Interference Tool window appears. 2. Under Transmitters: Select the transmitter whose signal is interfered from the Victim list or click the Victim button ( the transmitter by clicking it on the map. ) and select ) and

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

respectively).

3. Under Coverage Conditions, select what you are going to base the interference calculation on: Signal Level: Enter a signal threshold. Based on Study: Select the coverage prediction on which you want to base the interference calculation on.

4. Click Calculate. The interference will be displayed on the map if you have selected the Visible check box (see Figure 6.177).

Figure 6.177: The Sector-to-Sector Interference Tool Atoll allows you to display the interference between transmitters in a histogram. To display interference between transmitters in a histogram: 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 Detailed Results 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 copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics Based on Study Conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.

6.5.6

Auditing a GSM/GPRS/EDGE Frequency Plan

When you have assigned frequencies to the TRXs, either manually or automatically, you can make an audit of the frequency plan. The audit allows you to verify the consistency and validity of the following GSM/GPRS/EDGE network parameters: 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.

338

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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: Each transmitter has a single BCCH TRX defined. 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 be 0.

You can configure the frequency plan audit to verify the following points as well: Frequency domains belong to the assigned frequency band. The current frequency plan respects the assigned allocation strategy (free or group-constrained). The allocated resources, the frequency, HSN, or BSIC, belong to the assigned domain. There is consistency between the excluded channels defined at the subcell and the assigned channels. The exceptional separation constraints are respected. No transmitter has the same BSIC-BCCH pair as one of its neighbours. No transmitter has two neighbours with the same BSIC-BCCH pair.

To make a frequency plan audit: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Audit from the context menu. The Frequency Plan Audit dialogue appears. 4. On the General tab, under Loading, select the subcells to be considered: 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 dialogue (see step 8.). 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.

5. 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.

6. 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 dialogue (see step 8.) 7. 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.

8. Click the Separations tab. On the Separations tab, you can, if you wish define or modify separation constraints and exceptional separation constraints: a. Click the Exceptional Pairs button to open the Exceptional Separation Constraints dialogue 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 Exceptional Separation Constraints table. For information on defining exceptional separation constraints, see "Defining Exceptional Frequency Separations" on page 290. b. When you have finished entering exceptional separation constraints, click Close to close the Exceptional Separation Constraints dialogue. 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 290. 9. Click the Detailed Results tab. On the Detailed Results tab, you can select the check boxes of 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

339

Atoll User Manual Additional Warnings: If you select this check box, the audit displays additional detailed warnings. Postpone the Global Summary: If you select this check box, the global summary will not be generated immediately. Instead, the audit results will be displayed immediately and you can generate the global summary at that point.

10. Click OK to start the audit. The Checking Planning Consistency dialogue appears (see Figure 6.178). The results are given in a grid under Display. Under Messages are the detailed results as defined in step 9. If you had selected the Postpone the Global Summary check box in step 9., the Messages area will be empty. You can generate global summary now by clicking the Actions button and selecting Generate the Global Summary.

Figure 6.178: Checking Planning Consistency dialogue The results are listed in a table by transmitter, TRX type, and TRX and are coded by colour. Channels in black present no separation violations. Channels in red present separation violations. Any separation constraint violations are listed in the Separation Violations column. You can display details about separation constraint violations by right-clicking the separation constraint violation and selecting Separation Constraint Violations from the context menu. A message box appears displaying details about the separation constraint violation (see Figure 6.179). You can navigate to the TRX with which the current TRX has a separation violation by clicking the button in the With the TRX column.

Figure 6.179: Separation violations

6.5.7

Checking Consistency Between Transmitters and Subcells

When network data is imported into an Atoll document, inconsistencies can occur between parameters that can defined on the subcell and TRX and parameters that can be defined on the transmitter. You can perform an audit on the consistency of these parameters and have Atoll automatically correct these problems as well. For each transmitter, Atoll checks that: 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.

340

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To make a subcell audit: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > Audit from the context menu. The Subcell Audit dialogue appears. 4. Define the subcell audit: Generate a report in the Event Viewer: Problems grouped by transmitter are displayed in the Events Viewer. Fix incoonsistencies between transmitters and their subcells: Atoll updates parameters of transmitters that are inconsistent with their subcells and TRXs.

5. Click OK.

6.5.8

Displaying the Frequency Allocation

Atoll provides several tools that enable you to view the frequency allocation. You can use these tools to analyse a frequency plan by displaying the overall distribution of channels or channel and BSIC use on the map. You can also search for channels or BSICs. In this section, the following are explained: "Using the Search Tool to Display Channel Reuse" on page 341 "Displaying the Frequency Allocation Using Transmitter Display Settings" on page 342 "Grouping Transmitters by Frequencies" on page 343 "Displaying the Channel Allocation Histogram" on page 343.

6.5.8.1

Using the Search Tool to Display Channel Reuse

In Atoll, you can use the Search Tool to search for BCCH and non-BCCH channels, and BSICs. The Search Tool allows you to view channel and BSIC reuse on the map. The Search Tool has tabs allowing you to find transmitters using a given channel, BSIC or NCC-BCC, or combination of HSN and MAIO. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Channel reuse 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 227. Note: By including the BCCH, BSIC, and channel list of each transmitter in the transmitter label, the search results will be easier to understand. For information on defining the label, see "Defining the Object Type Label" on page 35.

Searching for Channels

You can use the Search Tool to search for a channel. You can search in all channels, in control channels, or in non-control channels. To find a channel using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Channel tab. 3. Enter a Channel. 4. Select from the As list what type of channels you want Atoll to search: All: all channels BCCH: control channels Non-BCCH: non-control channels

5. If you only want the channel entered in the Channel box to be displayed, select the Co-channel Only check box. 6. If you want to view the search results on the map as well as in the form of a report, select the Report check box. 7. Click Search. When you search for All 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 Non-BCCH 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 the co-channel case takes precedence over the colours used for adjacent channels. All other transmitters are displayed as grey lines.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

341

Atoll User Manual If you selected the Co-channel Only check box, transmitters using the same channel are displayed in red; all others, including transmitters with adjacent channels, are displayed as grey lines. If you selected the Report check box, Atoll displays a report of the search results in a text file called SearchReport.txt, which it opens at the end of the search. This file lists all the transmitters using the searched channel (cochannel) and its adjacent channels (adjacent or twice adjacent). To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.

Searching for a Combination of TRX and Subcell Parameters

You can use the Search Tool to search for a combination of TRX and subcell parameters: a channel, BSIC or NCC-BCC, as well as HSN and MAIO. To find a combination of TRX and subcell parameters using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Channel/BSIC/HSN/MAIO tab. 3. Select the parameters on which you want to search: Channel: Select one of the following and enter, if desired, a specific channel number. If you do not enter a channel number, Atoll will search all specified channels according to the other parameters. All: Atoll will search all channels. BCCH: Atoll will only search BCCH channels. Not BCCH: Atoll will only search channels that are not BCCH channels. BSIC: If you select BSIC, enter a value for the BSIC. NCC: If you select NCC, enter a value for the NCC and for the BCC.

BSIC or NCC-BCC: Select one of the following:

HSN: Enter, if desired, an HSN. MAIO: Enter, if desired, a MAIO.

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.

6.5.8.2

Displaying the Frequency Allocation Using Transmitter Display Settings

You can use the display characteristics of transmitters to display frequency allocation-related information on the map. To display frequency allocation-related information on the map: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. You can display the following information per transmitter: 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 tooltip: BCCH: To display the BCCH of a transmitters subcells, select "BCCH" from the Label or Tip Text Field Definition dialogue. BSIC: To display the BSIC of a transmitter, select "BSIC" from the Label or Tip Text Field Definition dialogue. Channels: To display the channels allocated to a transmitter, select "Channels" from the Label or Tip Text Field Definition dialogue. HSN: To display the HSN allocated to a transmitters subcells, select "HSN" from the Label or Tip Text Field Definition dialogue. MAIO: To display the MAIO allocated to a transmitters subcells, select "MAIO" from the Label or Tip Text Field Definition dialogue. Cell type: To display the cell type allocated to a transmitter, select "Cell type" from the Label or Tip Text Field Definition dialogue. 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 dialogue. 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 dialogue. Frequency Band: To display the frequency band assigned to a transmitter, select "Frequency Band" from the Label or Tip Text Field Definition dialogue.

342

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks GPRS/EDGE: To display which transmitters are GPRS/EDGE-capable, select "GPRS/EDGE" from the Label or Tip Text Field Definition dialogue. 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 dialogue. Codec Configuration: To display the codec configuration assigned to a transmitter, select "Codec Configuration" from the Label or Tip Text Field Definition dialogue. Note: 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 "Display Properties of Objects" on page 32.

6.5.8.3

Grouping Transmitters by Frequencies

You can group transmitters on the Data tab of the Explorer window by their channel list or by their frequency band, or by both. To group transmitters by channels or by frequency band: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group By. The Group dialogue appears. 5. Under Available Fields, select the parameter you want to group transmitters by: 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 will be grouped. . The selected parameter is removed from the list of parameters on which the transmitters

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 b. Select a parameter and click to move it up to the desired position. to move it down to the desired position.

9. Click OK to save your changes and close the Group dialogue.

6.5.8.4

Displaying the Channel Allocation Histogram

Atoll has a frequency distribution analysis tool. You can access this tool by selecting Frequency Distribution from the Transmitter > Frequency Plan context menu. The frequency distribution analysis tool gives you a three-column table with: The ARFCN The number of TRXs in which the ARFCN appears Its relative load.

The relative 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 size) 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 299. The frequency load distribution can be displayed as a histogram by clicking the Histogram button. The histogram is similar to the one in the AFP Progress dialogue.

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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

343

Atoll User Manual 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 second, forth, sixed, 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. Click the Data tab in the Explorer window. 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 dialogue and export the Channel Use Statistics table contents as a TXT, CSV, or XLS file. For information on using the Export dialogue, see "Exporting Tables to Text Files" on page 61. Histogram: Click the Histogram button to display the Distribution Histogram dialogue. 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 Detailed Results list. In the Distribution Histogram dialogue, 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.

6.5.9

Calculating Key Performance Indicators of a GSM/GPRS/ EDGE Network

Atoll allows the user to calculate and analyse key performance indicators (KPI), such as the reduction factor, the blocking probability, and the delay, that are currently defined for the network. This allows you to verify how well the network satisfies basic performance criteria. To run a KPI calculation: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Traffic > KPIs from the context menu. The Dimensioning/KPIs dialogue appears (see Figure 6.180).

Figure 6.180: The KPI Calculation dialogue: The Dimensioning/KPI dialogue

344

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 4. Under Dimensioning Parameters, select the dimensioning model that will be used for the KPI calculation from the Model list. You can access the parameters of the selected dimensioning model by clicking the Browse button ( ).

5. Under Traffic (Circuit and Packet Demand), select if the KPIs computation has to be based on the traffic demand computed in the default traffic capture of from the actual values (circuit and packet demands) in the subcells table. If you have selected "From subcell table", you will have to 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 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 Services (%), enter the percentage of each service used in the map. For each type of service (circuit or packet switched, assuming packet is made of max bit rate and constant bit rate packet services), the percentages must equal 100.

6. Click Calculate to run the KPI calculation. The output of the calculation appears in the KPI Calculation dialogue under Results. You can select which columns to display by clicking the Displayed Columns button and selecting or clearing the check box of the columns. The following results are given for each transmitter in the Transmitter column: 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 circuit-switched-service users within the coverage area of the transmitter. Note: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

345

Atoll User Manual At present, Atoll only models circuit calls using 1 timeslot per connection; this parameter is for forward compatibility. 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 traffic demand source 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.

7. Click Commit to assign the load and the effective rate of traffic overflow to the subcells. Note: 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.

6.6

Optimising Network Parameters Using the ACP

Atoll Automatic Cell Planning (ACP) enables radio engineers designing GSM networks to automatically calculate the optimal network settings in terms of network coverage and capacity. Atoll ACP can also be used in co-planning projects where GSM networks must both be taken into consideration when calculating the optimal network settings. Coverage maps are used for the optimisation process, however, traffic maps can be used for weighting network load distribution. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and transmission power. ACP can also be used during the initial planning stage of a GSM network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only takes transmitters into account in optimisations but also any repeaters and remote antennas. ACP also enables you to select to select which sites can be added or removed to improve existing or new networks.

346

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.6.1

The ACP Module and Atoll

Atoll ACP can be used either with existing networks or with networks in the initial planning phases. With existing networks, it is most efficient to focus on tuning the parameters that can be easily changed remotely, for example: Antenna electrical tilt: ACP adjusts the electrical tilt by selecting the best antenna from the antenna group assigned to this transmitter. Transmission power: The transmission power is set within a defined minimum and maximum value.

When optimising a network that is still in the planning phase, Atoll ACP can calculate how the network can be improved by: Selecting the antenna type for each transmitter: ACP selects the best antenna from the antenna group assigned to this transmitter. Changing the antenna azimuth: ACP sets the antenna azimuth using a defined range on either side of the currently defined azimuth. Changing the mechanical tilt of the antenna: ACP sets the mechanical tilt using a defined range on either side of the currently defined mechanical tilt. Changing the height of the antenna: ACP sets the optimal antenna height using a defined range on either side of the currently defined antenna height. Selecting sites: ACP adds or removes sites that you have indicated as candidates for addition or removal in order to improve existing or new networks.

In this section, the following are explained: "Using Zones with ACP" on page 347 "Using Traffic Maps with ACP" on page 348 "Shadowing Margin and Indoor Coverage" on page 348 "ACP and Antenna Masking" on page 348.

6.6.1.1

Using Zones with ACP

ACP uses different zones during the optimisation process for different purposes. ACP uses the computation zone to define the area of the network to be optimised. ACP always takes the entire computation zone into consideration, even if the zone selected for optimisation is the focus zone; the sites and transmitters included in the computation zone and not in the focus zone are still taken into consideration when calculating signal, interference, and best server status. ACP enables you to define different targets and different weights for each zone: for the computation zone, for the focus zone, for the hot spot zones, and for each clutter classes. In this section, the following are explained: "Using the Computation Zone and the Focus Zone" on page 347 "Using Hot Spots" on page 347 "Using the Filtering Zone" on page 347.

6.6.1.1.1

Using the Computation Zone and the Focus Zone

Atoll ACP optimises the settings for the sites in either the computation zone or the focus zone. If you have both a computation zone and a focus zone defined, you can select which zone will be used for the optimisation process. If there is no focus or computation zone, the ACP optimises the settings for the cells in a rectangle including all cells in the network. Atoll ACP allows you to define different targets for the computation zone and the focus zone, as well as for the hot spot zones. You can also define different weights for each zone. Note: It is recommended to define a computation zone. ACP uses the computation zone as the area in which the quality figures are calculated and improved during optimisation. Additionally, the zone defined by ACP might take into account areas outside of actual traffic boundaries.

6.6.1.1.2

Using Hot Spots

Atoll ACP also allows you to use hot spot zones, enabling you to specify different quality targets for each hot spot zone and display final results per zone. You can also define different weights for each zone. You can use the hot spot zones defined in the Atoll document, import ArcView SHP files to create hot spot zones, or you can create hot spot zones based on clutter classes.

6.6.1.1.3

Using the Filtering Zone

If there is a filtering zone defined, Atoll ACP will optimise all currently defined and active cells selected by the filtering zone.

Note:

ACP automatically considers all the cells that have an effect on the computation or focus zone, and ignores the rest (for example, cells that are too far away to have an impact on the selected cells). It is nonetheless recommended to use a filtering zone to speed up initial data extraction from the Atoll document.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

347

Atoll User Manual

6.6.1.2

Using Traffic Maps with ACP

Atoll ACP can use traffic maps to determine the traffic density on each pixel. The traffic density is used to weight each of the quality figures according to traffic and to put more emphasis on high traffic areas. You can apply the imported traffic density files to either or both of the quality indicators.

Figure 6.181: ACP traffic parameters Note: For the moment, traffic profiles are only used to evaluate the traffic weighting to apply to each pixel (by adding the load-scaled traffic distribution on each traffic profile). This information will also be used in the future to better manage cell load.

6.6.1.3

Shadowing Margin and Indoor Coverage

Atoll ACP enables you to take indoor coverage and a shadowing margin into consideration. When indoor coverage is taken into consideration, all pixels marked as indoors have an additional indoor loss added to total losses. The indoor loss is defined per clutter class. By default, ACP considers all pixels to be indoors, but Atoll ACP allows you to specify which clutter class should be considered as indoors and which not. When the shadowing margin is taken into consideration, the defined shadowing margin is taken into consideration in the calculation of the received useful signal power and interfering signal power. For more information on how shadowing and macro-diversity gains are calculated, see the Technical Reference Guide. Note: You can set ACP to not take macro-diversity gains into consideration by setting the appropriate option in the acp.ini file. You will need to update the corresponding parameters in the atoll.ini file as well. For information on modifying the atoll.ini file, see the Administrator Guide.

6.6.1.4

ACP and Antenna Masking

When ACP performs any type of antenna reconfiguration, it must determine how attenuation to the path loss changes when the antenna is modified. ACP determines changes to path loss attenuation using antenna masking. Depending on the propagation model used to calculate the path loss matrices, ACP supports the following antenna masking methods: Natively supported propagation models: ACP calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. Because ACP is using the same propagation model as was used to calculate the original path loss matrices, the results are consistent and accurate. For this reason, using natively supported propagation models is the preferred method. For more information, see "Natively Supported Propagation Models" on page 348. ACPs default propagation model: If the propagation model used to calculate the original path loss matrices is not supported by ACP, ACP can use its own default propagation model. Because the ACP default propagation model is not the same as the one used to calculate the original path loss matrices, accuracy cannot be guaranteed. ACPs default propagation model is similar to Atolls Standard Propagation Model and should deliver acceptable results for any macro-type propagation model. For more information, see "ACPs Default Propagation Model" on page 349. Precalculated path loss matrices: ACP allows you to designate all propagation models in the project which are not supported by the native method. ACP will then prerecalculated path loss matrices for these propagation models. For more information, see "Precalculated Path Loss Matrices" on page 349. Note: Site selection (without reconfiguration) is made independently of the method used to determine changes to path loss attenuation.

6.6.1.4.1

Natively Supported Propagation Models

During antenna optimisation, ACP must calculate how the attenuation to the path loss changes when the antenna is modified, i.e., when the antenna type, tile, or azimuth is modified. When ACP uses natively supported propagation models, it calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. The unmasking and remasking operations are strongly dependent on the propagation model that was used to calculate the path losses, especially to: Find the horizontal and vertical emission angles between a transmitter and the receiving pixel. The angles depend strongly on the radial method used to account for the height profile between the transmitter and receiver.

348

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Find the correct antenna gain for a given set of horizontal and vertical emission angles. The gain is usually based on a 3-D interpolation of the 2-D patterns and can be model-dependent.

How ACP calculates attenuation depends on the propagation model used by Atoll to generate the path loss. The propagation model parameters which affect processing are automatically extracted by ACP. ACP supports the propagation models commonly used in Atoll. For other propagation models, ACP uses a default model similar to Cost-Hata, however, you can always set ACP to use another propagation model, the SPM for example, if you feel it would give more accurate results. The raster data needed by ACP depends on the propagation model that Atoll used to generate the path loss.

Propagation Model
All Atoll Hata-based propagation models (Cost-Hata, Okumura-Hata, ITU, etc.)

Raster Data Required

DEM file DEM file Clutter Height file (optional) Clutter file (optional) DEM file

Atoll Standard Propagation Model

All other models.

Because the path loss information is not stored in the ACP optimisation setup but in the Atoll document where it is accessed by ACP, changes in the Atoll document can cause inconsistency between the optimisation results and the actual state of the network, for example, when transmitters are modified in the document. ACP deals with this situation by locking optimisation results. An optimisation can not be rerun on locked results if the path loss data are not consistent with the internal state of the optimisation. The results are automatically unlocked if the state of the Atoll document again becomes consistent with the ACP optimisation. The same mechanism applies when settings produced by an optimisation run are committed to the Atoll network. The results are locked after being committed and will be unlocked if the network is rolled back to the state on which the optimisation was based.

6.6.1.4.2

ACPs Default Propagation Model

ACP has an internal default propagation model that can be used if the propagation model used to calculate the original path loss matrices is not supported by ACP. Because the ACP default propagation model is not the same as the one used to calculate the original path loss matrices, accuracy can not be guaranteed, although it should deliver acceptable results for any macro-type propagation model. ACP offers a few parameters that enable you to improve the accuracy of the default propagation model: Use Clutter Height: By selecting Use Clutter Height, ACP will take into consideration clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on Top of Clutter: If the receiver is on top of the clutter, for example, if receivers are located on top of buildings, you can select Receiver on Top of Clutter. The receiver height will then be sum of the clutter height and the receiver height. Use Radial Method: You can select the Use Radial Method check box if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

These parameters can be set individually for each propagation model for which ACP will use the default propagation method. These parameters belong to the advanced parameters; to modify them, you must first make the advanced parameters visible. For information on making the advanced parameters visible, "Configuring the Default Settings" on page 350.

6.6.1.4.3

Precalculated Path Loss Matrices

After the ACP setup has been created, ACP calculates the path loss matrices necessary (i.e., for sites that are being optimised and do not use natively supported propagation models or the ACP's internal model) while the optimisation is loading. ACP does not calculate all path loss matrices for all possible combinations, for example, five possible changes in electrical tilt and five possible changes in azimuth, i.e., 25 path loss matrices to be calculated. ACP only calculates the path loss matrices for the most common optmisation changes, for example, changes to the electrical tilt. By pre-calculating only the most common changes, ACP reduces the number of path loss changes to be calculated and reduces the calculation time. While the optimisation is running, ACP uses the pre-calculated path loss matrices. If a change is made to a transmitter that was not taken into the consideration when the path loss matrices were calculated, ACP recalculates the path loss matrix for that change only. The end result are considerable savings in both time and computer resources. For information on natively supported propagation models, see "Natively Supported Propagation Models" on page 348. 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, it is often similar enough to a supported propagation model so that ACP can still use it. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

349

Atoll User Manual 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. Notes: Precalculated path loss matrices can only be used when optimising the antenna type and azimuth. Optimising the mechanical tilt is not currently supported.

6.6.2

Configuring the ACP Module

You can change the default settings of the Atoll ACP module so that selected options are the default settings each time you run ACP. Additionally, you can base the default ACP settings on some or all of the settings of a given Atoll optimisation. In this section, the following are explained: "Configuring the Default Settings" on page 350 "Defining the Antenna Masking Method" on page 351 "Saving Settings to a User Configuration File" on page 352.

6.6.2.1

Configuring the Default Settings

To configure the default settings of the ACP module: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Default Settings tab. On the Default Settings tab, you can define the configuration files that contain the default settings. These settings are applied every time you run an optimisation project. Under Loading Default Settings: Global Configuration: The Global Configuration is the configuration file set up by the administrator. This configuration provides the same default settings to everyone on the network. For information on the ACP global configuration file, see the Administrator Manual. User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings you want to be the default settings for the ACP module.

5. Click the User Preferences tab. On the User Preferences tab (see Figure 6.182), you can define settings that are saved to the acp.ini configuration file found in the ACP installation folder. These settings will be applied every time you run a new configuration.

Figure 6.182: Setting ACP user preferences Under Setup Preferences: You can define the following settings: Enable automatic setting from custom table field (antennas, sites): Select the Enable automatic setting from custom table field (antennas, sites) check box if you want ACP to use the custom columns in the SITES and ANTENNAS tables. If you want ACP to use the custom columns, you must set the appropriate options in the acp.ini file. For more information on the acp.ini file, see the Administrator Manual. Show advanced optimisation settings: Select the Show advanced optimisation settings check box if you want the ACP to display the Advanced tab when you define an optimisation setup. When the Advanced tab is available, you can set a few additional options related to services, terminals, clutter, and propagation models. Calculation setting: Adjust the slider to define whether you want ACP to provide its results more quickly, at the expense of precision, or whether you want ACP to provide more accurate results, at the expense of speed.

350

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks By selecting a higher speed, you will cause ACP to reduce the number of cells monitored for each pixel, some of which might only create a bit of interference at first, but which could possibly create significantly more interference after antenna parameters are changed during the optimisation process. Selecting a higher precision avoids this problem at the expense of more time and computer resources. Under Result Preferences: You can define the following setting for report maps: Default map transparency: Define the default map transparency with the slider.

6. Click the Private Directory tab. On the Private Directory tab (see Figure 6.183), you can define the directory to be used by the ACP to store precalculated path loss matrices as well as the path loss matrices for antenna height optimisation.

Figure 6.183: Defining the directory for path loss matrices 7. Enter the name of the directory or click the the Browse button ( 8. Click OK to save your changes. When the propagation model used is not one natively supported by ACP, for example, complex ray-tracing propagation models, ACP can use precalculated path loss matrices to calculate attenuation. For more information, see "Defining the Antenna Masking Method" on page 351. ) to navigate to the directory.

6.6.2.2

Defining the Antenna Masking Method

You can define how Atoll ACP calculates path loss matrices, using either Atolls propagation models, ACPs internal propagation model, or precalculated path loss matrices. These parameters will be applied to all new and duplicated setups. To define how ACP calculates path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Antenna Masking Model tab (see Figure 6.184).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

351

Atoll User Manual

Figure 6.184: The Antenna Masking Model tab 5. If you are using a propagation model that ACP does not natively support, select the Enable precalculated path loss matrices check box. You will then be able to select the propagation model for which ACP will pre-calculate path attentuation. 6. Under Propagation Models, select the check boxes in each column to define how ACP will interact with that propagation model. Not all parameters are available for all propagation models:

Tip:

By default, all available propagation models are displayed. By selecting the Show only used propagation models check box, ACP will only display the propagation models that are actually used.

Antenna masking method: The Antenna masking method indicates whether ACP can use this propagation model natively, or whether ACP uses its own default method. The information in this column can not be edited. Use precalculated path loss: Select the check box in the Use precalculated path loss column corresponding to every propagation model that is not supported natively by ACP or that can not be replaced using ACPs internal default method. Use clutter height: Select the check box in the Use clutter height column if you want ACP to take clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on top of clutter: Select the check box in the Receiver on top of clutter column if you want the receiver height to be sum of the clutter height and the receiver height. This option can be used, for example, to model receivers on top of buildings. Use radial method: Select the check box in the Use radial method column if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

7. Click OK.

6.6.2.3

Saving Settings to a User Configuration File

To save the settings to a user configuration file: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Default Settings tab. On the Default Settings tab, you can define the configuration files that contain the default settings. These settings are applied every time you run an optimisation project. Under Loading Default Settings: Global Configuration: The Global Configuration indicates the configuration file set up by the administrator. This configuration provides the same default settings to everyone on the network. For information on the ACP global configuration file, see the Administrator Manual. User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings you want to be the default settings for the ACP module.

352

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 5. Click the Save Configuration File button under Saving Default Settings to save settings to a user configuration file. Note: The settings you save to a user configuration file are from an ACP optimisation from the current Atoll document. If you have not yet used ACP for an optimisation in the current document, the Save Configuration File button is not available.

When you click the Save Configuration File button, the Save Configuration File dialogue opens (see Figure 6.185).

Figure 6.185: The Save Configuration File dialogue 6. From the Save setting based on setup list, select the ACP setup on whose parameters you want to base the user configuration file. 7. Click the Browse button ( file. ) next to To configuration file to select where you will save the user configuration

8. Under Sections to save, select the check boxes of the types of parameters whose settings you want to save to the user configuration file. 9. Click Save.

6.6.3

Optimising Cell Planning with the ACP

Optimising cell planning with the Atoll ACP consists of defining the parameters that will be used during the optimisation process and then running the process. Each optimisation, with its parameters and results, is stored in a Setup folder in the ACP - Automatic Cell Planning folder on the Data tab of the Explorer window. In this section, the following are explained: "Creating an Optimisation Setup" on page 353 "Defining Optimisation Parameters" on page 354.

6.6.3.1

Creating an Optimisation Setup

In ACP, you can create an optimisation setup either by creating and running a new one, or by duplicating or opening an existing optimisation, editing the parameters, and then running it. In this section, the following are explained: "Creating a New Optimisation Setup" on page 353 "Running an Existing Optimisation Setup" on page 354 "Duplicating an Existing Optimisation Setup" on page 354.

Creating a New Optimisation Setup

To create a new optimisation setup: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 354. 4. After defining the optimisation setup:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

353

Atoll User Manual Click the Run button to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 375. Click the Create Setup button to save the defined optimisation. For information on running the optimisation, see "Running an Existing Optimisation Setup" on page 354.

Running an Existing Optimisation Setup

To run an existing optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

3. Right-click the optimisation you want to run. The context menu appears. Select Run from the context menu to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 375. Select Properties from the context menu to view or modify the parameters of the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 354.

Duplicating an Existing Optimisation Setup

To duplicate an existing optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

3. Right-click the setup you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The ACP Duplicate Options dialogue appears. 5. Under Data Synchronisation Option, select one of the following: Minimal: The duplicated ACP setup will have only the data that was changed by the ACP during optimisation. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid. Complete: The duplicated ACP setup will have have all the data from the ACP optimisation.

6. Run the existing optimisation setup as described in "Running an Existing Optimisation Setup" on page 354.

6.6.3.2

Defining Optimisation Parameters

In Atoll ACP, when you create a new optimisation setup, you must first define all the parameters. You can also modify the parameters of an existing optimisation setup before running it. Creating a new optimisation setup is explained in "Creating a New Optimisation Setup" on page 353. Running an existing optimisation is explained in "Running an Existing Optimisation Setup" on page 354. The optimisation parameters are grouped onto specific tabs of the dialogue. The parameters are the same whether you create a new optimisation setup or whether you modify the parameters of an existing one. In this section, the following parameters are explained: "Setting Optimisation Parameters" on page 354 "Setting Objective Parameters" on page 357 "Setting Traffic Parameters for Non-uniform Traffic" on page 359 "Setting Network Reconfiguration Parameters" on page 360 "Defining Site Selection Parameters" on page 364 "Defining Antenna Groups" on page 368 "Adding Comments to the Optimisation Setup" on page 372 "Setting Advanced Parameters" on page 372.

6.6.3.2.1

Setting Optimisation Parameters

The Optimisation tab allows you to define the various parameters related to the optimisation algorithm. To set the optimisation parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Optimisation tab (see Figure 6.186).

354

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.186: The Optimisation tab 3. Define the following: Number of Iterations: Set the number of iterations for the optimisation algorithm. ACP calculates a suggested number of iterations by multiplying the total number of parameters to optimise (i.e., cell pilot power, antennas, azimuth, mechanical tilt, sites subject to selection) by two. You can accept the number of iterations, or set your own value. Often one-half or one-quarter of the suggested number is sufficient for ACP to find the optimal configuration. Resolution (m): Specify the resolution for the optimisation. Each criterion will be evaluated on each of these pixels. The total number of pixels and the average number per site is indicated. This parameter has a large influence on the accuracy and speed of the optimisation process. You should either set a resolution that is consistent with the path loss and raster data in the Atoll document, or you should set a resolution that will result in between 300 and 3000 positions per site.

4. Under Setup, you can set the following optimisation-related objectives and parameters: a. In the pane on the left-hand side, click Layers. Under Layers (see Figure 6.186 on page 355), you can define the following for each layer to be optimised: Use: You can select which layers are to be considered in the optimisation process by selecting their check box in the Use column. The signals and interference of the transmitters and sites in the selected layers will be taken into consideration during the optimisation process. If the transmitters and sites in the selected layers are within the area to be optimised (the computation zone or the focus zone, as selected under Zones on the Optimisation tab), these transmitters and cells will be optimised. Selecting layers to be taken into consideration is most useful when you want to take the signal and interference of several layers into consideration, but only want to optimise one of the layers. Selecting the layers here ensures that ACP will take them into consideration. Transmitters and sites in layers which are not selected are treated by 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. Note: If a transmitter on one selected layer that is optimised is linked with a transmitter on another selected layer that is not optimised, the second transmitter will still appear on the Reconfiguration tab and any changes to the first transmitter will be applied to the linked transmitter as well. Name: You can change the name of the layer by clicking it and entering a new name. Weight: You can change the weight assigned to the layer during optimisation by clicking it and entering a new weight. ACP will put more emphasis on increasing the quality of the layer with the greater weight. For example, if one layer has a weight of "2" and another layer has a weight of "1," ACP will consider increasing the quality of the first layer by 1% as equivalent to increasing the quality of the second layer by 2%. Reconfiguration: If you want the layer to be taken into consideration for reconfiguration, you can select the check box in the Reconfiguration column. Site Selection: If you want the layer to be taken into consideration for site selection, you can select the check box in the Site Selection column.

The following columns give information about the layer; they can not be edited: Forsk 2010 Technology: The technology (GSM in this case) used by the layer. Unauthorized reproduction or distribution of this document is prohibited

355

Atoll User Manual Freq. Band/Carrier: The frequency band and carrier (if applicable) used by the layer. Nb Tx/Cell: The number of transmitters in the layer.

You can merge layers if you want to define identical objectives for both layers (for more information on objectives, see "Setting Objective Parameters" on page 357). To merge layers: i. Hold CTRL and click the layers you want to merge.

ii. Click the Merge button. b. In the pane on the left-hand side, click Zones. Under Zones (see Figure 6.188), you can define how the zones will be used during optimisation. The zones are used to define geographical objectives and weighting. The zones are taken into consideration in the following order: the hot spot zones in their defined order, the focus zone, and finally the computation zone. Filtering Zones: Select the Computation Zone check box to lock sectors outside the computation zone and the Focus Zone check box to lock sectors outside the focus zone. If there is no focus zone in the project to be optimised, the computation zone is automatically selected. Hot Spots: For each new hot spot, enter a Name in the row marked with the New Row icon ( click the Browse button ( ) and ) to open the Zone Definition dialogue. You can import an ArcView SHP file

by selecting From file and clicking the the Browse button ( ). Or, you can use an existing hot spot zone in the Atoll document by selecting From hot spot and selecting the hot spot zone from the list. Or, you can create a hot spot zone composed of all areas in the reconfiguration zones that are included in one or more clutter class by selecing From clutter classes and selecting the check box corresponding to the clutter class or classes you want to study.

Figure 6.187: The Zone Definition dialogue You can change the order in which the hot spots will be taken into consideration, by clicking the layers number in the Order column and then clicking the Up button ( ) or the Down button ( ).

Figure 6.188: Configuring zones on the Optimisation tab c. In the pane on the left-hand side, click Cost Control. Under Cost Control (see Figure 6.189), you can define how the costs will be calculated for each optimisation option. ACP will use the defined costs to calculate the optimisations that are the most cost-effective. You can select three types of cost control: No cost control: If you select No cost control, ACP will not take cost into consideration when optimising the network.

356

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Maximum cost: If you select Maximum cost, you can enter a maximum cost not to be exceeded and define the costs under Cost Setting. Quality/Cost trade-off: If you select Quality/Cost trade-off, ACP will find a compromise between cost and quality. You can use the slider to define whether ACP should put more emphasis on quality (Low) or cost (High).

Figure 6.189: Configuring costs on the Optimisation tab In the Reconfiguration Cost section, under Cost Setting, define the individual costs for each reconfiguration option. If reconfiguring an option can only be done at the physical location of the transmitter, select the check box in the Site Visit column. The cost will be increased by the defined Site Visit value. The site visit cost is incurred only once per site, independently of the number of reconfigurations that might be made to the same site, including sites supporting more than one technology. In the Site Selection Cost section, under Cost Setting, define the individual costs for each site selection option.

6.6.3.2.2

Setting Objective Parameters

The Objectives tab allows you to define the various parameters related to the objectives of the optimisation. ACP allows you to set different objectives for each layer selected in the Use column under Layers on the Optimisation tab. The objectives vary according to the technology used by the network being optimised. The options are given here. To set the objective parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Objectives tab (see Figure 6.190).

Figure 6.190: The Optimisation tab

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

357

Atoll User Manual 3. Under Criteria, you can set the following objective-related objectives and parameters. a. Under Objective, click BCCH Coverage to define the BCCH coverage parameters. Computation zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for BCCH coverage in computation zone. Under Area Coverage, you can define the percentage by which the current BCCH coverage should be improved (Improve current coverage (+-)) or a target BCCH coverage (Target coverage (%)). Focus zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for BCCH coverage in focus zone. Hot Spot zone: Every hot spot zone defined under Zones on the Optimisation tab will appear under BCCH coverage. For each hot spot zone, select the check box in the Use column if you want to define a Minimum threshold (dBm) for RSCP coverage in the hot spot zone.

b. Under Objective, click Parameters under BCCH Coverage to define how ACP will calculate BCCH coverage. From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate BCCH coverage, or you can select Manual Configuration and define the settings yourself. Important: If you want to use a coverage prediction, the coverage prediction must have already been calculated. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own maps. However, if you have saved the display options of an ACP map as default, or if you are using a configuration file for ACP, these defined ranges and colours will be used as the default, overriding the settings in the selected coverage prediction. For information on setting ACP map display options as the default, see "Changing the Display Properties of ACP Maps" on page 387. For information on saving a configuration file, see "Configuring the Default Settings" on page 350. If you selected Manual Configuration from the Base prediction settings on list, define the following options: Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell edge coverage probability. When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied. You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced Parameters" on page 372.

c. Under Objective, click Cell Dominance to define the cell dominance parameters. Enter the Number of allowed servers and the Overlap margin.

d. If you want to define the coverage to be respected while meeting this BCCH objective, select the check box at the bottom of the tab (see Figure 6.191) and select one of the following options: Minimum area coverage: Select Minimum area coverage and define the minimum coverage as a percentage. Keep current coverage within: Select Keep current coverage within and define the range to be respected.

Figure 6.191: Defining the coverage area e. Under Criteria, click Weighting to set the importance of the objectives.

358

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.192: Setting weighting options for GSM i. Under Objective Weighting, move the slider to set the relative importance of BCCH coverage and cell dominance. You can set meeting one objective as more important than meeting the other, or you can set meeting only the EcIo or RSCP objective as necessary.

ii. Under Zone weighting, define the weight given to the computation zone, the focus zone, and any hot spot zone. With zone weighting, ACP adds an extra weight to all the pixels of a zone. Because one pixel can belong to several zones (for example, a pixel can be inside both the focus zone and the computation zone and in a hot spot zone, if there is one), the weight applied to that pixel is the weight of the zone with the highest priority: the hot spot zone, if it exists, then the focus zone, finally the computation zone. Important: It is important to remember that, if every zone is assigned the same weight, the optimisation is made as if no weight is assigned to any zone. Defining a weight of "0" for a zone means that that zone will not be taken into consideration when trying to reach the set objectives. Zone weighting is used to focus optimisation on the appropriate areas. The assigned weights are used to weight the traffic parameters selected on the Traffic tab, unless the optimisation is based on uniform traffic. For information on the selected traffic parameters, see "Setting Traffic Parameters for Non-uniform Traffic" on page 359. However, if no traffic maps are available or if the optimisation is based on uniform traffic, zone weighting can be used to ensure that ACP prioritises the optimisation of areas of high traffic. With multiple layers, you might have a layer that is restricted geographically (for example, the GSM 900 layer might only be available in rural areas). Because ACP always measures the quality target over the entire computation zone, such a situation would lead to a measurement of poor quality in the urban areas, where there are no GSM 900 transmitters. By defining a weight of "0" outside of the rural area for this layer, you can restrict the measurement of coverage only to the part of the layer with GSM 900 transmitters. This way, the global target (90% of coverage for instance) is measured in a meaningful way.

6.6.3.2.3

Setting Traffic Parameters for Non-uniform Traffic

By default, the traffic is assumed to be uniform within the computation zone. The Traffic tab enables you to select traffic maps in the Atoll document to define non-uniform traffic. The traffic maps describe the distribution of users in the network, along with their characteristics (i.e., services, terminals, and mobility types). Traffic maps can used to weight the quality figures measured on each pixel by using the traffic density on that pixel. You can use traffic maps to weight quality figures. For example, you can optimise RSCP coverage based only on area (defined on the Optimisation tab as explained in "Setting Optimisation Parameters" on page 354) while optimising EcIo coverage using traffic distribution. When using traffic maps, network quality is always optimised using traffic weighting. ACP supports all traffic maps used by Atoll. To set the traffic parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Traffic tab (see Figure 6.193).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

359

Atoll User Manual

Figure 6.193: Defining non-uniform traffic using the Traffic tab 3. Under Traffic Generated From, select one of the following methods for defining non-uniform traffic: Maps based on traffic densities: If you select Maps based on traffic densities, you can define the traffic weighting and traffic profiles. Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of Cell Dominance or BCCH coverage or both. The weighting applied is the weighting defined on the Objectives tab. Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Terminal, select a Traffic Density File by clicking the Browse button ( ), and define a Weight.

Following traffic maps: If you select Following traffic maps, you can select the maps that will be used to generate traffic and define the resolution of the extracted traffic and the traffic weighting. Under Following traffic maps, select the maps that will be used to generate traffic. Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of Cell Dominance or BCCH coverage or both. The weighting applied is the weighting defined on the Objectives tab. Under Traffic Profiles, the traffic profiles will be displayed after ACP has extracted them from the selected traffic maps.

4. If you want to view the traffic profiles without running the optimisation setup, click Create Setup. ACP will then create the traffic profiles based on the traffic maps selected and the traffic parameters defined.

6.6.3.2.4

Setting Network Reconfiguration Parameters

The Reconfiguration tab allows you to select the GSM TRXs for which the transmission power will be reconfigured and the transmitters for which the antenna, azimuth, height, or tilt will be reconfigured. The Reconfiguration tab also allows you to select which sites can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly select sites for reconfiguration. For information on site selection, see "Defining Site Selection Parameters" on page 364. Atoll allows you to export the reconfiguration parameters, modify them in an external application and then reimport them into the Reconfiguration tab. In this section, the following are explained: "Setting GSM TRX Reconfiguration Parameters" on page 360 "Setting Transmitter Reconfiguration Parameters" on page 361 "Linking Transmitters in Multi-layer Networks" on page 363 "Importing Network Reconfiguration Parameters" on page 364.

Setting GSM TRX Reconfiguration Parameters

To set the GSM TRX reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the GSM TRX tab (see Figure 6.195).

360

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.194: GSM TRX reconfiguration options 3. 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. 4. Define the power settings for each TRX. Use: Select the Use check box corresponding to the cell to include it in the optimisation of the transmission power. Current: The current transmission power for the TRX. Min. and Max.: Set a minimum and maximum power to be respected during the optimisation process. Note: If you selected the Power max/min as offset check box, you will set the Min. Offset and Max. Offset for each TRX.

Step (dB): Set a Step in dB that ACP should use with attempting to find the optimal transmission power.

You can make the same changes to several cells by making the change for one item, selecting the others starting from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 59. You can select the transmitters to which the reconfiguration options are going to be applied using the Advanced section of the Reconfiguration tab. For more information, see "Selecting Sites for Reconfiguration" on page 367. You can sort the contents of any column by right-clicking the column and selecting Sort Ascending or Sort Descending from the context menu. Caution: Transmitters that have been filtered out, either by zone or by clearing their check box in the table, will not be optimised but are still present in the network and, therefore, continue to generate interference.

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. For information on importing network reconfiguration options, see "Importing Network Reconfiguration Parameters" on page 364.

Setting Transmitter Reconfiguration Parameters

To set the transmitter reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Reconfiguration tab (see Figure 6.195).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

361

Atoll User Manual

Figure 6.195: Transmitter reconfiguration options 3. Select the parameters that will be optimised: Antenna type: Select the Antenna type check box for ACP to adjust the antenna type by selecting the best antenna from the antenna group assigned to each selected transmitter. Electrical tilt: Select the Electrical tilt check box for ACP to select the best electrical tilt from the antenna group assigned to each selected transmitter within the defined range. Note: When ACP selects the best antenna type, it will also chose the best electrical tilt from the antenna group even if it is not optimising the electrical tilt. However, because no range is defined, ACP will select the best electrical tilt from all available.

Azimuth: Select the Azimuth check box for ACP to set the antenna azimuth using a defined range on either side of the currently defined azimuth. Note: By default, ACP optimises the antenna azimuth of each sector of a site individually. However, you might want to retain the same inter-sector angle separation. If this is the case, you can select the Azimuth check box corresponding to that site under Lock Site on the Sites tab of the Reconfiguration tab.

Mechanical tilt: Select the Mechanical tilt check box for ACP to set the mechanical tilt within the defined range and in the defined number of steps. Height: Select the Height check box for ACP to set the antenna height within the defined range and in the defined number of steps. Note: By default, ACP optimises the height of all antennas of a site identically. In other words, if ACP optimises the antenna of one sector by raising it 1 m., it will also raise the antennas of all other sectors by the same amount, in order to respect the distance between all antennas on the transmitter mast. However, in might not be necessary to maintain this distance, in which case you might want to optimise the height of each antenna of a site individually. f this is the case, you can clear the Height check box corresponding to that site under Lock Site on the Sites tab of the Reconfiguration tab.

The table displays, for each parameter selected, both the current settings for each cell in the selected zone and the currently defined optimisation parameters. Note: If you want ACP to display more information on each transmitter, you can select the Show Advanced Grid check box. ACP will then display, for each transmitter, the antenna masking method, the propagation model used, the transmitter height, and the name and status of the site the transmitter is located on. The propagation model displayed is extracted from the Atoll document but can be changed if the propagation model is not recognised by ACP (for more information, see "ACP and Antenna Masking" on page 348).

362

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 4. Define the settings to be optimised for each cell. If are optimising the antenna azimuth, you can enter a single value in the Variation column, to define a range on either side of the current azimuth, or you can enter a minimum and maximum value separated by a semi-colon in the format "-min;max", (for example, "-20;40") in the Variation column for an asymmetric antenna. You can make the same changes to several cells by making the change for one item, selecting the others starting from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 59.

Linking Transmitters in Multi-layer Networks

When you are optimising transmitters in multi-layer environments, ACP automatically links transmitters in the same location but in different layers to ensure that it applies the same reconfiguration to them. ACP links them not only by location, but also by azimuth, mechanical tilt, and antenna height. If ACP does not automatically link two transmitters which should be linked, it is normally because there is too large a difference in one of the parameters of the two transmitters, for example, a few degrees in azimuth, one degree in mechanical tilt, or one meter difference in antenna height. If two transmitters should be linked but were not, you can manually link them. Note: If the site of one of the linked transmitters has either its antenna heights or azimuths locked, i.e., if changes made to one sector of the site are made to all sectors on that site, then corresponding changes will be made to the other linked transmitter. For more information on locking antenna heights or azimuths, see "Setting Transmitter Reconfiguration Parameters" on page 361.

To link transmitters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the Transmitters tab. 3. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear. 4. Under Advanced, click the Multi-layer Management tab. On the Multi-layer Management tab, you can link transmitters (see Figure 6.196).

Figure 6.196: Multi-layer management To link transmitters in the same location but on different layers: a. Hold CTRL and click the first transmitter in the table above and then the second transmitter. The Link button on the Multi-layer Management tab is now available. b. Click the Link button. The two transmitters are now linked and ACP will apply the same reconfiguration to them both. To unlink linked transmitters: a. Select the transmitters in the table The Unlink button on the Multi-layer Management tab is now available. b. Click the Unlink button. The transmitters are no longer linked. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

363

Atoll User Manual To unlink all linked transmitters: Click the Unlink All button. ACP resets all linked transmitters.

To automatically all transmitters in the same location but on different layers: Click the Auto Link button. ACP links all transmitters that have the same position, azimuth and mechanical tilt.

Importing Network Reconfiguration Parameters

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. To import reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the desired tab. 3. Right-click the table and select Export as Text from the context menu. The Save As dialogue appears. 4. Enter a name in the File name box and click Save. The file will be saved as a tab-delimited text file. 5. Open the text file in another application, for example, in a spreadsheet application, and make the modifications desired. 6. Save the file as a text file and return to Atoll. 7. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear. 8. Under Advanced, click the Import Facility tab. 9. Click the Import from File button. The Open dialogue appears. 10. Browse to the file and click Open. The Import Data dialogue appears (see Figure 6.197).

Figure 6.197: Importing site data into the Reconfiguration tab 11. Under Format Parameters, enter the number of the first row with data in the First Imported Row box, select the data Separator, and select the Decimal Symbol used in the file. 12. If you want only the cells in the imported list to be used on the Reconfiguration tab, select the Use Only Cells in List check box. The Use check box will be cleared for all cells that are not in the imported file and they will not be affected by reconfiguration options. 13. In the table, ensure that the column names from the imported file (the Source file) match the column names on the Reconfiguration tab (Destination). You can change the Destination column by clicking the column name and selecting the name from the list. Note: Any values in the imported file for current values can not be imported.

14. Click the Import button to import the file and replace the settings in the Reconfiguration tab.

6.6.3.2.5

Defining Site Selection Parameters

The Reconfiguration tab allows you to select which sites can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly select sites for reconfiguration.

364

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks In this section, the following are explained: "Selecting Sites for Addition or Removal" on page 365 "Creating Candidate Sites" on page 366 "Selecting Sites for Reconfiguration" on page 367.

Selecting Sites for Addition or Removal

You can use the Reconfiguration tab to select the sites that will be added or removed to improve existing or new networks. To set site selection parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab (see Figure 6.198).

Figure 6.198: Site selection 3. Select the Current Site Selection check box to enable site selection. You can then define how sites will be added or removed. 4. In the table, define how each site will be treated during site selection: a. Select the Locked check box for each site that is not to be affected by site selection.

Tip:

If you have many sites that you do not want to be affected by site selection, you can select and lock them with the Advanced section. For more information on the options in the Advanced section, see "Selecting Sites for Reconfiguration" on page 367.

b. Select the Status for each site that is not locked: Important: Only active sites are loaded by ACP. If you want inactive sites to be taken into account during site selection, you must set them as active first in Atoll. When you commit the results of the ACP run, all sites and sectors disabled by the ACP will be set to inactive in Atoll. Existing: An "Existing" site is considered as being active in the initial network. ACP will remove an existing site if the Site Removable check box has been checked and if removing the site will improve network quality. If the Sectors Removable check box has been checked, one or more sectors might be removed if removing them will improve network quality. Candidate: A "Candidate" site is considered as being inactive in the initial network. ACP will add the site during the optimisation process if adding the site will improve network quality. If the Sectors Removable check box has been checked, only one or more sectors might be added if adding them will improve network quality. You can define candidate sites by clicking the New Candidate Setup button. For more information on defining candidate sites, see "Creating Candidate Sites" on page 366. c. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

365

Atoll User Manual d. Select the Site Removable check box for each site that can be removed to improve network quality. e. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group. Note: If a site group has no sites belonging to it, it is automatically deleted.

You can create a new group for candidate sites if desired. To create a group: i. Under Group, click the field and select New from the list. The New Site Group dialogue appears (see Figure 6.199).

ii. Enter a Group Name and define the minimum and maximum number of sites from this group (from 0 to 1000) that must be respected by ACP during optimisation (Minimum Site Occurrence and Maximum Site Occurrence, respectively). If there is no minimum or maximum that ACP must respect, leave the field blank. iii. Click OK to create the group and return to the Site Selection tab.

Figure 6.199: Creating a new site group f. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality.

g. Select the Site Removable check box for each site that can be removed to improve network quality. h. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group. Note: If a site group has no sites belonging to it, it is automatically deleted.

You can create a new group for candidate sites if desired. To create a group:

Creating Candidate Sites

The ACP enables you to create a list of candidate sites that can be added to the network to improve quality. For each candidate, you can specify both the location and the station template the candidate site would be based on if the ACP adds it to the network. As well, the ACP can optimise candidate sites when they are added to the network. During optimisation, the ACP will choose first from the sites defined as candidates on the Sites tab and then from the list of candidate sites. To create or edit candidate sites: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab. 3. On the Sites tab, click the New Candidate Setup button. The New Candidate Setup dialogue appears (see Figure 6.200).

366

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.200: New Candidate Setup dialogue 4. Under Zone Configuration, define, if desired, how candidate sites will be treated for each zone: Zone: Select the zone (computation, focus, or hot spot zone defined on the Optimisation tab) from the list. The ACP will add the candidate site according to the quality objectives defined on the Optimisation tab. Default Station Template: Select the station template that any candidate site the ACP adds in the selected zone will be based on. Note: The ACP can optimise each candidate site based on a template. You can set the optimisation parameters for each template by clicking the Template Reconfiguration button. For information on the options, see "Setting Transmitter Reconfiguration Parameters" on page 361.

Default Group: Select the group that the candidate site will belong to by default. Radio Layer: If there is more than one radio layer, select the radio layer the candidate site will be added to.

5. Under New Candidate List, define the individual candidate sites. For each candidate site set the following: Name: Enter a name for the candidate site. Location: Click the Browse button ( ) to define the location of the candidate site. You can define the location either as a set of co-ordinates or you can select an existing site from a list. Station Template: Select the station template the candidate site will be based on. This selection overrides the selection made under Zone Configuration. Group: Select the group the candidate site will belong to. This selection overrides the selection made under Zone Configuration. Height: The 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 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. Radio Layer: Select the radio layer the candidate site will be added to. This selection overrides the selection made under Zone Configuration.

6. If desired, select the Try to use multi-band antenna when possible check box. The ACP will attempt to use linked transmitters on candidate sites if possible. 7. Click the Action button to update the list of new candidates by selecting one of the following options: Clear List: Select Clear List to delete all current entries in the New Candidate List. Import from File: Select Import from File to import a list of candidate sites, defined as XY coordinates. Import from Current Sites Defined as Location Only: Select Import from Current Sites Defined as Location Only to import as candidate sites sites in the current document that have no transmitters. The sites imported are those in the reconfiguration zone(s) selected on the Optimisation tab. The defined reconfiguration zone(s) is displayed at the top of the Reconfiguration tab as well. Update Candidate Height from Clutter Height: Select Update Candidate Height from Clutter Height to define the height of all candidate sites for each clutter class.

Selecting Sites for Reconfiguration

You can use the Advanced area of the Reconfiguration tab to select sites. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on page 360. To select sites: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

367

Atoll User Manual 3. Select the Site Selection check box. 4. Click Advanced to display the Advanced area (see Figure 6.201).

Figure 6.201: The Advanced section 5. Select the Global Change tab. 6. Select the sites: For entire table: Select For entire table if you want to select all sites in the table. 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 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. Note: This option is only available in co-planning projects with more than one technology.

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. Note: If you want to lock the selected sites, you can select the Set "Locked" check box and click Apply. The locked sites will not be affected by the site addition or removal options.

6.6.3.2.6

Defining Antenna Groups

You can use the Antenna tab to define antenna groups according to their physical characteristics, as well as grouping patterns according to their antenna pattern and defining multi-band antennas. The antenna groups are necessary to apply the antenna type or electrical tilt reconfiguration options defined on the Reconfiguration tab. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on page 360. 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. In this section, the following are explained: "Creating and Grouping Antennas by Pattern" on page 369 "Grouping Antennas Automatically" on page 370 "Defining Multi-band Antennas" on page 370 "Creating Antenna Groups" on page 371.

368

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Creating and Grouping Antennas by Pattern

Atoll enables you to create physical antennas by grouping several instances of antennas by their pattern. By setting an option in the ACP.ini file, you can also optimise the additional electrical downtilt (AEDT) of antennas. When you have set this option, you can select which antennas for which you will optimise the AEDT and the range of values that Atoll can chose from during the optimisation process. For information on setting options in the ACP.ini file, see the Administrator Manual. To group antennas by their pattern: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 6.202). The Antenna tab displays all antennas in the Antenna Pattern Table and the groups under Physical Antenna.

Figure 6.202: Antenna tab 3. Click the New button to create a new group under Physical Antenna. You can change the name of the new group or of any group by right-clicking the group name twice under Physical Antenna, selecting Rename from the context menu, and entering the new name. You can delete one group by selecting it under Physical Antenna and clicking the Delete button. You can delete all groups by clicking the Delete All button. 4. Assign antennas to a group to create physical antennas or to associate antenna patterns to define a radiation diagramme of a group of antennas with several variations of electrical tilt: a. Select the group under Physical Antenna. b. Select the antenna under Antenna Pattern Table and click the right arrow between the columns ( ) to assign it to the selected group. Antennas under Antenna Pattern Table that have been assigned to a group are indicated with an icon ( ). You can assign the same antenna to more than one group. You can remove an antenna from a group by selecting it in the group under Physical Antenna and clicking the left arrow between the columns ( Note: ).

When you have grouped the antennas, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antennas will then be grouped automatically according to this definition.

5. If you are also optimising additional electrical downtilt, select the check box in the Use AEDT column corresponding to each antenna for which you want to optimise the additional electrical downtilt and define the limits Atoll must respect by entering values in the Min. AEDT and Max. AEDT for each antenna to be optimised.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

369

Atoll User Manual

Figure 6.203: The Antenna Pattern Table with AEDT enabled

Grouping Antennas Automatically

You can group antennas automatically using a regular expression, or "regex." The regular expression is retained from one Atoll session to the next. Therefore, once you have set the regular expression for the given antenna naming convention, you will not have to set again for the next Atoll session. The default regex pattern is overwritten when you change it. You can return to the default regular expression by clearing the text box and clicking OK. You can change the default regular expression by editing the appropriate entry in the ACP.ini file. For more information on the options available in the ACP.ini file, see the Administrator Manual. Important: It is recommended to identify both the antenna type and the electrical tilt in the antenna name in Atoll and to separate the antenna type and electrical tilt with a special character, for example, "_". This will make it easier to group antenna groups automatically using a regular expression. To group antenna automatically: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Antennna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 6.202 on page 369). 3. Under Automatic Creation, enter a regular expression, or "regex," in the text box.

Tip:

Clicking the tooltip button ( expressions.

) displays a tooltip with an explanation of common regular

4. Click the Build from expression button to create antenna groups according to the defined regular expression. Note: When you have created the antenna groups, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antenna groups are then automatically created according to this definition.

Defining Multi-band Antennas

When you have grouped antennas according to their physical characteristics as explained in "Creating and Grouping Antennas by Pattern" on page 369 and "Grouping Antennas Automatically" on page 370, they are displayed on the Radome tab of the Antenna tab, grouped according to their frequency band. You can merge these groups to create groups of antennas that are multi-band antennas. To define multi-band antennas: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Radome tab (see Figure 6.204 on page 371).

370

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.204: Creating multi-band antennas 3. Create multi-band antennas by merging two or more antenna groups: a. Select two or more antenna groups by holding CTRL and clicking the antenna groups in the Radome Table. b. Click the Merge button. The antenna groups are now merged and will appear on the Antenna Groups tab. You can break the merged antenna groups up by selecting them in the Radome Table and clicking the Unmerge button, or by clicking Unmerge All. If you click Unmerge All, all merged antenna groups will be broken up. 4. Under Automatic Creation, enter a regular expression, or "regex," in the text box.

Creating Antenna Groups

ACP creates antenna groups based on common their frequency band, but you can create antenna groups based on other common characteristics. The antenna groups are used especially to chose between a directive antenna (of 35 degrees) and a less directive one (of 65 degrees). However, in most circumstances, one antenna group corresponds to one antenna radome. To group antennas: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Antenna Groups tab (see Figure 6.205 on page 372). On the Antenna Groups tab, there is already one group called "Default" in the Antenna Groups pane of the tab. The "Default" group is created automatically by ACP and contains all the antenna patterns available for a given frequency.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

371

Atoll User Manual

Figure 6.205: Creating antenna groups 3. Click the New button to create a new group under Antenna Groups. You can change the name of the new group or of any group by right-clicking the group name twice under Antenna Groups, selecting Rename from the context menu, and entering the new name. You can delete one group by selecting it under Antenna Groups and clicking the Delete button. You can delete all groups by clicking the Delete All button. 4. Assign antennas to groups according to their physical characteristics: a. Select the group under Antenna Groups. b. Select the antenna under Radome Table and click the right arrow between the columns ( ) to assign it to the selected group. Antennas under Radome Table that have been assigned to a group are indicated with an icon ( ). You can assign the same antenna to more than one group. You can remove an antenna from a group by selecting it in the group under Antenna Groups and clicking the left arrow between the columns ( Note: ).

When you have created the antenna groups, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antenna groups are then automatically created according to this definition.

6.6.3.2.7

Adding Comments to the Optimisation Setup

You can enter comments about the current optimisation setup on the Comments tab. To add comments: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Comments tab and add your comments.

6.6.3.2.8

Setting Advanced Parameters

The Advanced tab displays the traffic parameters that ACP uses to optimise the Atoll project. You can use the Advanced tab to modify this Atoll data. The Advanced tab is not displayed by default. For information on displaying the advanced parameters, see "Configuring the Default Settings" on page 350. To set advanced parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 353. 2. Click the Advanced tab. 3. In the left column, click the Expand button ( ) to expand the Parameters folder.

372

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 4. In the Parameters folder, select Services. In the Services section, the service-related parameters of the Atoll document are displayed. 5. In the Parameters folder, select Terminals. In the Terminals section, the terminal-related parameters of the Atoll document are displayed. In a co-planning document, there will be a Terminals folder for each technology. 6. Under Terminals, define the Noise Factor for each terminal. 7. In the Parameters folder, select Clutter Classes. In the Clutter Classes section, the clutter-related parameters of the Atoll document that affect optimisation are displayed. 8. Under Clutter Classes, you can set the following parameters for each clutter class: Height: You can set the Height for each clutter class. Indoor Loss (dB): You can set the Indoor Loss (dB) for each clutter class. The indoor loss is used to calculate shadowing losses on the path loss, as related to the cell edge coverage probability. Model Standard Deviation (dB): You can set the Model Standard Deviation (dB) for each clutter class. The model standard deviation is used to calculate shadowing losses on the path loss, as related to the cell edge coverage probability. C/I Standard Deviation (dB): You can set the Ec/Io Standard Deviation (dB) for each clutter class. The CI standard deviation is used to calculate shadowing losses on the C/I values, as related to the cell edge coverage probability. Additional Diversity Gain (DL) (dB): You can set an additionnal transmission diversity gain for each clutter class. This additional gain is added to the 3 dB gain in case diversity is set at the subcell level. Is Indoor: You can define the clutter class as being inside by selecting the Is Indoor check box. You can set default values for all clutter classes for each of these parameters except for height.

Note:

6.6.4

Running an Optimisation Setup

When you have finished defining the optimisation parameters as described in "Defining Optimisation Parameters" on page 354, you can run the optimisation setup, either immediately by clicking the Run button. You can also save the defined optimisation setup by clicking the Create Setup button and then running the optimisation at a later point. To run a saved optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 3. Right-click the setup folder that you want to run in the ACP - Automatic Cell Planning folder. The context menu appears. 4. Select Run from the context menu. The optimisation setup runs. As the optimisation setup runs, ACP displays the current status of the process (see Figure 6.206) allowing you to observe the progress. You can pause the optimisation if you desire or stop the optimisation early. The Optimisation dialogue has three tabs: Graphs: The Graphs tab displays a graph with the iterations on the X axis and the optimisation objectives (BCCH, cell dominance, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 6.206). The values displayed are indicated with a legend. Changes: The Changes tab displays in a graph indicating the quantity of changes made for each reconfiguration parameter selected during setup. The values displayed are indicated with a legend. Quality Maps: The Quality Maps tab displays coverage quality maps for BCCH and overlapping gain. The maps display the computation zone with the network improvement performed to that point. If you based this optimisation on a coverage prediction (see "Setting Objective Parameters" on page 357), the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default (see "Changing the Display Properties of ACP Maps" on page 387) or by using a configuration file (see "Configuring the Default Settings" on page 350).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

373

Atoll User Manual

Figure 6.206: The network coverage improvement graphs and maps When the optimisation has finished, the results are stored in the optimisation folder on the Data tab of the Explorer window. By default, Atoll calls the optimisation folder a "Setup" folder. Each setup folder contains one or more optimisation processes. Each optimisation process folder contains the results of that optimisation. For information on viewing optimisation results, see "Viewing Optimisation Results" on page 375.

Figure 6.207: An optimisation run in the Explorer window Note: You can perform an optimisation on a network that has already been optimised. After running the first optimisation and committing the results, you can create and run a second optimisation, with different parameters on the optimised network.

6.6.5

Working with Optimisations in the Explorer Window

Atoll offers you several options for working with the optimisation that you can access using the context menu on the Data tab of the Explorer window. To work with the optimisation: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 6.208).

374

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.208: Options available in the context menu 5. Select one of the following from the context menu: Properties: Selecting Properties from the context menu opens the optimisations Properties dialogue. You can modify all of the optimisation parameters except for the selection of traffic maps (for information on the optimisation parameters, see "Defining Optimisation Parameters" on page 354). If you want to base an optimisation on different traffic maps, you must create a new optimisation (for information on creating a new optimisation, see "Creating an Optimisation Setup" on page 353). Run: Selecting Run runs the optimisation setup. The results will be contained in a new optimisation folder in the setup folder. Caution: If you have changed some data in Atoll, for example, if you added transmitters or change some of the transmitter settings, the data that optimisation results are based on might differ from the current Atoll data. If you run a optimisation based on settings made before the changes, it will not take the changed data into consideration. ACP normally detects changes in the Atoll document data and can lock a group if it is impossible to run an optimisation that is coherent with existing data. ACP can lock a group if, for example, when you commit optimisation results after the path losses have been recalculated and are no longer consistent with the data used to run the optimisation. When this happens you will either have to: Create a new optimisation as explained in "Creating a New Optimisation Setup" on page 353. Duplicate an existing optimisation which will create a new optimisation with the same configuration but with updated parameters. Roll back the previously committed parameters as explained in "The Commit Tab" on page 382.

Delete: Selecting Delete deletes the defined optimisation setup and any results. Storing optimisation results and the group configuration increase the size of the Atoll file. Deleting unused setups in the ACP - Automatic Cell Planning folder will decrease the size of the Atoll file.

Load Configuration: Selecting Load Configuration displays the Open dialogue. You can then select a PRJ file based on the settings of a different optimisation. When you load a configuration based on a different Atoll document, only the settings that are not specific to that document are loaded. Save Configuration: Selecting Save Configuration displays the Save As dialogue. You can then save the optimisation settings in a PRJ file. You can then use this PRJ file to quickly configure an optimisation.

Tip:

Saving a configuration is a quick way to save the settings you have made in an external file. you can then easily create new configurations using these same settings as a basis without having to recreate them.

Duplicate: Selecting Duplicate displays the ACP Duplicate Options dialogue. You can then duplicate the either the ACP-generated data of selected optimisation setup or all of the data of the setup. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid.

6.6.6

Viewing Optimisation Results

Once you have run the calibrated optimisation as explained in "Running an Optimisation Setup" on page 373, the results are stored in the optimisation folder on the Data tab of the Explorer window. You can view the results in the optimisations Properties dialogue or in the map window. In this section, the following are explained: "Viewing Optimisation Results in the Properties Dialogue" on page 376 "Viewing Optimisation Results in the Map Window" on page 382 "Viewing Optimisation Results Using the Histogram" on page 388.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

375

Atoll User Manual

6.6.6.1

Viewing Optimisation Results in the Properties Dialogue

You can view the results of the optimisation run in its Properties dialogue in the ACP - Automatic Cell Planning folder. To view the results of the optimisation in its Properties dialogue: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view.

4. Right-click the optimisation. The context menu appears. 5. Select Properties from the context menu. The optimisations Properties dialogue appears. The optimisation results are on individual tabs of the Properties dialogue (with an extra tab, the General tab, that allows you to change the name of the optimisation results): Statistics: The Statistics tab displays a synthesised view of the optimisation results of the quality figures (BCCH and cell dominance). For more information on the Statistics tab, see "The Statistics Tab" on page 376. Sectors: The Sectors tab displays a table with the reconfigured cells in green, sites and sectors which have been added or removed, and BCCH and cell dominance per cell before and after optimisation. For more information on the Statistics tab, see "The Sectors Tab" on page 377. Graph: The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (BCCH, cell dominance, and global cost, if you have selected to take cost into consideration) on the Y axis. The values displayed are indicated with a legend. For more information on the Graph tab, see "The Graph Tab" on page 379. Quality: The Quality tab displays the computation zone with coverage quality maps for BCCH before and after optimisation. For more information on the Quality tab, see "The Quality Tab" on page 380. Change Details: The Change Details tab enables you to analyse the improvement caused by each reconfiguration option. For more information on the Change Details tab, see "The Change Details Tab" on page 381. Commit: The Commit tab enables you to commit the set of selected changes. For more information on the Commit tab, see "The Commit Tab" on page 382.

6.6.6.1.1

The Statistics Tab

The Statistics tab displays a synthesized view of the optimisation results of the quality figures (BCCH quality and cell dominance).

Figure 6.209: The Statistics tab For the BCCH coverage quality and cell dominance, both the initial and final figures are given, as well as the absolute improvement. These figures are given both for the computation zone and the focus zone. If you defined weights for each zone on the Objectives tab of the dialogue used to define the optimisation (see "Setting Objective Parameters" on page 357), ACP indicates that the results are weighted. You can see more detailed information by clicking the links (see Figure 6.210): Show Change Statistics: The change statistics showing the reconfiguration and site selection statistics. Show Detailed Hot Spot/Clutter Results: The detailed quality figures on each hot spot and by each clutter class.

376

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Show Input: The input settings of this optimisation.

Figure 6.210: The Statistics tab - detailed information You can export the results by clicking the Export button. The Save As dialogue that appears allows you to select the format in which you want to save the results: XLS, TXT, HTML, or XML.

6.6.6.1.2

The Sectors Tab

The Sectors tab displays a table with all the cells in the network with the following information: Cells which have been reconfigured are displayed in green (i.e., if they have had their antenna type, azimuth, or mechanical tilt reconfigured). Sites and sectors which have been added or removed. The BCCH coverage quality and cell dominance before and after optimisation. The quality figures are measured on the best server area of each cell. Antenna type, azimuth, and mechanical tilt initial and final values for each cell.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

377

Atoll User Manual

Figure 6.211: The Sectors tab The cell results are displayed in a table. You can access options such as sorting, exporting data using the context menu (see Figure 6.212) sort, column hiding, export, etc.

Figure 6.212: Options available for data in the Sectors tab

378

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.6.6.1.3

The Graph Tab

The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (BCCH coverage, cell dominance, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 6.213). The values displayed are indicated with a legend.

Figure 6.213: The Graph tab The tool bar allows you to: Zoom and span the graph Export to a BMP image file or simple text file Print the graph Show the values along the curves.

Figure 6.214: The Graph tab with the values displayed on the selected point

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

379

Atoll User Manual

6.6.6.1.4

The Quality Tab

The Quality tab displays the computation zone with coverage quality maps for BCCH before and after optimisation. You can define the area displayed in the coverage quality maps by selecting the zone (computation, focus, or hot spot) from the list above the maps.

Figure 6.215: Coverage maps on the Quality tab The maps are displayed with a range of values displayed on the right. If you based this optimisation on a coverage prediction (see "Setting Objective Parameters" on page 357), the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default (see "Changing the Display Properties of ACP Maps" on page 387) or by using a configuration file (see "Configuring the Default Settings" on page 350). This range can be modified using the Map Properties dialogue accessed through the tool bar (see Figure 6.216).

Figure 6.216: Defining the display properties of the coverage maps In addition to the map, a histogram is provided for quick evaluation of the improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the Generate Report tool in Atoll which only uses uniform weighting. Note: The default colour range used for display can be changed using the acp.ini preference configuration file. For information on the acp.ini file options, see the Administrator Manual.

380

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.6.6.1.5

The Change Details Tab

In addition of the map, a histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the Generate Report tool in Atoll which only uses uniform weighting. Note: The default colour range used for display can be changed using the acp.ini preference configuration file. For information on the acp.ini file options, see the Administrator Manual.

Figure 6.217: The Change Details tab You can select a subset of all changes using a slider and view the corresponding performance improvement on the graph. This can enable you to achieve two goals: To select a subset of changes to be implemented. For example, you might find that implementing only one-third of the recommended changes will provide 80% of the benefit. You could then chose to commit only those changes to the Atoll document. To find the optimal order in which to apply these changes in the field, while at the same time avoiding less than optimal performance, or even degrading the performance, during the implementation phase.

Before selecting a subset of recommended changes, it is important to understand that ACP calculates the set of recommendations globally and that these changes are interdependent. During the finalisation step, ACP calculates the ordered list of changes displayed on the Change Details tab by starting from the initial network configuration and iteratively selecting the change that will have the most effect on the network. If you 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 proposed configuration. Important: The data displayed on the other tabs takes all the proposed changes into consideration. If you select only a subset of the proposed changes on the Change Details tab, the statistics displayed on other tabs do not change. When you commit the optimisation changes, ACP will only commit the proposed changes selected on the Change Details tab. For information on committing the optimisation changes, see "The Commit Tab" on page 382.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

381

Atoll User Manual

6.6.6.1.6

The Commit Tab

This dialogue enables you to commit the set of selected changes (antenna, azimuth, tilt, or site selection) to the Atoll document or to roll the network back to its initial state. The Commit tab automatically takes into account the changes selected on the Change Details tab; the Use check box is cleared for any change that was deselected on the Change Details tab.

Figure 6.218: The Commit tab 6. Select the Current Site Selection check box to enable site selection. You can then define how sites will be added or removed. 7. In the table, define how each site will be treated during site selection: a. Select the Locked check box for each site that is not to be affected by site selection.

6.6.6.2

Viewing Optimisation Results in the Map Window

ACP can display optimisation results in the form of maps in the map window. This allows you to view the results and facilitates analysis. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default or by using a configuration file. To view the results of the optimisation in the map window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view.

4. Right-click the optimisation. The context menu appears. 5. Select New Map from the context menu. The ACP Map Types dialogue appears (see Figure 6.220).

Figure 6.219: Displaying a new map based on ACP results The maps available in the ACP Map Types dialogue are organised by category. 6. Select the category of maps or click the Expand button ( egory or map. ) to expand the category and then select the sub-cat-

382

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 7. Click OK to create the maps. The maps are created and inserted into the folder of the setup containing the optimisation results (see Figure 6.220).

Figure 6.220: The map types correspond to the available results You can display a map by selecting its check box in the folder of the setup containing the optimisation results. The display properties can be changed for a single map or for all maps. For information on the display properties for ACP maps, see "Changing the Display Properties of ACP Maps" on page 387. The following sections provide more information on the maps: "The Quality Analysis Maps" on page 383 "The Coverage Analysis Maps" on page 384 "The Change Analysis Maps" on page 385 "Best Server Analysis" on page 386 "Comparing Maps" on page 386 "Changing the Display Properties of ACP Maps" on page 387 "Exporting ACP Coverage Maps" on page 388.

6.6.6.2.1

The Quality Analysis Maps

The quality analysis maps enable you to display the BCCH quality maps in the Atoll map window. These maps are the same as those displayed on the Quality tab of the optimisations Properties dialogue. The quality analysis maps are the equivalent of maps created by different Atoll coverage predictions: The BCCH maps correspond to the Atoll coverage by CI level in GSM. For more information, see "Making Quality Studies Based on CI or C(I+N)" on page 320. The overlapping zones maps correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 232.

Making these maps available within ACP enables you to quickly validate the optimisation results without having to commit the results and then calculate a coverage prediction in Atoll. The ACP maps display results very similar to those that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before basing any decision to commit the optimisation results on the maps produced by ACP, you should keep the following recommendations in mind: You should verify the results with a different Atoll coverage prediction, such as the pilot pollution prediction. ACP generated maps are generated using the entire set of proposed changes. They do not take into account the change subset defined on the Change Details tab. Multiple carriers are not supported by ACP; the maps are only provided for the requested carrier. Even after committing the optimisation results, differences can remain between the ACP maps and the maps resulting from Atoll coverage predictions.

You can view the exact BCCH value on any pixel by letting the pointer rest over the pixel. The BCCH value is then displayed in a tooltip. For the overlapping zones map, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Configuring the Default Settings" on page 350) or by setting the CellOverlap parameter in the acp.ini file.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

383

Atoll User Manual

Figure 6.221: Examples of an overlapping zones map (left) and a BCCH variation map (right) For each network quality study, ACP offers a map showing the initial network state, the final network state, and a map showing the changes between the initial and final state.

6.6.6.2.2

The Coverage Analysis Maps

The coverage analysis maps display the coverage status according to the defined threshold used in the optimisation (for BCCH). You can use the coverage analysis maps to quickly see the area where the coverage requirements have been fulfilled. In addition, the thresholds used for clutter and hot spot zones are taken into account. ACP offers the following coverage analysis map: Cell Coverage Improvement: The cell BCCH coverage improvement maps show how the coverage has been improved or degraded by the optimisation.

Figure 6.222: Example of BCCH coverage improvement (right) You can define how the coverage analysis maps will be displayed. To define the coverage analysis map display: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 382, right-click the Coverage Analysis folder. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears (see Figure 6.223).

384

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.223: Defining display and threshold properties 3. Select the Display tab. On the Display tab, you can select the colour used to display initial BCCH, final BCCH coverage, and both. As well, you can use the slider to adjust the Transparency. 4. Select the Thresholds tab. On the Thresholds tab, you can set the thresholds to be used for the map for BCCH coverage. You can use the same thresholds as you used when you calculated the optimisation, or you can set a different threshold.

6.6.6.2.3

The Change Analysis Maps

The change analysis maps allow you to analyse the changes recommended by the ACP. The change attributes are displayed on the map using a best server map, because the types of changes that ACP recommends are all related to individual cells. The best server map used is usually the initial best server map but you can use the final best server map for new sites (i.e., sites that have been added during optimisation). The following maps are available: Reconfiguration Types: In the Reconfiguration Types folder, there is a separate map for each reconfiguration option displaying the changes to the network: azimuth, mechanical tilt, and antenna. The changes are displayed for the best server zone. The maps can be displayed individually to display each reconfiguration option separately or together to display all reconfiguration options. Sector Selection Types: In the Sector Selection Types folder, there are maps to display which sites have been added or removed. These maps are only available if the site selection was activated during optimisation. Change Order: The Change Order map displays the order of changes (as displayed on the Change Details tab of the optimisations Properties dialogue). You can define the colours used to display the order of changes by right-clicking the Change Order map in the Data tab, selecting Properties from the context menu and then changing the colours on the Display tab. By displaying the Change Order map, you can see where the most important changes to be made to the network are located. Change of Electrical Tilt, Mechanical Tilt, Azimuth, Height and Change Cost: These maps show the variation of the given parameter. They can be used to see where in the network this reconfiguration option was changed. Note: The electrical tilt values are calculated using the vertical antenna pattern. The Change of Electrical Tilt map is made available even when the change was to the antenna type.

Figure 6.224: Example of antenna type change (left) and electrical tilt change (right)

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

385

Atoll User Manual

6.6.6.2.4

Best Server Analysis

The best server analysis maps contain maps enabling you to analyse cell-related parameters as related to the best server. The following maps are available: Initial and Final Electrical and Mechanical Tilt Values: These maps show the tilt values on the initial and final network. They can be used, for example, to identify areas with strong tilt values. Initial and Final Antenna Height: These maps show the initial and final antenna heights. Initial and Final Cell BCCH Coverage: These maps show the percentage of the best server area which is covered according to the defined threshold. The values displayed are the same as those on the Cells tab of the optimisations Properties dialogue. You can use these maps to quickly identify the cells which potentially have poor quality. Initial and Final Overlapping Ratio: These maps show the percentage of the best server area with overlapping coverage greater than "1," i.e., with several received signals over the defined threshold.

6.6.6.2.5

Comparing Maps
You can compare the results displayed on one map with the results of another map from the same optimisation or from a different optimisation. To compare a map with a map from the same optimisation: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 382, right-click the map you want to compare. The context menu appears. 2. From the context menu, select Compare With and then select one of the maps in the submenu. A new map is created in the Data tab and the results of the comparison are displayed in the map window. 3. ACP creates a new map in the Data tab and displays it in the map window with the pixels that are displayed on both maps or only on a single map.

Figure 6.225: Comparing two optimisation maps To compare a map with a map from a different map type or with a map from a different optimisation: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 382, right-click the map you want to compare. The context menu appears. 2. From the context menu, select Compare With > Others. The ACP Compare Map dialogue appears (see Figure 6.226). By default, the ACP Compare Map dialogue displays only maps from the same optimisation as the map you want to compare.

Figure 6.226: The ACP Compare Map dialogue

386

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 3. Define the maps you choose from: Show studies from Predictions folder: Select the Show studies from Predictions folder check box if you want to be able to compare with a map from a coverage prediction you have already created and calculated. Show maps from all ACP setups: Select the Show maps from all ACP setups check box if you want to be able to compare with a map from a different optimisation. Show only maps of same type: Select the Show only maps of same type check box if you want to restrict the maps displayed to maps displaying comparable information.

4. Select the map with which you want to compare the first one and click OK. ACP creates a new map in the Data tab and displays it in the map window with the pixels that are displayed on both maps or only on a single map.

Tip:

By first defining a display interval of "1" in both maps and then comparing them, the resulting comparison map will have more meaningful results. For information on defining "Changing the Display Properties of ACP Maps" on page 387.

6.6.6.2.6

Changing the Display Properties of ACP Maps

You can define how ACP maps are displayed in the Atoll map window. You can define the colours used as well as the ranges of values on the Display tab of each maps Properties dialogue. As well, ACP allows you to display the value on each pixel in the form of a tooltip. To define the display of an ACP map: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 382, right-click the map whose display you want to define. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears (see Figure 6.227).

Figure 6.227: Setting the display properties for a map 3. Select the Display tab. 4. On the Display tab, you can define the following settings: Colours: For each range of values, you can click the colour button and select the colour that will be used to represent that range. Min. and Max.: You can define the minimum and maximum values that will define that range. Transparency: You can define the transparency of the map using the slider. Add to legend: You can display the range of values of the optimisation map by selecting the Add to legend. check box. Actions: You can modify the ranges of values by clicking the Actions button and selecting one of the following: Select All: Select Select All to select all the ranges on the display tab. Anything you select after that from the Actions menu (for example, Delete) will be applied to the selected ranges. Delete: Select Delete to delete the selected range or ranges. Insert Before: Select Insert Before to insert a new range before the selected range. Insert After: Select Insert After to insert a new range after the selected range Shading: Select Shading to open the Shading dialogue where you can define all the ranges by setting the first value, the last value, and the step between values, as well as the colour used for the first value and the colour used for the last value. ACP will shade the ranges in between the first and last value with a range of colours going from the first colour to the last.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

387

Atoll User Manual Save as Default: Select Save as Default to set the current settings on the display tab to the default settings. These settings can then be used for all maps of the same kind. Load from Default: Select Load from Default to change the current settings to those set as the default using Save as Default. Reset to Default: Select Reset to Default to change the current settings back to the ACP defaults. You can also use Reset to Default to return to the ACP defaults when you have created user-defined defaults using Save as Default.

You can display the value on a pixel by resting the pointer on the pixel in the map window. The value on that pixel will be displayed in a tooltip (see Figure 6.228).

Figure 6.228: Tool tip displaying ACP results on selected point

6.6.6.2.7

Exporting ACP Coverage Maps

ACP enables you to export the optimisation coverage maps as BMP files. Before you can export an optimisation coverage map, you must first select the map and define its appearance as explained in "Viewing Optimisation Results in the Map Window" on page 382. To export an optimisation coverage map: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( 4. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation map you want to export. ) to expand the optimisation.

5. Right-click the map. The context menu appears. 6. Select Export the Coverage from the context menu. The Save As dialogue appears. 7. Enter a File name for the exported coverage map and select the format from the Save as type list. 8. Click Save. The exported coverage map is saved in the selected format. Depending on the file format selected from the Save as type list, Atoll creates an additional file in the same location containing geo-referencing information: BMP file: Atoll creates a BPW file. ArcView grid (TXT) file: Atoll creates a BPW file. BIL file: Atoll creates a HDR file. GRD or GRC file: Atoll creates a TAB file. PNG file: Atoll creates a PGW file. TIF file: Atoll creates a TFW file.

9. Atoll also creates a BPW file in the same location containing geo-referencing information.

6.6.6.3

Viewing Optimisation Results Using the Histogram

ACP can display optimisation results in the form of a histogram. The histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be used for the histogram, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default or by using a configuration file. To view the results of the optimisation using a histogram: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( 4. Click the Expand button ( Note: ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view. ) to expand the folder of the optimisation.

Depending on the type of optimisation results you want to view, you might need to expand additional folders.

5. Right-click the optimisation results. The context menu appears.

388

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 6. Select Histogram from the context menu. The histogram appears in a separate window with a legend on the right side.

6.7

Verifying Network Capacity

An important step in the process of creating a GSM/GPRS/EDGE network is verifying the capacity of the network. This is done using measurements of the strength of the pilot signal in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: "Importing a Drive Test Data Path" on page 389 "Displaying Drive Test Data" on page 391 "Defining the Display of a Drive Test Data Path" on page 392 "Network Verification" on page 392 "Exporting a Drive Test Data Path" on page 398 "Extracting CW Measurements from Drive Test Data" on page 398 "Printing and Exporting the Drive Test Data Window" on page 399.

6.7.1

Importing a Drive Test Data Path

In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving subcells, neighbour subcells, or any other subcells). In GSM/GPRS/EDGE networks, a transmitter is identified by its BCCH and its BSIC. Therefore, you must indicate during the import process which columns contain the BCCH and the BSIC of transmitters and the BSIC format (decimal or octal) used in 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. Click the Data tab in the Explorer window. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. You can import one or several files. Select the file or files you want to open. Note: If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import.

5. Click Open. The Import of Measurement Files dialogue appears. Note: Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue.

6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Configuration, select an import configuration from the Configuration list. b. Continue with step 10.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

389

Atoll User Manual

Notes: When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. In case several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual. 7. Click the General tab. On the General tab, you can set the following parameters: Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document. 8. Click the Setup tab (see Figure 6.229).

Figure 6.229: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click Setup to link file columns and internal Atoll fields. The Drive Test Data Configuration dialogue appears. c. 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. Note: 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. In the BCCH Identifier box, enter a string that must be 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 scram-

390

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks bling code group of scanned cells, enter it here. Atoll will then search for columns with this string in the column name. If there is BCCH information contained in the drive test data file, leave the BCCH Identifier box empty. e. In the BSIC Identifier box, enter a string that must be found in the column names identifying the BSIC 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. f. From the BSIC Format list, select the scrambling code format, either "Decimal" or "Octal."

g. Click OK to close the Drive Test Data Configuration dialogue. Important: If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Configuration dialogue, Atoll should recognize all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>". If a column is marked with "<Ignore>", it will not be imported. The data in the file must be structured so that the columns identifying the 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 wish 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 Configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a special 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, "*.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. Notes: 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 button ( ) in front of the file in the Setup part to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Setup and clicking the Delete button.

10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The mobile data are imported into the current Atoll document.

6.7.2

Displaying Drive Test Data

When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see information about the transmitters at that location. To display information about a single drive test data point: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want server and neighbour information. Atoll displays an arrow pointing towards the serving transmitters and neighbours (see Figure 6.231 on page 397), with a number identifying the server as numbered in the drive test data. If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display Type" on page 33.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

391

Atoll User Manual

6.7.3

Defining the Display of a Drive Test Data Path

Drive test data paths have the standard Atoll display dialogue to allow you to define the display according to any available attribute, to manage permanent labels on the map, tooltips and the legend. To open the display dialogue of a drive test data path: 1. Click the Data tab in the Explorer window. 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 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: a text or integer attribute (discrete value) a numerical value (value interval).

In addition, a last option is available which permits to display points according to more than one criterion at a time. By selecting Multiple AdvancedAdvanced Display from the Display Type, a dialogue opens in which you can define the following display for each single point of the measurement path: a symbol type according to any attribute a symbol colour according to any attribute a symbol size according to any attribute

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. Notes:

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 on the Data tab of the Explorer by selecting Sort Alphabetically from the Drive Test Data context menu. You can export the display settings of a drive test data path. Colours, symbols, and other display settings can be saved in a .cfg file to make them available for use on another drive test data path. To access the import/export interface, click the Actions button on the Display tab of the path properties dialogue. You can then import the configuration file by selecting Tools > User Configuration > Import.

6.7.4

Network Verification
The imported drive test data is used to verify the GSM/GPRS/EDGE network. To improve the relevance of the data, Atoll allows you to filter out incompatible or inaccurate points. You can then use the data for coverage predictions, either by comparing the imported measurements with previously calculated coverage predictions, or by creating new coverage predictions using the imported drive test data. In this section, the following are explained: "Filtering Incompatible Points Along Drive Test Data Paths" on page 392 "Creating Coverage Predictions from Drive Test Data Paths" on page 394 "Displaying Statistics Over a Drive Test Data Path" on page 395 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 396 "Analysing Data Variations Along the Path" on page 396.

6.7.4.1

Filtering Incompatible Points Along Drive Test Data Paths

When using a drive test data path, some measured points might present values that are too far outside of the median values to be useful in calibration. As well, test paths might include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder. The context menu appears.

392

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 3. Select Filter from the context menu. The CW Measurement Filter dialogue 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. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder. The context menu appears.

3. Select Filter from the context menu. The CW Measurement Filter dialogue appears. 4. Click More. The Filter dialogue 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 6.230).

Figure 6.230: The Filter dialogue - Advanced tab i. 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 X*

Data are kept in the table only if

value equal to X (X can be a number or characters) value not equal to X (X can be a number or characters) numerical value is less than X numerical value is greater than X numerical value is less than or equal to X numerical value is greater than or equal to X text objects which contain X text objects end with X text objects which start with X

ii. Click OK to filter the data according to the criteria you have defined. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

393

Atoll User Manual Combinations of filters are first made horizontally, then vertically. For more information on filters, see "Advanced Data Filtering" on page 75. iii. Click OK to apply the filter and close the dialogue. Note: The Refresh Geo Data option available in the context menu of Drive Test Data paths enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones.

6.7.4.2

Creating Coverage Predictions from Drive Test Data Paths

You can create the following coverage predictions for all transmitters on each point of a drive test data path: Coverage by signal level Coverage by C/I.

To create a coverage prediction along a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. 5. Under Standard Studies, select one of the following coverage predictions and click OK: Coverage by Signal Level: a. Click the Condition tab. At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range.

b. Under Server, select "All" to consider all servers. c. If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Probability. d. You can select the Indoor Coverage check box to add indoor losses. e. You can select which TRX type to consider by selecting it from the Reception from Subcells list. Coverage by C/I: a. Click the Condition tab. On the Condition tab, you can define the signals that will be considered for each pixel. You can click the arrow button ( ) and select one of the following thresholds: Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower end of the signal level range.

b. 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 400). c. Enter a hand-over margin in the With a Margin text box. The default value is "4 dB." d. 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. e. You can select the Indoor Coverage check box to add indoor losses. f. Under Interference Condition, You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list. Click the arrow button ( ) and select one of the following thresholds: Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for each subcell (including the defined power reduction) as the lower end of the CI range. Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for all subcells as the lower end of the CI range.

g. Select either CI or C(I+N). h. Click the arrow button ( ) and select one of the following thresholds:

394

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for each subcell (including the defined power reduction) as the upper end of the CI range. Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for all subcells as the upper 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.

Note:

i.

Select whether you want the defined interference 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.

j.

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.

k. 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. l. 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.

m. 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 you want Atoll to take interference due to intra-technology third-order intermodulation into consideration when calculating the total interference, you must set up your document and database as explained in "Taking Intermodulation Interference into Consideration in Calculations" on page 422. n. 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 Studies from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calculations in Atoll). You can display the information in these new columns in the Drive Test Data window. For more information on the Drive Test Data window, see "Analysing Data Variations Along the Path" on page 396.

6.7.4.3

Displaying Statistics Over a Drive Test Data Path

Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific Drive Test Data path: 1. Click the Data tab in the Explorer window. 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 dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

395

Atoll User Manual 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.

6.7.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. Click the Data tab in the Explorer window. 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 dialogue appears. 5. Select a transmitter from the On the Transmitter list. 6. Click the For the Fields list. The list opens. 7. Select the check box beside the field you want to extract for the selected transmitters. Note: 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.

6.7.4.5

Analysing Data Variations Along the Path

In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point. To analyse data variations using the Drive Test Data window. 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 6.231)

396

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks .

Figure 6.231: The Drive Test Data window 5. Click Display at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 6.232).

Figure 6.232: The Display Parameters dialogue 6. In the Display Parameters dialogue: Select the check box next to any field you want to display in the Drive Test Data window. If you 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 dialogue. Note: You can change the display status or the colour of more than one field at a time. You can select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field you want to import. You can select non-contiguous fields by pressing CTRL and clicking each field. You can then change the display status or the colour by right-clicking on the selected fields and selecting the choice from the context menu.

The selected fields are displayed in the Drive Test Data window. 7. You can display the data in the drive test data path in two ways: Click the values in the Drive Test Data window. Click the points on the drive test data path in the map window.

The drive test data path appears in the map window as an arrow pointing towards the serving cell, with a number identifying the best server (see on page 397). If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display Type" on page 33.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

397

Atoll User Manual 8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the secondary Y-axis from the right-hand list on the top of the Drive Test Data window. The selected values are displayed in the colours defined for this variable in the Display Parameters dialogue. 9. You can change the zoom level of the Drive Test Data window display in the Drive Test Data window in the following ways: Zoom in or out: i. Right-click the Drive Test Data window.

ii. Select Zoom In or Zoom Out from the context menu. Select the data to zoom in on: i. Right-click the Drive Test Data window on one end of the range of data you want to zoom in on.

ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data window on the other end of the range of data you want to zoom in on. iv. Select Last Zoom Point from the context menu. The Drive Test Data window zooms in on the data between the first zoom point and the last zoom point. 10. Click the data in the Drive Test Data window to display the selected point in the map window. Atoll will recentre the map window on the selected point if it is not presently visible.

Tip:

If you open the table for the drive test data you are displaying in the Drive Test Data window, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data window (see Figure 6.231 on page 397).

6.7.5

Exporting a Drive Test Data Path

You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.

6.7.6

Extracting CW Measurements from Drive Test Data

You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears. 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the Transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the For the Fields list. 6. Under CW Measurement Creation Parameters: a. Enter the Min. Number of Points to Extract per Measurement Path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured Signal Levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Measurements and Model Calibration Guide.

398

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.7.7

Generating Interference Matrices from a Drive Test Data Path

You can generate interference matrices from drive test data paths and extract the results to the Interference Matrix folder. To generate Interference Matrices from a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract Interference Matrices from the context menu. The Interference Matrix Export dialogue appears. 5. Under Storage File: a. Click the Browse button to select the path and the name of the interference matrix file to be generated. b. Select the field that contains the signal level information that you want Atoll to convert into C/I values from the Select the measured signal levels list. 6. Click OK. Atoll creates a new inteference matrix item in the Interference Matrix folder which can be used like any other interference matrix (See "Interference Matrices" on page 280).

6.7.8

Printing and Exporting the Drive Test Data Window

You can print or export the contents of the Drive Test Data window, using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 6.231 on page 397). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 396. 6. Right-click the Drive Test Data window. The context menu appears. To export the Drive Test Data window: a. Select Copy from the context menu. b. Open the document into which you want to paste the contents of the Drive Test Data window. c. Paste the contents of the Drive Test Data window into the new document. To print the Drive Test Data window: a. Select Print from the context menu. The Print dialogue appears. b. Click OK to print the contents of the Drive Test Data window.

6.8

Advanced Configuration
In this section, the following advanced configuration options are explained: "Setting HCS Layers" on page 400 "Comparing Service Areas in Calculations" on page 400 "Cell Types" on page 404 "TRX Configuration" on page 407 "Codec Configuration" on page 408 "Coding Scheme Configuration" on page 411 "Timeslot Configurations" on page 414 "Advanced Transmitter Configuration Options" on page 415 "GSM/GPRS/EDGE Multi-Service Traffic Data" on page 418 "Defining the Interferer Reception Threshold" on page 421 "Advanced Modelling of Hopping Gain in Studies" on page 421 "Taking Intermodulation Interference into Consideration in Calculations" on page 422 "Modelling Shadowing" on page 422 "Modelling the Co-existence of Networks" on page 423

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

399

Atoll User Manual

6.8.1

Setting HCS Layers

You can model hierarchical networks in Atoll by defining hierarchical cell structure (HCS) layers. HCS layers are defined by the following parameters: 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 dialogue). Note: 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. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > HCS Layers. The HCS Layers table appears. 4. 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 "Working with Data Tables" on page 53): Name: Enter a name for the HCS layer. This name will appear in other dialogues 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 studies when the HCS server option is selected.

6.8.2

Comparing Service Areas in Calculations

For any coverage prediction, traffic analysis, or interference matrix calculation, transmitter service areas can be defined differently according to the server selection made on the Condition tab of the dialogue used to define the calculation. On the Condition tab, you can select: All: All servers will be taken into consideration. Best Signal Level: The best signal level from all servers on all layers will be taken into consideration. Second Best Signal Level: The second best signal level from all servers on all layers will be taken into consideration. Best Signal Level per HCS Layer: The best signal level from all servers on each HCS layer will be taken into consideration. Second Best Signal Level per HCS Layer: The second best signal level from all servers on each HCS layer will be taken into consideration. HCS Servers: The best signal level by HCS layer on each pixel will be 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. 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. Grouped HCS Servers: The best signal level by HCS layer on each pixel will be 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. In addition, layers are grouped by supported mobility types.

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 Condition 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: 3 tri-sector base stations on a micro layer

400

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 1 omni base station on a macro layer 1 omni base station on an umbrella layer

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
Macro Layer Micro Layer Umbrella Layer

Priority (0:Lowest)
2 3 1

Max Speed (km/h)

100 10 300

Layer Reception Threshold (dBm)

-90 -84 -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. All: All servers are taken into consideration

Composite Coverage

Umbrella Layer Coverage

Macro Layer Coverage

Micro Layer Coverage

Figure 6.233: Coverage by Transmitter on All the servers Figure 6.233 shows the service areas of all the transmitters without any layers taken into consideration. Each cell is considered individually and the limit of its coverage is defined by its subcell reception thresholds. Overlapping is possible between transmitters and between HCS layers. Best Signal Level: The best signal level from all servers on all layers is taken into consideration.

Composite Coverage Figure 6.234: Coverage by Transmitter for the Best Signal Level

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

401

Atoll User Manual

Umbrella Layer Coverage

Macro Layer Coverage

Micro Layer Coverage

Figure 6.234: Coverage by Transmitter for the Best Signal Level Figure 6.234 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

Umbrella Layer Coverage

Macro Layer Coverage

Micro Layer Coverage

Figure 6.235: Coverage by Transmitter for the Best Signal Level per HCS Layer Figure 6.235 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. 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.

Composite Coverage Figure 6.236: Coverage by Transmitter for the HCS Servers

402

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Umbrella Layer Coverage

Macro Layer Coverage

Micro Layer Coverage

Figure 6.236: Coverage by Transmitter for the HCS Servers Figure 6.236 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 assuming their calculated signal level is higher than the subcell reception thresholds and the HCS layer reception threshold. Overlapping between HCS layers is possible, but overlapping between transmitters on a given HCS layer is not possible. In the case above, the micro layer overlaps the macro layer and its borders are defined by the maximum between the subcell reception thresholds (-102 dBm) and the micro layer threshold (-84 dBm), i.e. -84 dBm. In addition, the macro layer overlaps the umbrella layer and its borders are defined by the maximum between the subcell reception thresholds (-105 dBm) and the macro layer threshold (-90 dBm), i.e. -90 dBm. The umbrella layer is displayed when its signal level exceeds the maximum between the subcell reception thresholds and the umbrella layer threshold, i.e. -105 dBm. 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

Umbrella Layer Coverage

Macro Layer Coverage

Micro Layer Coverage

Figure 6.237: Coverage by Transmitter for the Highest Priority HCS Server Figure 6.237 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. Note: 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.

Grouped 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. The server selection mode is similar to HCS Servers except that, if a mobility is supported by several layers, the traffic is served on the layer with the highest priority.

This option is not available by default. To add the "Grouped HCS Servers" option to the server list in prediction, traffic capture, and interference matrix calculations, you must add the following lines in the atoll.ini file:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

403

Atoll User Manual

[TMP] ExtraServZone = 1

Composite Coverage

Umbrella Layer Coverage

Macro Layer Coverage

Micro Layer Coverage

Figure 6.238: Coverage by Transmitter for the Grouped HCS Servers Figure 6.236 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 when their calculated signal level is higher than the subcell reception thresholds and the HCS layer reception threshold. Overlapping between HCS layers is possible, but overlapping between transmitters on a given HCS layer is not possible. In the case above, the micro layer overlaps the macro layer because it has the highest priority with the 3 kmh mobility and the macro layer has a higher priority than the umbrella layer with the 50 kmh and 90 kmh mobilities (which are not supported by the micro layer). The umbrella layer is displayed when neither the micro nor the macro layer provides enough signal strength to fulfil the reception threshold conditions

6.8.3

Cell Types
A cell type is a defined set of TRX types. The cell type, with its TRX types, constitutes the basic configuration of a transmitter in GSM/GPRS/EDGE. By changing the cell type assigned to a transmitter or station template, you change its basic configuration. You can create cell types and assign different existing TRX types to them. In this section, the following are described: "TRX Types" on page 404 "Creating a Cell Type" on page 404 "Examples of Cell Types" on page 406.

6.8.3.1

TRX Types
By default, the Atoll GSM/GPRS/EDGE document template has three types of TRXs: BCCH: The BCCH TRX type is the BCCH carrier TCH: The TCH TRX type is the default traffic carrier TCH_EGPRS: The TRX type is the EDGE traffic carrier. TCH_INNER: The TRX type is the inner traffic carrier.

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_EGPRS.mdb." For information on the Atoll document template, see the Administrator Manual.

6.8.3.2

Creating a Cell Type

A cell type must have a BCCH TRX type for the broadcast control channel and a TCH TRX type for the default traffic carrier; it can also have a TCH_INNER or TCH_EGPRS TRX type. You can not have more than one instance of a given TRX type in a cell type. To create a cell type: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears.

404

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 3. Select Network Settings > Cell Types. The Cell Types table appears. 4. In the row marked with the New Row icon ( other dialogues when you select a cell type. ), enter the name of the new cell type. This name will appear in

5. Select the row containing the cell type and click the Properties button. The cell types Properties dialogue appears. In the cell types Properties dialogue, you can add and define the TRX types that will constitute the cell type. 6. 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 "Working with Data Tables" on page 53): TRX Type: Select a TRX type from the list. Frequency Domain: Select a frequency domain from the list. Only channels belonging to this frequency domain will be allocated to TRXs of this TRX type during automatic or manual frequency planning. DL Power Reduction: Enter a value for the reduction of power relative to the transmitter power. The downlink power reduction can be used to model inner subcells. Reception Threshold (dBm): Enter a minimum received signal for this TRX type. C/I Threshold (dB): Enter a minimum signal quality for this TRX type. The C/I Threshold can be used in interference studies and in the AFP. 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. Important: 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 6.103). Note: 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 "Synthesized 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 (Synthesized 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 (Synthesized 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. 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 mulitplies 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. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

405

Atoll User Manual 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. Number of Antennas (Transmission Diversity): Enter the number of antennas subcells based on this TRX type can use for transmission. In most cases, a transmitter will transmit with only one antenna, however, some transmitters are capable of transmission diversity. By transmitting on more than one antenna, the signal experiences a gain of 3 dB. An additional transmission diversity gain can be defined per clutter class in order to correctly model gain due to the environment. Notes: An Other Properties tab is available if user-defined fields have been added to the Cell Types table.

7. Click OK to close the cell types Properties dialogue. 8. Click Close to close the Cell Types table.

6.8.3.3

Examples of Cell Types

When you create a new GSM/GPRS/EDGE document, some cell types are provided by default. In this section, the parameters for two examples of cell types are given: "Normal Cell Type" on page 406 "Concentric Cell Type" on page 407.

Normal Cell Type

A normal cell type consists of two TRX types: BCCH TRX type TCH TRX type

The following table describes the parameters to be specified for each hopping mode.

Hopping mode Parameter Where Used in Atoll

Automatic or manual frequency planning Automatic frequency planning Automatic or manual frequency planning Interference studies, Automatic frequency planning Automatic frequency planning Signal level studies Interference studies Signal level studies Automatic frequency planning Automatic frequency planning Automatic frequency planning Automatic frequency planning, Interference studies Traffic analysis Traffic analysis Dimensioning

Non hopping
x Not used x x x = 0 for BCCH = 0 for TCH Non Hopping x x Not used x x x x x

BBH
x x x x x = 0 for BCCH = 0 for TCH Base Band Hopping x x x x x x x x

SFH
x x x x x = 0 for BCCH = 0 for TCH Synthesized Hopping x x x x x x x x

Frequency domain Maximum MAL (Mobile Allocation List) length Allocation strategy C/I threshold % max interference DL power reduction Hopping mode Reception threshold AFP weight HSN domain Lock HSN DTX supported Half-rate traffic ratio Target rate of traffic overflow Timeslot configuration

406

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Hopping mode Parameter Where Used in Atoll

Traffic analysis, Packet studies Traffic analysis, Packet studies Signal level studies

Non hopping
x x x

BBH
x x x

SFH
x x x

Default TRX configuration EDGE Power Backoff Number of antennas

Concentric Cell Type

A concentric cell type consists of three TRX types: BCCH TRX type TCH TRX type TCH_INNER

The following table describes the parameters to be specified for each hopping mode.

Hopping mode Parameter Where Used in Atoll

Automatic or manual frequency planning Automatic frequency planning Automatic or manual frequency planning Interference studies, Automatic frequency planning Automatic frequency planning

Non hopping
x Not used x x x = 0 for BCCH => 0 for TCH <> 0 for TCH_INNER Non Hopping x x Not used x x x x x

BBH
x x x x x = 0 for BCCH => 0 for TCH <> 0 for TCH_INNER Base Band Hopping x x x x x x x x

SFH
x x x x x = 0 for BCCH => 0 for TCH <> 0 for TCH_INNER Synthesized Hopping x x x x x x x x

Frequency domain Maximum MAL (Mobile Allocation List) length Allocation strategy C/I threshold % max interference

DL power reduction

Signal level studies

Hopping mode Reception threshold AFP weight HSN domain Lock HSN DTX supported Half-rate traffic ratio Target rate of traffic overflow Timeslot configuration

Interference studies Signal level studies Automatic frequency planning Automatic frequency planning Automatic frequency planning Automatic frequency planning, Interference studies Traffic analysis Traffic analysis Dimensioning

6.8.4

TRX Configuration
In GSM/GPRS/EDGE projects, coding schemes are modelled using TRX Configuration. For each TRX, you can define a maximum coding scheme for GPRS or for EDGE. The maximum number of coding schemes can also be defined per terminal, if the terminal is GPRS or EDGE-capable. Capacity will be limited by the lower of the maximum coding schemes defined for the TRX Configuration and for the terminal. For example, if the highest coding index number defined on the terminal is lower than the value defined on the TRX Configuration, capacity will be limited by the highest index number supported by the terminal. 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,

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

407

Atoll User Manual the value for 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 this section, the following is described: "Creating or Importing TRX Configuration" on page 408.

6.8.4.1

Creating or Importing TRX Configuration

In Atoll, you can create or import TRX Configuration for GSM/GPRS/EDGE documents. To create new TRX Configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > TRX Configuration. The TRX Configuration table appears. The TRX Configuration table contains a entry called "Standard." 4. In the row marked with the New Row icon ( ), enter the following parameters to create TRX Configuration (for information on working with data tables, see "Working with Data Tables" on page 53): Name: Select a TRX type from the list. Max. GPRS CS: Enter the maximum number of coding schemes that the GPRS-compatible configuration can use. Max. EDGE CS: Enter the maximum number of coding schemes that the EDGE-compatible configuration can use. Comments: You can enter comments in this field if you wish.

If you have 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 new TRX Configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > TRX Configuration. 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 63.

6.8.5

Codec Configuration
In Atoll, you can model configurations of voice codecs for GSM networks. The codec configurations are modelled with codec configuration and their parameters are used in coverage predictions concerning voice quality indicators. You can create different codec configurations for different Active Codec mode Sets (ACS). For example, a certain codec configuration might have full-rate and half-rate codec modes defined for 12.2 Kbps, 7.4 Kbps, 5.9 Kbps, and 4.75 Kbps. This configuration would then only be compatible with the defined modes. When the codec configuration does not have the capacity for ideal link adaptation, adaptation thresholds are used in calculations (see "Setting Codec Mode Adaptation Thresholds" on page 409). When the codec configuration has the capacity for ideal link adaptation, quality thresholds are used in calculations (see "Setting Codec Mode Quality Thresholds" on page 410). In this section, the following are described: "Opening the Codec Mode Table" on page 408 "Creating or Modifying Codec Configuration" on page 409 "Setting Codec Mode Adaptation Thresholds" on page 409 "Setting Codec Mode Quality Thresholds" on page 410 "Using Codec Configurations in Transmitters and Terminals" on page 410. Note: Codec configurations can be adapted in order to create an advanced model of the frequency hopping gain effect on the quality indicator studies (see "Advanced Modelling of Hopping Gain in Studies" on page 421).

6.8.5.1

Opening the Codec Mode Table

You can access the table containing all the codec modes which can be used to create or modify and codec configurations. This table is read-only and cannot be edited.

408

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To open the Codec Mode table: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings >Codec Modes >Open Table from the context menu. The Codec Mode table appears. It displays the following information: Name: The name of the codec mode. Codec Type: The specific type of a speech coding algorithm, applied on a specific radio access technology (e.g., FR or AMR). Half Rate: The codec mode is half rate if the check box under Half Rate is selected. Power Backoff: The codec mode has power backoff if the check box under Power Backoff is selected. Max Rate (Kbps): The maximum rate per timeslot corresponding to the selected codec mode. Priority: For a given quality, in a non ideal link adaptation mode, if several codec modes are possible, the one with the highest priority (i.e., the highest number) is retained.

6.8.5.2

Creating or Modifying Codec Configuration

You create a codec configuration by creating a new entry in the Codec configuration table. Additional parameters, such as the adaptation thresholds and the quality thresholds, can be set in the Properties dialogue for the codec configuration. The additional parameters are explained in the following sections: "Setting Codec Mode Adaptation Thresholds" on page 409 "Setting Codec Mode Quality Thresholds" on page 410

To create or modify codec configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings >Codec Modes >Codec Configurations. The Codec Configuration table appears. 4. If you are creating a new codec configuration, enter the name of the codec configuration in the row marked with the New Row icon ( ). This name will appear in other dialogues when you select a codec configuration. If you are modifying an existing codec configuration, continue with the following step. 5. Set the following parameters for the codec configuration: 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. Note: 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 dialogue.

6.8.5.3

Setting Codec Mode Adaptation Thresholds

A GSM network has a variety of different codec modes that allow it to optimise resource usage. These codec modes include Full Rate (FR), Half Rate (HR), Enhanced Full Rate (EFR), and many Adaptive Multi-Rate (AMR) modes and can be seen in the read-only codec mode table (See"Opening the Codec Mode Table" on page 408). A GSM network, with different codec configurations on different transmitters, can dynamically allocate and manage resources based on interference levels. You can define quality thresholds for each codec mode compatible with the codec configuration in the Adaptation Thresholds tab in the codec configuration Properties dialogue. These thresholds are used in calculations when the codec configuration does not have the capacity for ideal link adaptation. To define the codec mode adaptation thresholds to be used when the codec configuration does not have the capacity for ideal link adaptation: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings >Codec Modes >Codec Configurations. The Codec Configuration table appears. 4. 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. 5. Select Record Properties from the context menu. The codec configuration Properties dialogue appears. 6. Select the Adaptation Thresholds tab. Each codec mode adaptation threshold has the following parameters:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

409

Atoll User Manual Codec Mode: The codec mode. Mobility: The mobility to which this configured codec mode applies. You can select "All" if you want it to apply to all mobilities. Frequency Hopping: The type of frequency hopping to which this configured codec mode applies. You can select "All" if you want the adaptation threshold to apply to any type of frequency hopping. Frequency Band: The frequency band to which this configured codec mode applies. You can select "All" if you want it to apply to any frequency band. Adaptation Threshold (dB): Enter the adaptation threshold that will be used when the codec configuration does not have the capacity for ideal link adaptation. Note: You can create a new adaptation threshold by entering the parameters in the row marked with the New Row icon ( 7. Click OK. ).

6.8.5.4

Setting Codec Mode Quality Thresholds

You can define quality thresholds for each codec mode compatible with the codec configuration in the Adaptation Thresholds tab in the codec configuration Properties dialogue. These thresholds are used in calculations when the codec configuration has the capacity for automatic mode selection. The quality indicators that can be used with codec configuration are Bit Error Rate (BER), Frame Error Rate (FER), and Mean Opinion Score (MOS). You can define each a quality threshold for each quality indicator, in combination with specific codec modes, mobilities, frequency hopping modes, and frequency bands, as a function of CN and CI + N. These quality thresholds are used in calculations when codec configuration has the capacity for ideal link adaptation. The quality threshold chosen respects the combination of codec modes, mobilities, frequency hopping modes, and frequency bands as well as the selected quality indicator. To define the codec mode quality thresholds to be used when the codec configuration has the capacity for automatic mode selection: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings >Codec Modes >Codec Configurations. The Codec Configuration table appears. 4. 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. 5. Select Record Properties from the context menu. The codec configuration Properties dialogue appears. 6. Select the Quality Graphs tab. Each quality indicator threshold has the following parameters: Quality Indicator: The quality indicator. Codec Mode: The codec mode to which this quality indicator threshold applies (See "Opening the Codec Mode Table" on page 408 for more information). Mobility: The mobility to which this quality indicator threshold applies. You can select "All" if you want it to apply to all mobilities. Frequency Hopping: The type of frequency hopping to which this quality indicator threshold applies. You can select "All" if you want it to apply to all types of frequency hopping. Frequency Band: The frequency band to which this quality indicator threshold applies. You can select "All" if you want it to apply to all frequency bands. QI = f(C/N): The values of the graph defining the selected quality indicator threshold as a function of CN. You can view the graph and edit its values by selecting the row containing the quality indicator and clicking the CN Graph button. 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 interference due to intra-technology third-order intermodulation is taken into consideration, Atoll assumes that the CI graphs include the effect of this interference whereas the CN graphs do not. Note: You can create a new quality indicator threshold by entering the parameters in the row marked with the New Row icon ( 7. Click OK. ).

6.8.5.5

Using Codec Configurations in Transmitters and Terminals

In Atoll, codec configurations can be assigned to transmitters and terminals. If a codec configuration is assigned on both the transmitter and terminal, Atoll takes the codec modes common to both and finds the possible modes, using the terminal-side thresholds if the defined thresholds are different on transmitter and terminal sides. If no codec configuration is defined either at the transmitter or in the terminal, the transmitter will not be considered in the specific quality indicators coverage prediction.

410

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To assign a codec configuration to a transmitter: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign the codec configuration. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter on the map and selecting Properties from the context menu.

5. Click the Configurations tab. 6. Under GSM Properties, select the Codec Configuration from the list. To assign a codec configuration to a terminal: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder. ) to expand the Terminals folder.

4. Right-click the terminal to which you want to assign the codec configuration. The context menu appears. 5. Select Properties from the context menu. The terminals Properties dialogue appears. 6. Select the Codec Configuration from the list.

6.8.6

Coding Scheme Configuration

In Atoll, you can model a coding scheme configuration with coding schemes and their related thresholds. Any GPRS/ EDGE-capable transmitters must have a coding scheme configuration assigned to them. In this section, the following are described: "Opening the Coding Schemes Table" on page 411 "Creating or Modifying a Coding Scheme Configuration" on page 412 "Using Coding Scheme Configuration in Transmitters and Terminals" on page 413 "Adapting Coding Scheme Thresholds for a Maximum BLER" on page 413 "Displaying Coding Scheme Throughput Graphs" on page 413. Note: Coding scheme configurations can be adapted in order to create an advanced model of the frequency hopping gain effect on the GPRS/EDGE studies (see"Advanced Modelling of Hopping Gain in Studies" on page 421).

6.8.6.1

Opening the Coding Schemes Table

You can access the table containing all the coding schemes that can be used to create or modify and coding scheme configurations. This table is read-only and can not be edited. To open the Coding Schemes table: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings >Coding Schemes >Open Table from the context menu. The Coding Schemes table appears. It displays the following information: Name: The name of the coding scheme: CS: Coding schemes for GPRS MCS: Modulation and coding schemes for EGPRS (EDGE) DAS: Downlink coding schemes for EGPRS2-A (EDGE Evolution) DBS: Downlink coding schemes for EGPRS2-B (EDGE Evolution)

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). Max throughput (Kbps): For a given quality, if several codec modes are possible, the one with the highest priority (highest number) is retained.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

411

Atoll User Manual

6.8.6.2

Creating or Modifying a Coding Scheme Configuration

You create a coding scheme configuration by creating a new entry in the Coding Scheme Configurations table. The coding scheme thresholds for a coding scheme configuration can be set in its Properties dialogue. To create or modify a coding scheme configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings >Coding Schemes >Coding Scheme Configurations. The Coding Scheme Configurations table appears. 4. If you are creating a new coding scheme configuration, enter the name of the coding scheme configuration in the row marked with the New Row icon ( scheme configuration. ). This name will appear in other dialogues when you select a coding

If you are modifying an existing coding scheme configuration, continue with the following step. 5. Set the following parameters for the coding scheme configuration: 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. Note: 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 dialogue.

6. 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. 7. Select Record Properties from the context menu. The coding scheme configurations Properties dialogue appears. The coding scheme configurations Properties dialogue has a General tab which allows you to modify the properties described above. 8. Select the Thresholds tab. Each coding scheme threshold has the following parameters: Coding Scheme: The coding scheme. Reception Threshold (dBm): The signal level admission threshold for the corresponding coding scheme when the ideal link adaptation option is cleared in GPRS/EDGE coverage predictions. C/I Threshold (dB): The C/I admission threshold for the corresponding coding scheme when the ideal link adaptation option is cleared in GPRS/EDGE coverage predictions. 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. 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 interference due to intra-technology third-order intermodulation is taken into consideration, Atoll assumes that the CI graphs include the effect of this interference whereas the C graphs do not. Max. Throughput (Kbps): The maximum throughput per timeslot using this coding scheme. 8PSK Modulation: The 8PSK Modulation check box is selected if this coding scheme supports it. This has an impact on the EDGE service zone which can be seen in traffic analysis and EDGE predictions. EDGE: The EDGE check box is selected if this coding scheme supports EDGE. 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. Note: You can create a new coding scheme threshold by entering the parameters in the row marked with the New Row icon ( 9. Click OK. ).

412

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Notes The throughput per timeslot graphs are defined for given frequency hopping mode, mobility type and frequency band. These graphs will be taken into account in a prediction study if these parameters correspond to the ones defined in that study. Otherwise, Atoll will use the graphs for which none of these parameters has been defined. If no such graph exists, Atoll will consider that the corresponding coding scheme is not defined during the calculations.

6.8.6.3

Using Coding Scheme Configuration in Transmitters and Terminals

In Atoll, a coding scheme configuration can be assigned to transmitters. If a coding scheme configuration is assigned on both the transmitter and terminal, Atoll takes the coding scheme configuration common to both and finds the possible modes, using the terminal-side thresholds if the defined thresholds are different on transmitter and terminal sides. If no coding scheme configuration is defined either at the transmitter or in the terminal, the transmitter will not be considered in certain quality indicators coverage predictions. To assign a coding scheme configuration to a transmitter: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign the coding scheme configuration. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter on the map and selecting Properties from the context menu.

5. Click the Configurations tab. 6. Under GPRS/EDGE Properties, select the GPRS/EDGE Transmitter check box. 7. Select the Coding Scheme Configuration from the list. To assign a coding scheme configuration to a terminal: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder. ) to expand the Terminals folder.

4. Right-click the terminal to which you want to assign the coding scheme configuration. The context menu appears. 5. Select Properties from the context menu. The terminals Properties dialogue appears. 6. Select the GPRS Configuration from the list.

6.8.6.4

Adapting Coding Scheme Thresholds for a Maximum BLER

You can have Atoll automatically calculate the reception and CI thresholds for a coding scheme configuration. You enter the acceptable Block Error Rate (BLER) in the coding scheme configurations Properties dialogue and Atoll calculates the thresholds required to ensure that the defined BLER is never exceeded. The admission threshold corresponds to 1 - BLER X max. throughout calculated for the coding scheme. To calculate the reception and C/I thresholds for a coding scheme configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings >Coding Schemes >Coding Scheme Configurations. The Coding Scheme Configurations table appears. 4. In the Coding Scheme Configurations table, right-click the record of the coding scheme configuration for which you Atoll to automatically calculate reception and CI thresholds. The context menu appears. 5. Select Record Properties from the context menu. The coding scheme configurations Properties dialogue appears. 6. Select the Thresholds tab. 7. Under Calculate the Thresholds to Get the Following BLER Value, enter a value in the BLER text box and click the Calculate button. Atoll calculates the thresholds required to satisfy the entered BLER. 8. Click OK to close the coding scheme configurations Properties dialogue and save the new threshold values.

6.8.6.5

Displaying Coding Scheme Throughput Graphs

In GPRS/EDGE technology, coding schemes are linked with data transmission redundancy levels. With coding schemes, two types of information is transmitted: user data and error correction data. There is a trade-off between accurate data transmission and transmission rates. Low error correction offers potentially higher transmission rates, but also a higher

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

413

Atoll User Manual risk of data loss. On the other hand, a high rate of error correction ensures safer data transmission, but means a lower transmission rate. Coding schemes are defined to obtain the best compromise between the transmission rate and the safety of the data sent. That is why each coding scheme has an optimum working range depending on either C or CI values. This optimum range can be seen in the coding scheme throughput graphs for each defined coding scheme configuration. The graphs show the throughput as a function of radio conditions (C and C/I) as calculated using block error rates. The graphs can help choose a coding scheme suitable to radio conditions. To display the graph of the throughput as a function of C or CI for a given coding scheme: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings >Coding Schemes >Coding Scheme Configurations. The Coding Scheme Configurations table appears. 4. In the Coding Scheme Configurations table, right-click the record describing the coding scheme configuration for which you Atoll to automatically calculate reception and CI thresholds. The context menu appears. 5. Select Record Properties from the context menu. The coding scheme configurations Properties dialogue appears. 6. Select the Thresholds tab. 7. Select the coding scheme for which you want to display a throughput graph and click one of the following: 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 interference due to intra-technology third-order intermodulation is taken into consideration, Atoll assumes that the CI graphs include the effect of this interference whereas the C graphs do not. 8. Click OK to close the dialogue.

6.8.7

Timeslot Configurations
You can create timeslot configurations that can be used to allocate different timeslot types to TRXs. A timeslot configuration describes how circuit, packet, and shared timeslots will be distributed in a subcell, depending on the number of TRXs. Shared timeslots are used for both circuit-switched and packet-switched calls. The distribution and definition of timeslot configurations have an influence on the network dimensioning results and the calculation of Key Performance Indicators (KPIs). Timeslot configurations are assigned to each TRX type of each cell type. If there is no timeslot configuration assigned to a TRX type, the fields defined at the subcell level "Number of packet (circuit or shared) timeslots" are used. In this section, the following is explained: "Creating or Modifying a Timeslot Configuration" on page 414.

6.8.7.1

Creating or Modifying a Timeslot Configuration

To create or modify a timeslot configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Timeslot Configurations. The List of Timeslot configuration table appears. 4. If you are creating a new timeslot configuration, enter the name of the timeslot configuration in the row marked with the New Row icon ( ). This name will appear in other dialogues when you select a timeslot configuration. If you are modifying an existing timeslot configuration, continue with the following step. 5. Select the row containing the timeslot configuration and click the Properties button. The timeslot configurations Properties dialogue appears. 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. 6. In the timeslot configurations Properties dialogue, 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.

414

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Note:

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.

7. Click OK to close the timeslot configurations Properties dialogue. 8. Click Close to close the List of Timeslot configuration table.

6.8.8

Advanced Transmitter Configuration Options

Atoll offers several options to help you configure more complex transmitter situations. These options are explained in this section: "Defining Extended Cells" on page 415 "Advanced Modelling of Multi-Band Transmitters" on page 415.

6.8.8.1

Defining Extended Cells

GSM cells usually cover an area within a 35 km radius. But, as user locations and their distances from the base station vary, and radio waves travel at a constant speed, the signal from users who are further than 35 km from the base station may be delayed by almost an entire timeslot. This delay creates interference with the signal on the adjacent timeslot. 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 can cover distances from 70 to 140 km from the base station. In a network with extended cells, Atoll will calculate coverage predictions from the extended cells defined minimum to maximum range, but will calculate interference caused by the extended cell beyond these ranges, inwards and outwards. To define an extended cell: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter for which you want to define an extended cell. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter on the map and selecting Properties from the context menu.

5. Click the TRXs tab. 6. Under Extended Cells, set a Min. Range and a Max. Range for the extended cell. 7. Click OK.

6.8.8.2

Advanced Modelling of Multi-Band Transmitters

In Atoll GSM/GPRS/EDGE projects, all subcells share the same frequency band by default. However, by changing an option in the atoll.ini file, you can model transmitters with more than one frequency band. For more information on changing options in the atoll.ini file, see the Administrator Manual. Once you have set the multi-band option in the atoll.ini file and restarted Atoll, you can modify the properties of existing transmitters to change them to multi-band transmitters or create a multi-band transmitter template. The relevant properties of all multi-band transmitters can be accessed in a special table. In this section, the following are explained: "Defining a Multi-Band Transmitter" on page 415 "Creating a Multi-Band Template" on page 416 "Accessing the Multi-Band Propagation Parameters Table" on page 418.

6.8.8.2.1

Defining a Multi-Band Transmitter

Each subcell on a transmitter is assigned a frequency domain. After making the necessary changes in the atoll.ini file, you must change the frequency domain of one or more non-BCCH subcells to a domain on a frequency band that is different from the frequency band used by the BCCH. You can then modify the frequency-band-specific settings: Antenna type, height, mechanical and additional electrical downtilt, Equipment losses Propagation models and path loss matrices.

This settings are taken into account in: Coverage predictions Traffic capture Dimensioning Interference matrices.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

415

Atoll User Manual To define the propagation settings for a frequency band used by a subcell: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter you want to change to a multi-band transmitter. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter on the map and selecting Properties from the context menu.

5. Click the TRXs tab. 6. Under Subcells, select "Standard" from the Display list. The standard table lists each TRX group defined in the cell type selected under Cell Type on the TRXs tab. 7. Change the Frequency Domain for one of the TRXs to a frequency band belonging to a different frequency band. 8. In the Subcells table, select the row of the TRX and click the Frequency Band Propagation button. The frequency band Properties dialogue appears. 9. 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 dialogue 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.

10. 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. 11. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Transmitters table. 12. Click OK.

6.8.8.2.2

Creating a Multi-Band Template

If you will be creating new multi-band base stations, you can first create a multi-band template with the necessary parameters, including the propagation model parameters for each subcell using a different frequency band. When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. Note: 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 404.

It is assumed that you have already set the multi-band transmitter option in the atoll.ini file and restarted Atoll before beginning this procedure. To create a multi-band template: 1. In the Radio toolbar, click the arrow to the right of the list of templates. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Under Station Templates, select the station template that most closely resembles the station template you want to create and click Add. The Properties dialogue appears. 4. Create the multi-band template: a. Click the General tab of the Properties dialogue. b. In the Name text box, give the template a descriptive name. c. From the Cell Type list, select the multi-band cell type that corresponds to the type of station template you are creating.

416

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks d. Make any other necessary changes to the station template parameters. For information on the parameters available, see "Creating or Modifying a Station Template" on page 204. e. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes. 5. Set the propagation parameters for each frequency band in the multi-band template: a. Select the multi-band template you have just created and click Add. Because the station template you selected is a multi-band template, the New Station Template dialogue appears with the following options (see Figure 6.239): 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.

Figure 6.239: New Station Template dialogue b. Select Add a new multi-band station template for the frequency band, choose a frequency band from the list and click OK. A properties dialogue appears. On the General tab, you can set the antenna and propagation parameters for the selected frequency band (see Figure 6.240): Under Main Antenna, you can modify the following: the antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Height of the antenna 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 Mechanical Downtilt, and the Additional Electrical Downtilt. Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

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 Specifications dialogue which appears when you click the Equipment button. For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 193.

Figure 6.240: Properties dialogue for frequency band of a multi-band template 6. Click OK. The properties defined for the frequency band appear in the Station Template Properties dialogue with a name composed of the multi-band template they belong to followed by the frequency band, separated by "@". 7. Repeat step 5. for every frequency band modelled by the multi-band template.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

417

Atoll User Manual

6.8.8.2.3

Accessing the Multi-Band Propagation Parameters Table

In a GSM/GPRS/EDGE multi-band document, you can access the properties of all multi-band transmitters using the MultiBand Propagation Parameters table. To open the Multi-Band Propagation Parameters table: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > Multi-Band Propagation Parameters from the context menu. The Multi-Band Propagation Parameters table appears. Multi-band transmitters are identified in the Transmitter column, with the subcells using a frequency band other than the main frequency band for that transmitter identified with a name composed of the multi-band transmitter they belong to followed by the frequency band, separated by "@".

6.8.9

GSM/GPRS/EDGE Multi-Service Traffic Data

In Atoll, you can define the traffic data in the GSM/GPRS/EDGE network. The data will be used in different network calculations, such as, dimensioning and coverage predictions. In this section, the following are explained: "Modelling GSM/GPRS/EDGE Services" on page 418 "Modelling GSM/GPRS/EDGE Mobility Types" on page 419 "Modelling GSM/GPRS/EDGE Terminals" on page 419.

6.8.9.1

Modelling GSM/GPRS/EDGE Services

You can model both circuit and packet-switched GSM/GPRS/EDGE services. In this section, the following are explained: "Creating or Modifying a GSM/GPRS/EDGE Service" on page 418 "Displaying the GSM/GPRS/EDGE Services Table" on page 419

6.8.9.1.1

Creating or Modifying a GSM/GPRS/EDGE Service

You can define the various user services in GSM/GPRS/EDGE documents. The services can be circuit-switched or dataswitched. Currently the only circuit-switched service in a GSM/GPRS/EDGE network is a GSM voice service that uses a single timeslot. The quality requirement parameters of services are mostly used in the dimensioning process. To create or modify a service: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. Note: You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.

5. You can modify the following parameters: Name: Atoll proposes a name for the new service, but you can change the name to something more descriptive. 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). 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. Min. Throughput or Guaranteed Bit Rate (per User): The minimum throughput (or the guaranteed bit rate for constant bit rate packet-switched services) per user is used in the dimensioning process for GPRS/EDGE networks. 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: The maximum number of timeslots is used during dimensioning to limit the number of timeslots that can be assigned to a user using this service. This parameter applies to packetswitched services. In case of Constant Bit Rate packet-switched services such as VoIP, this parameter has to be set to 1. Under 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 RLC/MAC throughput or timeslot coverage prediction. These parameters model header information and other supplementary data that do not appear at the application level.

6. Click OK.

418

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.8.9.1.2

Displaying the GSM/GPRS/EDGE Services Table

You can display the parameters of all the services in the Services table. You can modify any of the parameters or create a new service. To display the Services table: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select Open Table from the context menu. The Services table appears. For information on working with tables in Atoll, see "Working with Data Tables" on page 53.

6.8.9.2

Modelling GSM/GPRS/EDGE Mobility Types

In a multi-layer GSM/GPRS/EDGE network, the speed the user is travelling is one of the most important criteria in allocating the user to a server. A mobile user travelling at a high speed is usually allocated a channel on the macro layer rather than on the micro layer in order to minimise signalling and system load and to spread the traffic over several layers. In this section, the following are explained: "Creating or Modifying a GSM/GPRS/EDGE Mobility Type" on page 419 "Displaying the GSM/GPRS/EDGE Mobility Types Table" on page 419.

6.8.9.2.1

Creating or Modifying a GSM/GPRS/EDGE Mobility Type

To create or modify a mobility type: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

3. Right-click the Mobility Types folder. The context menu appears. 4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears. Note: You can modify the properties of an existing mobility type by right-clicking the mobility type in the Mobility Types folder and selecting Properties from the context menu.

5. You can modify the following parameters: Name: Atoll proposes a name for the new mobility type, but you can change the name to something more descriptive. Speed: The average speed of the mobility type. In a hierarchical network, a maximum speed is defined for each HCS (Hierarchical Cell Structure) layer. Any mobility that exceeds the defined maximum speed will not be captured by that layer but passed on to the layer above.

6. Click OK.

6.8.9.2.2

Displaying the GSM/GPRS/EDGE Mobility Types Table

You can display the parameters of all the mobility types in the Mobility Types table. You can modify any of the parameters or create a new mobility type. To display the Mobility Types table: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

3. Right-click the Mobility Types folder. The context menu appears. 4. Select Open Table from the context menu. The Mobility Types table appears. For information on working with tables in Atoll, see "Working with Data Tables" on page 53.

6.8.9.3

Modelling GSM/GPRS/EDGE 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. In Atoll, a terminal is modelled in terms of its GSM and GPRS/EDGE-relevant parameters. In this section, the following are explained: "Creating or Modifying a GSM/GPRS/EDGE Terminal" on page 419 "Displaying the GSM/GPRS/EDGE Terminals Table" on page 420.

6.8.9.3.1

Creating or Modifying a GSM/GPRS/EDGE Terminal

To create or modify a terminal: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

419

Atoll User Manual 3. Right-click the Terminals folder. The context menu appears. 4. Select New from the context menu. The Terminals New Element Properties dialogue appears. Note: You can modify the properties of an existing terminal by right-clicking the terminal in the Terminals folder and selecting Properties from the context menu.

5. You can modify the following parameters: Name: Atoll proposes a name for the new terminal, but you can change the name to something more descriptive. Main Band: The primary frequency band with which the terminal is 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 multiband 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.

If you chose "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. Note: 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: If the terminal is GPRS or EDGE-compatible, you can enter the maximum number of downlink timeslots the terminal can use. Terminals using only circuit-switched services will use only one downlink timeslot. Using more than one DL timeslot has an effect in the dimensioning process (see "Dimensioning a GSM/GPRS/EDGE Network" on page 267 for more information). 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 (see "Dimensioning a GSM/GPRS/EDGE Network" on page 267 for more information). Note: 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 C/I) graphs.

6. Click OK.

6.8.9.3.2

Displaying the GSM/GPRS/EDGE Terminals Table

You can display the parameters of all the terminals in the Terminals table. You can modify any of the parameters or create a new terminal. To display the Terminals table: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select Open Table from the context menu. The Terminals table appears. For information on working with tables in Atoll, see "Working with Data Tables" on page 53.

420

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.8.10

Defining the Interferer Reception Threshold

In Atoll, you can define a limit on the received signal level. 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 studies can be improved. As well, the performance of calculations using the Interference tab 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 will discard all interferers with a signal level lower than this value. To define the interferer reception threshold: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Predictions tab. 5. Under Calculation Limitation, enter an Interferer Reception Threshold in dBm. 6. Click OK.

6.8.11

Advanced Modelling of Hopping Gain in Studies

Using frequency hopping has an advantage from the point of view of interference in the way interference can be smoothed over several frequencies. In addition, radio link resistance to fast fading is increased and its efficiency is optimised. Because this effect of hopping can be noticed on voice quality and on throughput, you can define specific admission thresholds for codec modes and coding schemes according to specific MAL lengths. If you want Atoll to take advanced modelling of hopping gains in coverage predictions, the administrator (or you, if you have administrator rights) has to add the field MAL_LENGTH to the CodecQualityTables and EGPRSQuality tables. Adding this custom field provides a MAL_LENGTH column in the definition of each codec configuration (Quality Graphs tab) and each coding scheme configuration. For codec configurations, it means that you can define a specific codec mode graph per MAL length where the graph efficiency increases as the MAL length increases, too (see Figure 6.241 on page 421).

Figure 6.241: 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) Coverage Prediction" on page 335), 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 6.242 on page 422).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

421

Atoll User Manual

Figure 6.242: Coding Scheme Configuration Properties (with MAL length definition) In GPRS/EDGE coverage predictions (see "Packet-Specific Coverage Predictions" on page 328), 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.

For a more precise description of these fields, see the Administrator Manual.

6.8.12

Taking Intermodulation Interference into Consideration in Calculations

Intermodulation interference is the result of two or more signals of different frequencies combined. When two or more signals of different frequencies combine, they generate additional signals at frequencies that are not harmonic frequencies (integer multiples) of the frequencies of the original signals. Intermodulation is not desirable in mobile networks as it creates spurious emissions which can create minor to severe interference. Odd-order intermodulation products are of the most interest because they are in the vicinity of the original frequency components, and could therefore interfere with useful signals. The third-order intermodulation product has the highest amplitude among all odd-order intermodulation products. If you want Atoll to take third-order intermodulation into consideration when calculating total interference, you have to add some optional fields to the data structure. For more information on which fields to add and to which tables, see the Administrator Manual.

6.8.13

Modelling Shadowing
Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be greater and in 50% of the measured cases, the result will be worse. Atoll uses a model standard deviation with the defined cell edge coverage probability to model the effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. 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.

422

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks In GSM/GPRS/EDGE projects, the standard deviation of the propagation model is used to calculate shadowing margins on signal levels. You can also calculate shadowing margins on CI. For information on setting the model standard deviation and the CI standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 121. Shadowing can be taken into consideration when Atoll calculates the signal level (C) and the signal-to-noise ratio (CI) for: A point analysis (see "Making a Point Analysis to Study the Profile" on page 215) A coverage prediction (see "Studying Signal Level Coverage" on page 216, "Interference Coverage Predictions" on page 320, "Packet-Specific Coverage Predictions" on page 328, and "Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction" on page 335) Neighbours (see "Allocating Neighbours Automatically" on page 243) Traffic capture (see "Calculating and Displaying a Traffic Capture" on page 262).

You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter Class" on page 423.

6.8.13.1

Displaying the Shadowing Margins per Clutter Class

To display the shadowing margins per clutter class: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears (see Figure 6.243). 4. You can set the following parameters: Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin: 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.

5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.

Figure 6.243: The Shadowing Margins dialogue

6.8.14

Modelling the Co-existence of Networks

In Atoll, you can study the effect of interference received by your network from other GSM/GPRS/EDGE networks. The interfering GSM/GPRS/EDGE network can be a different part of your own network, or a network belonging to another operator. To study interference from co-existing networks: 1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a Group of Base Stations" on page 208. 2. For the interfering networks transmitters, set the Transmitter Type to Extra-Network (Interferer Only) as explained in "Transmitter Description" on page 193. During calculations, Atoll will consider the transmitters of type Extra-Network (Interferer Only) when calculating interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interference.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

423

Atoll User Manual Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network. If the interfering network is a part of your own network, this information would be readily available. However, if the interfering network belongs to another operator, the information available might not be accurate.

6.8.15

Modelling Inter-Technology Interference

Analyses of GSM networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a GSM network. Atoll can take into account interference from coexisting networks in calculations. 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) may be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (CDMA, TDMA, OFDM). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-Technology IRFs" on page 424. Interference from external mobiles (also called uplink-to-downlink interference) may be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your GSM 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 TRX in the GSM network. This noise rise is taken into account in all interference-based calculations. For more information on the Inter-technology DL Noise Rise, see "TRX Definition" on page 200.

Figure 6.244: Interference received by mobiles on the downlink

6.8.15.1

Defining Inter-Technology IRFs

Interference received from external base stations on mobiles of your GSM 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 An IRF depends on: The interfering technology (TDMA, CDMA, and OFDM) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).

IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your GSM document, i.e., when Atoll is in co-planning mode. To define the inter-technology IRFs in the victim network: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Inter-technology IRFs from the context menu. The Inter-technology Interference Reduction Factors table appears. 4. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: Technology: Select the technology used by the interfering network. Interferer Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfering network. This channel width must be consistent with that used in the linked document. Victim Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfered network. This channel width must be consistent with that used in the main document.

424

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Reduction Factors (dB): Click the cell corresponding to the Reduction Factors (dB) column and the current row in the table. The Reduction Factors (dB) dialogue appears. Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document.

Notes: Reduction values must be positive. Undefined reduction factors are assumed to be very high values. Click OK. The interference reduction factors are stored.

6.9

The Atoll AFP Module

The main role of the Atoll Automatic Frequency Planner (AFP) is to assign frequencies (i.e., channels) to the network in such a way that overall network quality is optimised. With the evolution of GSM over the years to integrate many improvements, additional requirements have emerged in the process of radio network planning. The implementation of baseband and synthesised frequency hopping, discontinuous transmission, and network synchronisation, for example, has led to greater sophistication in the process of frequency planning. These enhancements require that the AFP be advanced enough to help the frequency planner throughout the entire task. The Atoll AFP takes a large number of constraints and directives into consideration, for example, ARFCN separation requirements between transmitters, interference relations, HSN assignment methods, frequency domain constraints, a given fractional load to maintain, etc. The AFP depends on a variety of input data, such as the interference matrix, neighbour relations, traffic information, etc. Before continuing, ensure that you are familiar with the prerequisite information explained in "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 270. In the previous chapters, the basic elements of the AFP usage were presented. In this chapter, we will depict the more advanced aspects, as well as what is specific to Atoll's AFP module. It will therefore not be relevant to a third party AFP module. As in previous chapters, the content is presented according to the sophistication level you will be targeting. It is presented in that way in order to help the users that are looking for a simple and fast frequency solution. Therefore this section is organized according to the level of complexity: "Basic Atoll AFP Use" on page 425 "Using the Atoll AFP" on page 427 "Advanced AFP usage" on page 445.

6.9.1
6.9.1.1

Basic Atoll AFP Use

In this section, you will find the information necessary to run the Atoll AFP to solve a simple problem, or to evaluate a hypothetical situation "What if" scenario.

Using the Atoll AFP in a simple way

If you do not know a lot about the AFP cost function or how its parameters are set, you can use the Atoll AFP with its default values. If you are new to the Atoll AFP, it is very important that you follow the recommendations given in this section. The only parameter you should alter, if you are new to the Atoll AFP, is the cost weight of modifying a TRX and the intermodulation tax. The other settings of the AFP model should be left as is. It is assumed that the data you have available is consistent. To set the parameters of the Atoll AFP module in a simple way: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to the left of AFP Modules folder to expand the folder. 3. Right-click the Atoll AFP Module folder. The context menu appears. 4. Select Properties from the context menu. The Atoll AFP Module Properties dialogue appears. 5. Select the Cost tab (see Figure 6.245).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

425

Atoll User Manual

Figure 6.245: The Cost tab of the AFP Module Properties dialogue 6. Select the Modified TRX check box to restrict the number of modifications to the existing plan. 7. Select the Intermodulation Tax check box in order to try avoiding these products. 8. Click OK to save your changes to the AFP Module and close the AFP Module Properties dialogue. All the other AFP settings must keep their default values. To avoid risks and to keep the AFP process simple: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Automatic Allocation from the context menu. The AFP dialogue appears with the AFP Selection tab. 4. In the first page af the AFP wizard, do not select any allocation strategy and do not allocate any performance indicators then click Next, 5. In the second page of the AFP wizard, do not change the separation rules and do not define any exceptional pairs then click Next, 6. In the third page of the AFP wizard, extract the traffic data from the subcells table. Do not make possible DTX and do not use any locking option 7. Click OK. 8. In the following dialogue, define the Target Calculation Time for a relatively short period. If you have fewer than 20 transmitters, set the TCT for about 2 minutes. If you have many transmitters, around 3,000 for example, set the TCT for about 200 minutes.

For more information on running an automatic frequency allocation, see "Automatic Resource Allocation Using an AFP Module" on page 299.

6.9.1.2

The Atoll AFP Cost Definition

The Atoll AFP cost function maps two frequency plans (the initial and the final frequencies plans) to a single number: the AFP cost. The Atoll AFP cost function has two roles: It is a directive. It defines what the AFP has to do. It is an understandable unit by which you can see what is going on in the network.

Atoll's AFP cost function has the advantage of being TRX-based. It is calculated for each TRX and then added up. It corresponds to the served traffic of each TRXs. When you use the AFP at the most basic level, you should not worry too much about the cost function. The only thing that is important is that the actual cost is reduced. If the actual cost does not go down, or if you want to reduce the cost even more, see "An Overview of the AFP Cost Function" on page 427 for more information about the cost function.

426

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.9.1.3

The Atoll AFP Algorithm

The Atoll AFP module is implemented using simulated annealing, taboo search, graph heuristics, and machine learning. It manages its time resources to match the target calculation time defined by the user. If the target calculation time is high, the module will use part of this time to "learn" the network. During the learning phase, the module adjusts its internal parameters. After the learning phase, the AFP will switch to a randomised combinatorial search phase. The Atoll AFP module performs network learning by executing many fast and deterministic instances of the AFP. The instance that results in the best performance can be memorised both in the document and in the database. If this experience is conserved, the next time that an AFP is executed, it will start where the learning process ended: it will use the parameter profile of the best solution stored in the AFP model. For more information on how storing network learning improves the algorithm, see start here XREF. The most important part of network learning is the parameters controlling trade-offs between the various parts of the algorithm. For example, you can base candidate selection on interference only by choosing frequencies that do not interfere and are not interfered. Or you can base candidate selection on availability reduction only by choosing frequencies that do not reduce the availability of non-interfered frequencies in the surrounding TRXs. In Atoll's AFP the two criteria are combined and their relative weight is part of the AFP experience.

6.9.2

Using the Atoll AFP

This section will be much longer than the last one. It contains all the basic things about the AFP that you must know in order to successfully work with it. Starting with the cost function, going through the AFP property pages, and finishing with the frequency hopping functionality.

6.9.2.1

An Overview of the AFP Cost Function

In this section, the following are explained: "The Cost Function as a Combination of Separation Violation and Interference Probabilities" on page 427 "Counting Bad TRXs (Nodes) Instead of Bad Relations (Edges)" on page 427 "The Cost of Each TRX" on page 428 "Cost of Each Subcell" on page 428 "An Example of Separation Violation Cost with Frequency Hopping" on page 428 "Interference Cost" on page 429 "Probabilistic Cost Combination" on page 430 "The Cost of Missing and Corrupted TRXs" on page 430 "Cost of Out-of-domain Frequency Assignment" on page 431 "Preferred Group Cost" on page 431 "Preferred Group Cost" on page 431 "Quality Target" on page 432 "AFP Shadowing" on page 432.

6.9.2.1.1

The Cost Function as a Combination of Separation Violation and Interference Probabilities

The cost function of the Atoll AFP has two main components. The first component is the cost for violations of separation constraints and the second component is the cost of creating interference. The Atoll AFP gives each separation violation the cost equivalent to a certain amount of interference, making it possible to add both costs and minimize their total. For example, you can decide that a separation violation of 1 costs the same as x% of interfered traffic. This is weighted by the type of violation (for example, co-transmitter separation violations have a higher impact than neighbour separation violations). By defining equivalence between these dissimilar measurements, you can add sum separation violation and interference costs with their common unit, i.e., the percentage of interfered traffic. Following this principle, all other cost elements are calculated in the same way: The cost component due to allocation changes The cost component of allocating TRXs that belong (or not) to a preferred frequency group (if such a group is indeed defined) The cost component of missing or extra TRXs compared to the number of required TRXs The cost component of corrupted TRXs The cost component of assigned frequencies that are not in the domain The cost component of blocked traffic (calculated only when you set the AFP to optimise the number of required TRXs) The cost component due to intermodulation effect.

6.9.2.1.2

Counting Bad TRXs (Nodes) Instead of Bad Relations (Edges)

In the following example, each separation violation represents an edge and each TRX a node. The two frequency plans proposed in this example do not respect all separation requirements for all TRXs, meaning that they all have bad nodes and bad edges. They demonstrate the difference between minimizing the number of bad edges or the number of bad nodes. The network in this example consists of 6 TRXs, all having a separation constraint of 1 with each other (i.e., 6 nodes, 15 edges):

Case 1

Case 2

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

427

Atoll User Manual F1 is used 4 times; F2 and F3 are used one time each. Number of separation violations is 6 (6 bad edges) Two TRXs have a good assignments The spectrum is not equally used F1, F2, and F3 are used two times each. Number of separation violations is 3 (3 bad edges) No TRX has a good assignment The spectrum is equally used

This example shows the particularity of the node-oriented cost approach. Atoll AFP 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. A greater capacity to optimise the number of TRXs. The ability to respect a TRX-based quality target, i.e., to disregard interference at a TRX that does not equal a certain value (for more information, see start here XREF).

The node-oriented approach is an important feature of the Atoll AFP and provides a tighter correspondence between the AFP cost and the network quality.

6.9.2.1.3

The Cost of Each TRX

The AFP cost function is added up for each TRX according to the following logic: 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 432).

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.

6.9.2.1.4

Cost of Each Subcell

When you use the AFP to optimise the number of required TRXs, the cost function is adapted in a certain way: The traffic load becomes dependent on the number of TRXs. And, moreover, a blocked cost component is used. For the purposes of this section, you can assume that the cost of each subcell corresponds to all cases where the allocation strategy does not include the optimisation of the number of TRXs. For more detailed information on the changes in the cost of each subcell, see start here XREF. Note: The AFP cost is the cost of the entire loaded network, not only the cost of the selected or non-locked TRXs. In many cases, the AFP is authorized to change only a part of the network. Therefore, the part of the cost corresponding to the non-locked part of the network and the part of the cost corresponding to the locked part of the network are indicated.

6.9.2.1.5

An Example of Separation Violation Cost with Frequency Hopping

In this example, the interference cost is ignored in order to make the separation violation cost easier to understand. The example uses a TRX with only one separation. In this example, Sij represents the required separation between two transmitters. If f1 is assigned at i and f2 at j such that , the separation constraint is not satisfied. Separation constraints can be violated strongly or weakly. For example, the pair of frequencies 1 and 2 violates a separation requirement of 3. The pair of frequencies 1 and 3 violate this requirement as well but is still a better solution than 1 and 2 and, therefore, should have a lower cost. Frequencies that are part of a MAL with a low fractional load and that violate a separation constraint, should not be weighted the same as for non-hopping separation violations. In fact, the separation component is weighted by the burst collision probability, which is the multiplication of the victim's fractional load and the interferer's fractional load.

428

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.246: The Separation tab of the AFP Module Properties dialogue In this example, there is a network with two TRXs in the same cell. The first, TRXi, has a MAL refered 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 6.246 on page 429. Because only one channel of each TRX causes interference, and the length of MALi is 5 and the length of MALi is, 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 hopping gain table in the "advanced" property page of the AFP. 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: . For TRXi, this resulting gain is 4.5%/1.38, or 3.25%. 1 90 For TRXk, the cost will be ----- ------------------------ = 3.41% . The cost will be a little larger because the gain is smaller. 20 10 ( 1.2 10 ) 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 together. Note: 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.

6.9.2.1.6

Interference Cost
Traffic on a TRX is interfered if and only if interfering transmittes have co/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. In the following example, how a single interference cost element is calculated is explained. 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 6.247.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

429

Atoll User Manual

Figure 6.247: 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 Subcell 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, the AFP weight. For more information, see the cost function formula in start here (todo put ref XXXXX)

6.9.2.1.7

Probabilistic Cost Combination

In this example, TRX is subject to a separation violation causing a cost of 30% of T( )(where T( ) is an estimate of the traffic time slots for TRX weighted by the AFP weight for this TRX) and in addition, a co/adjacent-channel reuse causing this TRX to be 40% interfered. These costs are combined using a probabilistic approach. In this example, the probabilities of these costs occurring are p(Violation) with a value of 0.3 and p(Interference) with a value of 0.4. The cost of the two together is given by: 1 ( 1 p ( violation ) ) ( 1 p ( Interference ) ) = 0.58 or 58% P1, P2, .Pn are the costs of the probability of a violation of aTRX (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: The cost of separation for this TRX is therefore: 1 The additional cost of this TRX is: 1
m+1

i=1

( 1 Pi )
i=1

i=1

( 1 P i ) 1

( 1 Pi )

The interference cost uses the "min C/I" value, defined at subcell level, for which it may have precise pair-wise interference information. It may apply various gains to this C/I quality target due to frequency hopping and/or DTX.

6.9.2.1.8

The Cost of Missing and Corrupted TRXs

It is easy to have a 0-cost solution if the criterion of the required number of TRXs is not fulfilled (for example, by removing all TRXs). This is the main purpose of the missing TRX cost. By default, the exact traffic that a missing TRX was supposed to carry will be counted as a cost. However, you can increase this cost (by 200% for example) if necessary. Corrupted TRXs are TRXs where the assignment is unusable by the AFP. A few xamples of corrupted TRXs would be: TRXs with an empty channel list A TRX with a MAL without HSN or without a MAIO for synthesised hopping. A TRX assigned an invalid frequency, for example, "-32UT-222DL" or "26Mhz." A non-hopping or base-band hopping TRX with a MAL that has more than one frequency.

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.

430

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Note:

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).

6.9.2.1.9

Cost of Out-of-domain Frequency Assignment

If a TRX is assigned out-of-domain frequencies (channels) but has correct ARFCNs, it will have a double influence on the cost: The usual cost of interference, separation or modification, and An additional cost of having out-of-domain channels, multiplied by the number of frequencies out of domain and divided by the MAL length.

6.9.2.1.10

Preferred Group Cost

If a subcell's allocation strategy is group constrained, or if it's hopping mode is synthesized hopping, the subcell could be influenced by a preferred frequency group in the following ways: 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. Moreover, 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).

6.9.2.1.11

Intermodulation Cost
This cost component has the goal of avoiding the cases were intermodulation can cause problems. It is therefore slightly stricter than the real cases where intermodulation effects occurs. The intermodulation violations are summarized as a tax, since they always have relatively low interference probabilities. The Tax is applied when the combinations of allocated frequencies generates a frequency already allocated within the same site. Depending on the type of combination (order, harmonics, various amplification spreading violation), if the combination of DL frequencies may affect or not UL frequencies, or if the intermodulation may take place within a same site, BTS or equipment, this tax is weighted accordingly. Each ARFCN carrier number refers to 2 physical frequencies: the uplink frequency and the downlink frequency. The translation function from ARFCN to frequency is given by the ARFCN standard. Each physical frequencies used in a site could be subject to a second (or third) order or a VASP (Various Amplification Spreading Violation) inter-modulation separation violation. In the case of 2 frequencies, X and Y where X < Y, a separation constraint will exist according to the following table:

Constraint Order
Second order (Harmonics) VASP

Condition
Y=2X Y < X + 600 kHz

Constraint applied to
X and Y X and Y

In the case of 3 frequencies, f1, f2, f, a separation constraint will exist according to the following table:

Constraint Order
Second order Third order

Condition
f=f1+f2 f=2f1-f2 f=f1-2f2

Constraint applied to
f, f1 and f2 f, f1 and f2

The tables above summarize 5 types of violations. Each type will therefore have a weight. By default:

Constraint Type
Second Order Harmonics VASP Third order

Weight
0.02 0.01 0.0002 0.002

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

431

Atoll User Manual The costs, as explained up to now, is summed up as a tax, and is weighted by the inter modulation weight W, the UL/DL component, and the equipment sharing weight. In each intermodulation violation there is an interfering frequency (or frequencies) and an interfered frequency. In all the equations above 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. In the harmonic case, two equations are depicted for this reason. We assume that the generator frequencies are all Uplink or are all 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
DL

Interfered Frequencies
UL

Weight
5

Description
High power amplification pollution penetrates into the RX, causing an important noise rise High power received signals generate an inter modulation product on a weekly received interfered frequency Downlink power control is active over the interfered frequency yet is not active over the generators, which generate high noise on the interfered signal This type of interaction can be ignored

UL

UL

DL

DL

UL

DL

Finally, the last weighting concerns the equipment sharing. This aspect has a crucial effect on the importance of the intermodulation. In Atoll, we assume that site sharing = BTS sharing, and that feeder + antenna sharing = co-cell cohabitation. In the case of Co-cell inter modulation (generating frequencies as well as IM product belong to the same cell) the inter modulation cost is multiplied by 5.

6.9.2.1.12

Quality Target
It is often necessary to deal with small and large amounts of interference in different manners. 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. The Cost section of the Atoll AFP Properties dialogue that sets the Atoll AFP to dismiss interference and separation costs that do not add up to the value of the parameter % Max Interference set in the Subcells table for each subcell. TRXs that have a lower percentage of interference than % Max Interference are considered to have no interference and are excluded from the cost. For more information on defining the parameters of the Atoll AFP, see start here XREF. This option can be used to distribute interference equally among some transmitters instead of having a few with very low interference and others with high interference.

6.9.2.1.13

AFP Shadowing
AFP shadowing is an important feature usually enabled by default on the Protection tab of the AFP Properties dialogue. It is so important that in some cases it is enabled automatically, for example, if the interference matrixes 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 429.

6.9.2.2

Setting the Parameters of the Atoll AFP Module

You can define the Atoll AFP-specific parameters used when calculating the cost and set some guidelines for the Atoll AFP module by using the Atoll AFP Module Properties dialogue. To open the Atoll AFP module Properties dialogue: 1. Click the Modules tab of the Explorer window. 2. Click the Expand button ( ) to the left of AFP Modules folder to expand the folder. 3. Right-click the Atoll AFP Module folder. The context menu appears. 4. Select Properties from the context menu. The Atoll AFP Module Properties dialogue appears. The AFP Properties dialogue 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 Execution 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 AFP module and set different parameters for each copy (for information on copying modules, see start here XREF). All copies will be available in AFP sessions. In other words, you will be able to choose from the list of all AFP modules, each with its own defined parameters.

432

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks The settings of each 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 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: "The Atoll AFP General Tab" on page 433 "The Atoll AFP Cost Tab" on page 433 "The Atoll AFP Separation Weights Tab" on page 434 "The Atoll AFP Interference Matrices Tab" on page 435 "The Atoll AFP HSN Tab" on page 436 "The Atoll AFP MAL Tab" on page 437 "The Atoll AFP Execution Tab" on page 438 "The Atoll AFP Spacing Tab" on page 439 "The Atoll AFP Protection Tab" on page 440 "The Atoll AFP Advanced Tab" on page 442

6.9.2.2.1

The Atoll AFP General Tab

The General tab of the Atoll AFP Module Properties dialogue enables you to change the name of the AFP module. For example, if you have created a copy of the Atoll AFP and modified some parameters in order to customise the copy for a specific situation, you can give the copy a descriptive name. To display the General tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the General tab. 3. Change the Name of the Atoll AFP module.

6.9.2.2.2

The Atoll AFP Cost Tab

The Cost tab of the Atoll AFP Module Properties dialogue enables you to define the different components that make up the global cost. A component will be taken into consideration by the AFP if it is selected. If its cost or weight is "0," it will not be taken into consideration. The most important parameters on this tab are the interference and separation weights. These are used as multiplicative factors for each incidence of interference or violation. In other words, these parameters can reduce cost. If these two parameters have low values (for example, 0.1 for interference and 0.035 for separation), AFP will be forced to work using an edge-oriented strategy, which is probably not the best approach. By default, interference costs are less important than separation violation costs. The second most important parameter is the cost of modifying a TRX. This parameter should be set if the non-locked part of the network is to be changed as little as possible. The example in the following table shows how this parameter can affect total costs. In this example, there is a network with a total of 90 transmitters. 15 of these transmitters are locked. Out of a total of 257 required TRXs, only 193 good TRXs have already been allocated. This leaves 64 TRXs that will have to be created and allocated affecting the other 193 as little as possible:

Cost
For a cost of changing a TRX = 1 For a cost of changing a TRX = 0.3 For a cost of changing a TRX = 0.1 For a cost of changing a TRX = 0

Effect
AFP changed only 98 TRXS AFP changed only 129 TRXS AFP changed only 139 TRXS AFP changed 162 TRXS

Selecting the Take into account all the TRXs check box makes the AFP take the cost of all the 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. The last part of this page corresponds to the optimisation of the number of TRXs, if will therefore be depicted in the advanced part. To display the Cost tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in ""Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the Cost tab (see Figure 6.248).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

433

Atoll User Manual

Figure 6.248: AFP Module Properties dialogue - Cost tab 3. Under Cost per TRX, set the following parameters: 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 TRX with frequencies outside its domain: 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 Cost (order 2 and 3) check box to make it active and set the tax each applied to the total cost each time intermodulation may 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 429. 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 428. 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 430. Out of 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 431.

6. If desired, select the Take into account all TRXs check box to make it active. When you make the Take into account all TRXs option active, the Atoll AFP takes the interfence of all TRXs into account. This option is used to distribute interference equally among some transmitters instead of having a few with very low interference and others with high interference. For more information, see "Quality Target" on page 432. 7. Under Optimisation of the number of TRXs, select the traffic source the AFP will use during optimisation: Based on traffic load and respecting a maximum blocking rate of: If you choose to use the traffic load, enter a blocking rate. Based on the traffic demand (from the subcell table or default traffic capture): If you choose to use the traffic demand, the AFP will use either the traffic demand defined in the Subcell table or the default traffic capture (depending on what you select when you run an AFP optimisation.

6.9.2.2.3

The Atoll AFP Separation Weights Tab

The AFP Separation Weights tab of the Atoll AFP Module Properties dialogue enables you to define a weight for each type of separation constraints violation or partial violation. You can assign a weight between 0 and 1 for the following types of separation constraint violations: Co-cell separation violations

434

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks Co-site separation violations Neighbourhood separation violations Exceptional pair separation violations

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 in case of a partial separation constraint violation. You can also add and remove different. To display the Separation Weights tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the Separation Weights tab (see Figure 6.249).

Figure 6.249: AFP Module Properties dialogue - Separation Weights tab 3. Under Partial Separation Constraint Violations, you can edit the conditions defining a partial separation constraint. You can have up to 7 separations. To edit the separation conditions: a. Click the Expand button ( ) to the left of the separation. b. Click the entry in the Value column and enter a percentage corresponding to the amount of traffic. To remove a separation: 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.

4. Under Partial Separation Constraint Violations, you can edit the conditions defining a partial separation constraint. You can have up to 7 separations. 5. If desired, modify the weight for each of the following: Co-transmitter Violations Co-site Violations Violations between Neighbours Violations between Exceptional Pairs

6.9.2.2.4

The Atoll AFP Interference Matrices Tab

The Interference Matrices tab of the Atoll AFP Module Properties dialogue enables you to define weights that are used to control the combination of interference matrices. The Interference Matrices tab of the Atoll AFP Module Properties dialogue enables you to define weights that are used to control the combination of interference matrices.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

435

Atoll User Manual The Atoll AFP combines interference matrices by first loading the part of active interference matrices that intersects the scope of the AFP. The AFP then combines the information by performing a weighted average of all entries for each pixel. The weighted average is calculated by multiplying the following three components present on the Interference Matrices tab: Belonging to the scope of the AFP The type of interference matrix The interference matrix quality indicators

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 dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the Interference Matrices tab (see Figure 6.250).

Figure 6.250: AFP Module Properties dialogue - Interference Matrices tab The first component in combining interference matrices is whether a given interference matrix entry is part of the scope of the AFP scope. 3. Under The type of interference matrix, define the parameters for each section: Overlapping area based on propagation matrices As a fraction of the surface As a fraction of traffic Signal level measurements (RXLEV) only between neighbours Signal level measurements (RXLEV) + extended neighbourhoods Based on reselection Based on drive test data Based on CW measurements Based on scan measurements

OMC Statistics

Measurement Analysis

4. Under The interference matrix quality indicators, select the Active check box if you want the Atoll AFP to include the quality matrix specific to each type of interference matrix when combining interference matrices.

6.9.2.2.5

The Atoll AFP HSN Tab

The HSN tab of the Atoll AFP Module Properties dialogue enables you to define how the HSN will be allocated when synchronised frequency or base-band hopping is used. For detailed information on hopping parameters, see XREF.

436

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks To display the HSN tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the HSN tab (see Figure 6.251).

Figure 6.251: AFP Module Properties dialogue - HSN tab 3. Under Allocation, select how the HSN will be allocated: By Subcell By Transmitter By Site Free.

6.9.2.2.6

The Atoll AFP MAL Tab

The MAL tab of the Atoll AFP Module Properties dialogue enables you to define Mobile Allocation List patterns and length priorities when synchronised frequency or base-band hopping is used. For detailed information on hopping parameters, see XREF. To display the HSN tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the MAL tab (see Figure 6.252).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

437

Atoll User Manual

Figure 6.252: AFP Module Properties dialogue - MAL tab 3. Under MAL Allocation Method, select how the MAL will be allocated for groups of synchronised subcells. Allocation of the same MAL for all the subcells of a synchronised set, or Allocation of different MALs within a synchronised set.

4. 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. Note: If you select Max MAL Length, it is not necessary to set any other constraints.

c. Define the value that MAL Length/Domain Size must not be equal to or greater than. d. Long or Short MAL Strategy (with the option of keeping MAL long enough to allow a certain pattern). e. 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. Note: It is recommended that you let the AFP automatically adjust the target fractional load.

6.9.2.2.7

The Atoll AFP Execution Tab

The Execution tab of the Atoll AFP Module Properties dialogue enables you to define the behaviour of the Atoll AFP module when it reaches the end of the calculation time. To display the Execution tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the Execution tab (see Figure 6.253).

438

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.253 AFP Module Properties dialogue - Execution tab 3. Under Target Calculation Time, select how the AFP uses the .user-defined TCT: 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. Directive duration: This is the AFP's default. If you select Directive duration, the TCT is used by the module to estimate the methods which will be used to find the best solution. If the TCT 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 TCT 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 TCT, the AFP will stop. On the other hand, if convergence has not been reached by the end of the TCT, the AFP will continue; with fixed duration, the TCT corresponds to the minimum amount of time you reserve for the AFP to find the best solution.

4. Under Result Assignment, select how the AFP assigns the results once the automatic allocation has stopped: 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-Save is enabled.

6.9.2.2.8

The Atoll AFP Spacing Tab

The Spacing tab of the Atoll AFP Module Properties dialogue enables you to define an allocation strategy if the selected allocation strategy is "free." To display the Spacing tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the Spacing tab (see Figure 6.254).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

439

Atoll User Manual

Figure 6.254: AFP Module Properties dialogue - Spacing tab 3. Under Pattern, define the pattern to be used to assign frequency groups to sectors. The assigned pattern is defined by "1/n," where "n" is the number of the larger frequency groups in the domain. If the frequency domain has fewer than "n" groups, the pattern is ignored. 4. Under BSIC, define the diversity of BSIC use for frequency hopping: 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: Automatic: The AFP optimises channel spacing to minimise the cost. Max.: The AFP uses the entire spectrum. This option is recommended with the modelling is not accurate. Min.: This option is recommended when a part of the spectrum is to be saved for future use.

6. Under MAIO, define the MAIO allocation strategy for frequency hopping: Staggered: The MAIOs assigned to TRXs of a subcell are evenly spaced. Free: The AFP module freely assigns MAIOs.

6.9.2.2.9

The Atoll AFP Protection Tab

The Protection tab of the Atoll AFP Module Properties dialogue enables you to define additional strategies to evaluate interference. To display the Protection tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 432. 2. Click the Protection tab (see Figure 6.254).

440

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.255: AFP Module Properties dialogue - Protections tab 3. Under Additional Protection Against Adjacent Channel Reuse, select the level of additional protection you want the AFP to use against adjacent channel reuse. 4. Under Definition of Interference for the Required Quality Threshold, select the level of additional protection you want the AFP to use against adjacent channel reuse.

Adjacency Suppression
Adjacency suppression is defined as the difference between the required C/I and the required C/A (C/A being the "Carrier to Adjacent Intensity ratio"). By default this is set to 18 dB following the standard. It is available in the Predictions folder properties dialog window under the name "Adjacent channel protection level". The GSM standard requires this desired behaviour for a relatively good C/I situation. It is therefore recommended to be sure that the physical equipment in the network support this value. When the value of this parameter is used in the AFP (for extracting the interference caused by an adjacent channel) there is a possibility to have a small safety margin, temporarily reducing the 18 Db to 16.5, or even to 15.5. This safety margin is only applied in the AFP, while Atoll's studies continue to apply the full adjacency suppression. You can choose one of the following three options for adjacent channel protection: None: no additional protection is added to the initial protection. Weak: a fixed-size shift of 1.5 dB is applied to the initial protection. Strong: a fixed-size shift of 2.5 dB is applied to the initial protection. Note: For interference matrices based on propagation, Atoll can determine whether they have been calculated with a handover margin. If the 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 handover margin into consideration when calculating the interference matrix, Atoll can automatically change the adjacent channel additional protection from none to weak, or even to strong.

Shadowing in the AFP

The Interference definition according to the required quality threshold section enables you to 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. This is explained in detail in "Interference Cost" on page 429.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

441

Atoll User Manual Note: For interference matrices based on propagation, Atoll can determine whether they have been calculated with a 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.

6.9.2.2.10

The Atoll AFP Advanced Tab

In the next section "Calculating the separation cost for an hopping TRX" start here todo XXXX put ref, we saw how the fractional load is taken into account: If only one frequency in a mal is "dirty", and the mal length is 5, then the TRX cost effect will be 1/5 (=20%) "dirty". This means the cost will be 5 times smaller than if the entire MAL was composed of "dirty" frequencies. This fact is sometimes called a "gain", or even "frequency diversity", which causes a big mis-understanding. In the AFP, the fractional load directly affects the cost. It can not be parameterized, and it is not referred to as a gain. For example, if my MAL length is n, and one of my frequencies has a cost of X, then for the entire mal the cost will be X/n. If this same MAL is repeated in m TRXs of the transmitter, then the cost will be X*m/n. So why not put very long mal lists? (so that m/n is small ?) Because of the fact that the more n is big, the more we have cost effects: 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 none hopping and base band hopping plans, were the fractional load is 1. (m = n) This corresponds to the case were all gains are 0 in the advanced property page below:

Figure 6.256: AFP Module Properties dialogue - Advanced tab The tables in this page enable you to define the Interference and Frequency diversity gains in the case of frequency hopping, which are supplementary gains. These gains model the non linear effects of the C/I diversity on the quality (FER, BLER). Due to fast fading, and channel burst interleaving. 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.

442

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.9.2.3

Frequency Hopping Overview

Atoll AFP is capable of performing both free MAL assignment (sometimes called ad hoc), as well as predefined MAL assignment. The instruction indicating the assignment mode to be used is at subcell level: i.e. different subcell can each indicate a different assignment mode. In free assignment mode, the AFP is free to assign any MAL (assuming of course that it belongs to the domain, and not too long). The length of MAL, the HSNs and the MAIOs are assigned in compliance with the user's directives. If the assignment mode is group constrained, the AFP can only assign one of the predefined groups in the domain.

6.9.2.3.1

The Case of Synthesized Hopping + Group Constrained

If you are working on a group constrained assignment mode, the success of your assignment will strongly depends on the definition of the groups in the domain. We recommend you work as following: Step 1: decide what is(are) going to be the MAL size(s) that your domain will permit. Choosing a single MAL size is a current option. Choosing multiple MAL sizes is often called MPR: Multiple pattern Reuse. The more MAL sizes you have the more optimized will be your allocation. We recommend MPR. Step 2: For each length you have chosen, create as many groups as possible having the specific length and if possible, covering the entire domain. Example, For a domain of 60 frequencies, create: 3 groups of 20 frequencies each (mainly reserved for the preferred group allocation of an azimuth oriented allocation) 10 groups with 12 frequencies each + 12 groups of 10 frequencies each (will be used in heavy traffic cases or in "HSN by site" cases). We are giving an example were there are so many groups that some of them must overlap. In addition we could define 20 groups with 6 frequencies each, 24 groups of 4 frequencies each, and even 30 groups with 4 frequencies each. By thus each frequency will belong to an average of 11 groups. Do not hesitate to create groups, the AFP likes groups. When many groups are defined, the quality is almost as good as with free assignment. Notes: 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 pre-defined 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.

6.9.2.3.2

An Atom = A perfectly Synchronized Set of Equi HSN SFH Subcells

An atom is a set of synchronised subcells that share the same HSN, the same frequency domain and have the same length MAL. The MAIO assignment of an atom manages the frequency collisions between the MALs of the atom. If an atom contains more than one subcell, the AFP may assign to it partially different MALs (depending on a user-definable option) but it will always consider the fact that the subcells are synchronised. Atoms can be determined by the user or by the AFP via the HSN allocation. Some restrictions on this definition exist due to some extreme cases: 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. An important feature is the possibility to 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.

6.9.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).

6.9.2.3.4

Optimising Hopping Gains

If the AFP was given a degree of freedom when choosing MAL lengths, it may opt for longer MAL lengths. In this way, it can profit more from the hopping gains. On the other hand, it may be increasingly hard to find frequencies for these MALs The advanced page, the MAL page, and the HSN page in the AFP property pages provides the capacity to control this convergence. For more details, see the advanced page description. In interference limited network, the default hopping gain values are not sufficiently strong to cause the AFP to converge toward long MALs.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

443

Atoll User Manual

6.9.2.3.5

Fractional Load
Both HSN assignment and MAL length determination processes are tuned to obtain a user defined fractional load. A fractional load of is obtained if the number of TRXs using a certain MAL is only times the size of the MAL. Atoll's notion of fractional load does not require the traffic load to be taken into account. Since fractional load cannot always be obtained, this parameter is considered as a guide rather than a constraint. When it can be obtained, AFP chooses either a MAL length 1/ times longer than the number of TRXs in the biggest subcell of the atom or a MAL length 1/ times longer than the sum of all TRXs in the atom. These are called "the short MAL strategy" and "the long MAL strategy" respectively. You can choose between the two in the MAL tab of the properties dialog. The value of the fractional load parameter can also be edited and, furthermore, it can even be automatically calibrated by the AFP. Note: Fractional load is 1 for Baseband hopping The MAL length has an upper limit defined in the "Max MAL length" parameter of the subcell table. The user can instruct the AFP to strictly use this value. (see the MAL page in the AFP property pages)

6.9.2.3.6

Domain Use Ratio

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

6.9.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 studies.

The user can control the HSN allocation so that it performs one of the following: Assigns the same HSN to all subcells of a site Assigns the same HSN to all subcells of a transmitter Assigns pair-wise different HSNs if a pair of subcells have mutual interference. Optimise HSN assignment so that the frequency assignment is better (free HSN).

6.9.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 averages the cost upon all frame numbers in the synchronised case and upon all collision probabilities in the nonsynchronised case.

6.9.2.4

Azimuth Oriented Assignments (Pattern Allocation, 1/1 1/3 1/x )

In order to understand what a pattern allocation in Atoll's AFP is, you must first read the previous chapters, since the pattern allocation in Atoll is performed as following: 1. The AFP first assigns preferred groups to all demanding subcells 2. The AFP assigns what ever needs to be assigned, trying to respect these preferred groups, as explained in the cost description. The conditions for getting a preferred group from the AFP are the following: The subcells must be or in synthesized 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. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

444

Chapter 6: GSM/GPRS/EDGE Networks Only transmitters that are not lonely in their site will be entitled to a preferred group: 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 axises are equi spread. It matches each directional axis to a group. The pattern allocation associates the X main direction axises with the X biggest groups in the domains

The AFP will only allocate a preferred group if the transmitters azimuth is clearly aligned with one of the directional axises. 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 the usage of this feature since 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-sartorial, X should replace 3). We recommend not imposing the pattern very strongly on your network. It should be kept as a guideline.

6.9.2.5

BSIC Allocation
Atoll AFP allocates BSICs according to two criteria, a soft criterion and a hard criterion. Not respecting the hard criterion is considered an error, while not respecting the soft criterion provokes a warning. The soft constraints are logically stronger, meaning these have a higher probability of not being satisfied. The hard criterion is easier to satisfy but must not be broken as it will cause handover failures. The hard criterion is based on the second order neighbour relation and BCCH co-channel reuse. The soft criterion uses interference information as well and tries to induce a larger [BSIC, BCCH] reuse distance. (See todo XXXX were we depict the new algorithm and both criteria. The BSIC allocation is compliant with the BSIC domains of transmitters and the strategy indicated in the BSIC tab of the AFP module property dialog. Either the algorithm selects a minimum number of BSICs in the related BSIC domain (Minimal option), or it chooses as many BSICs as possible while keeping them evenly distributed in the related BSIC domain (Maximal and homogeneous option). In the Atoll AFP, the directions of neighbour relations are all considered equivalent, so that the BSIC allocation is subject to harder constraints. Let us consider the following two examples:

From the operational point of view, the first case is much more critical in terms of (BSIC, BCCH) collision. However, both cases are considered as violations of hard constraints by the AFP and error messages are generated (if the domain limitation provokes violations). The soft criteria add additional constraints due to interference and adjacent reuse between BCCH channels. Warning messages are generated when soft criteria are not fulfilled. An old tradition consisted on assigning BSICs according to distance constraints. This practice is no longer needed because of the much more evolved soft criteria (based also upon interference matrix) BSIC assignment cannot be performed if the BSIC domain is empty or not assigned. When no BSIC domain is assigned, Atoll displays a warning message that says that the BSIC domain is either null or empty. When an empty BSIC domain is assigned, Atoll displays an error message telling the user that BSIC allocation is not possible, and the network loading is stopped.

6.9.3

Advanced AFP usage

Whenever a network becomes spectrum-wise limited, frequency planning becomes the most cost efficient way to optimize its performance. The AFP usage in these cases must evolve in order to include the more advanced capacities of the AFP.

6.9.3.1

Optimizing the Number of Required TRXs

One of the two new allocation styles is the one in which the AFP is permitted to optimize the number of required TRXs. When this option is selected, the AFP may reduce the number of TRXs compared to the number of required TRXs in order to maximise the amount of correctly served traffic, and consequently, reduce the level of interferences. In the same way, for highly traffic-loaded subcells, the AFP may increase the number of TRXs compared to what is required in order to reduce the blocked traffic. The circuit and packet demand are the two main inputs used for estimating the blocking rates. They can be either directly extracted from the subcell table, or come from the default traffic capture, or be re-estimated by the Atoll AFP Module. It will perform do it using the old traffic load, and the number of required TRXs as input.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

445

Atoll User Manual Whatever the method is, when the traffic demand is known, the Atoll AFP Module may vary the number of TRXs in subcells and for each it will calculates: The blocking probability The served circuit and packet traffic The resulting traffic loads.

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.

6.9.3.1.1

Soft Blocking Versus Hard Blocking

We choose to start by citing a reference taken from the book "Performance Enhancements in a Frequency Hopping GSM Network" written by Thomas Toftegaard Nielsen and Jeroen Wigard, page 68: In this reference, as many others, the authors suggest that quality is a trade-off between Soft Blocking and hard blocking. The soft blocking is due to interference related effects (such as call drop), while the hard blocking is due to the circuit shortage during the most busy periods. A cost component of the AFP models the hard blocking, based on the Erlang B theory. The AFP is therefore capable of finding the optimal trade-off point. This tradeoff point is not a global one. Its specific to each TRX.

6.9.3.1.2

Splitting the Problem is not Optimal.

When a combinatorial optimization problem becomes complicated, we are often tempted to split it into two parts. In this case it corresponds to 1): Dimensioning) and 2): Frequency planning. However, a conjoint optimization, as done in the AFP, permits the exploitation of the local variations of soft versus hard blocking measures; and by thus can obtain a nice performance enhancement. Towards the end of this section depict a realistic case study, which quantifies the gain in efficiency obtained by our new methodology. Here we will only discuss the more simple benefit which is the process simplification: We can avoid the needing to manually find a target blocking rate: In Atoll AFP model, this optimisation is achieved without iterating.

It is important to keep in mind that the evaluation method of the resulting frequency plan must change: If plan A has more TRXs than plan B, it is possible that an interference study for plan A will display more interference, even it plan A is the good plan. This is the main reason behind the recent enhancement of the AFP evaluation method depicted in (todo XXXX put ref). It consists on the positive attitude: trying to maximize the correctly served traffic instead of trying to minimize the interfered traffic.

6.9.3.1.3

What Are Exactly the "Local" Decisions Taken By the AFP?

We will answer this question with an example: Let us assume that the AFP is called to optimize a single transmitter. We assume it is a default value case having two subcells: TCH and BCCH. The two subcells absorb the traffic demand together. We assume that the traffic demand consists on 25 Erlangs of circuit switched traffic, and 5 timeslots of packet switched traffic. We also assume that the required number of TRXs is 2 for TCH, and 1 for BCCH. The AFP could simply assign 3 TRXs in this cell, exactly as required, or it can also study a few additional possibilities: Assign only 2 TRX, by thus reducing interference. Assign 4 TRXs (one TRX more); by thus reduce the blocking rate.

Let us see how the AFP chooses the best option: First it calculates the available number of circuits (depending on the HR ration ). Then it calculates the blocking rate using the Erlang B equation and the circuit switched demand. Once it knows how much traffic is served, it can calculate the traffic load (Between 0-1, 1 correspond to full load). And once calculating the load it can calculate the interference cost as well as the hard blocking cost.

446

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks The cost represents the interference which depends on the frequencies that were assigned. When we have many TRXs it is harder to find clean frequencies. In the case below, the "local" spectral availability is the following: Only 2 frequencies have low interference. (Probability of interference = 10%). We call them f1 and f2. One frequency has a medium level of interference (20%), and is called f3. One frequency has a high level of interference (30%), and is called f4. All the other available frequencies are even more heavily interfered. The entire process is summarized in the table below: Optional frequency plan Units : Frequency plan 1: Frequency plan 2: Frequency plan 3: TRXs Number of circuits. 21 Blocked traffic Time slot. 7.4 Traffic load % 100 Interfered traffic on f1 and f2 Time slot. 1.5 Interfered traffic on the f3 Time slot. 0: Since it is not used 1.56 Interfered traffic on the f4 Time slot. 0: Since it is not used 0: Since it is not used 1.77

2 TRXs: using f1 and f2. 3 TRXs: using f1, f2 and f3. 4 TRXs: using f1, f2, f3, and f4.

32.2

0.55

97.7

1.46

43.4

0: No blocking with 4 TRXs.

74

1.1

1.18

Since the AFP will try to minimize what is red in the table above. It will choose frequency plan 2. (Bold figures sum up to 3.57). We use the term local because of the fact that the decision depends on the local spectral availability: if the frequencies were a little cleaner, the AFP would have chosen plan 3. If frequency f3 and f4 were very dirty, the AFP would have chosen Plan 1

6.9.3.1.4

The Measure That Remains Constant During the Entire Optimization

When not optimizing the number of required TRXs, or in old versions of AFP, the served traffic is constant In older versions, the AFP received the traffic load as input. The traffic load represents the ration between the served traffic and the available resources. It would be more precise to call it the "Served traffic load". During the entire AFP process the traffic load remained constant, since the AFP did not consider the possibility of assigning more (or less) TRXs. When optimizing the number of required TRXs the traffic demand is a constant. From the 2.8.0 and on, (and when the TRX number optimization is on), the measure that remains constant in the AFP is the traffic demand. In each evaluated frequency plan. (Initial plan, solution 0 plan, Solution 1 plan ) the AFP will first calculate the traffic loads, and only then the cost and the blocking rates.

6.9.3.1.5

How Does the AFP Get the Traffic Demands

As with the traffic loads, also the traffic demands can come from the traffic capture: If the user chooses to work with traffic maps, the traffic capture will contain this information. Then performing dimensioning or KPI calculation this information is committed into the subcell table. In the AFP wizard the user is asked if traffic information should be fetched from the default capture or from the subcell table. (As before was the case with the traffic load). Or they can come directly from the OMC and inserted into the subcell table A specific table is defined in order to absorb OMC traffic readings. To open it: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > Subcells Table: Traffic Data from the context menu. The Traffic data part of the Subcells table appears. The BCCH and TCH subcells are assumed to share the same traffic management unit. We therefore have a single line for both. On the other hand, TCH_INNER subcells usually manage their traffic separately. When such exist, there will be an additional line for each such transmitter. By copying OMC traffic figures to the two demand fields into the subcell traffic view above, you will supply the AFP directly with your OMC traffic. Note: Subcells that share the same traffic management unit are assumed to have the same traffic load. (At least that is the case when Atoll calculates this load). The field Max Traffic load shows the highest traffic load value that was found among the subcells sharing the line. Normally all should have the same.

Or, the AFP can use the traffic loads in order to calculate the demands. (In order to maintain compatibility with old documents).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

447

Atoll User Manual In older versions, the AFP used the field "traffic load" and the number of required TRXs as its traffic source. When the adjustment of required number of TRX is not performed, the cost function will continue to be the same. When the adjustment is requested, the AFP can base its demand on the traffic load, in a way that permits the used to stick to its old traffic model.

How to control the optimization so that it allocates more or less TRXs?

The more you increase the traffic demand the more you will have TRXs. The more there is a demand, the higher will be the pressure on the AFP to allocate more TRXs. As said above, the demand can come, or from the traffic model, or from the subcell table, or from the traffic load values. If demands come from the traffic capture, you can increase demand by recalculating the capture with a higher traffic coefficients. If the demands comes from the OMC, you can bust it up using an excel sheet. And if it comes from the 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 TRXs). 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

Figure 6.257: AFP Module Properties dialogue - Cost tab The 5% in this screen shot mean that the traffic demand can exceed the served traffic by no more than 5% By Increasing this measure we increase the difference between served traffic and traffic demand. (yet only in the heavily loaded TRXs, when traffic loads are low, served demand ~= demand ) Since we are in the case were the served traffic is our information source, and therefore constant, this means we are increasing the demand. And increasing demand means more need for TRXs. You can modify the cost weights for interference and separation violation. This is the other side of the balance: High cost will put pressure on the AFP to allocate less TRXs. You can modify the tax for missing (or extra) TRXs As it name indicates, this is a simple cost component aimed to softly limit the freedom of the AFP in this new domain. The higher it is, the better will be the respect of the original "number of required TRXs" A dedicated Locking flag at subcell level Permitting you to shut down the new capacity whenever you exactly know the number of TRXs you need. Plan 1

448

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.9.3.1.6

The Positive Attitude for Frequency Plan Evaluation

When optimizing the number of required TRXs, the evaluation process and objective must adapt as following: After the AFP, you might want to run a KPI calculation. When using the interfered zones study as shown in Figure 6.258 on page 449, you should prefer the frequency plan were X - Y is the highest. In the figure below, X is 7880.9316 and Y is 598.3921. The correctly served traffic is therefore 7282.5395 weighted timeslots.

Figure 6.258: The report on the interfered zones coverage prediction In the AFP, the "positive attitude" consists in communicating what's good: correctly served Erlang estimation, and not what's bad: AFP cost, various penalties, or taxes. By adopting this attitude the AFP simplifies the decision process for the user, since there is only one single number to consider:

Figure 6.259: Summary tab of the AFP output dialogue The screen shot above shows the Summary tab of the AFP output dialogue. This page also shows the history and the cost components. One can remark in the example above that the different frequency plans have different numbers of TRXs, and therefore different blocking costs. Addtionnaly, in the Allocation tab of this AFP output dialogue, the TRXs which have been deleted can also be displayed by using hashed cells:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

449

Atoll User Manual

Figure 6.260: Subcells tab of the AFP output dialogue The Subcells tab of the AFP output dialogue displays additional subcell information:

Figure 6.261: Subcells tab of the AFP output dialogue With all these new elements, the primary acceptance decision becomes quite easy.

6.9.3.1.7

What are the Main Benefits of the Capacity to Adjust the Number of TRXs?
Less Interference
A case study showed us that a big amount of interference reduction can be obtained. The graphs below show the effect of the TRX number adjustment (compared to the initial dimensioning) on the interfered and served traffic.

450

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.262: Effects of TRX number adjustement on Traffic The 4 frequency plans above were all generated using exactly 50 frequencies. All other network parameters were the same. The plan "Dim - 76 TRXs" is a plan in witch many TRXs were removed by the AFP (76 out of 820). This removal gave a big reduction in interference, yet did not impact the absorbed traffic since the TRX reduction was considered only if the transmitter's load was low.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

451

Atoll User Manual

Re-adjusting the number of TRXs so that it fits to OMC traffic

In a real network, it is often needed to re-adjust the number of TRXs to the evolution of the traffic. A typical situation is the following snap shot; taken before any adaptation is done:

Figure 6.263: Number of required TRXs vs. Erlang Demand It is normal that not all "X" TRX transmitters have the same traffic demands, therefore the traffic loads will often vary from one transmitter to an other. Once the AFP performs its optimization, the traffic load values become more uniform, as can be observed in the output below:

Figure 6.264: Load comparison before and after TRX adjustment

Frequency Domain and Frequency Band balancing

Standard practice BCCH/TCH/EGPRS domain split HCS layer band/domain split

The splitting point stays global, yet the number of TRXs is adapted.

452

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

Figure 6.265: Frequency reuse balancing with or without TRX number adjustment In the example above it is a little hard to see, yet in fact, most TRXs that were removed were removed in the 900 band (In the first half, the red line is almost always below the blue line.)

6.9.3.2

Interference Matrix combination according to max likelihood

One of the more advanced features of the AFP is the capacity to intelligently combine different interference matrices. Different types of interference matrices have different weak points. The maximum likelihood approach detects and avoids these weak points. The most important aspect of the maximum likelihood combination is the capability to differentiate between no-interference and unknown-interference. Therefore, this approach requires that Atoll keeps the information about the type of the interference matrix, its quality indicators, and its scope. The next sections explain the maximum likelihood combination performed by the Atoll AFP Module. Before describing the combination process, the scope and context of interference matrices is explained.

6.9.3.2.1

Interference Matrix Context

The context of an interference matrix refers to the following properties associated with each matrix: Name (and comments, if any) External file name (if the matrix in externalised) Active or not Type (one of the 9 types described in "Defining Type-Dependant Quality Indicators on Interference Matrices" on page 285) Type-dependent quality indicators

The context of an interference matrix is mainly used to indicate the statistical quality if the interference matrix so that the AFP can weight the information read from the interference matrix accordingly. Atoll can support a 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 context of interference matrices allows a common representation and significance of the parameters influencing the combination process. These parameters are, therefore, described as a set of quality indicators, with comprehensive 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 9 pre-defined types of Interference matrices are divided into 4 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 gives you access to this information:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

453

Atoll User Manual

Figure 6.266: Definition of Interference Matrix Types Depending on the matrix type, the quality indicators available in the advanced tab include: For matrices based on path loss (propagation data) matrices The standard deviation The resolution Whether the interference information (probabilities) correspond to traffic or surface area The statistic duration 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 in each matrix calculation point The volume of information Whether the interference information (probabilities) correspond to traffic or surface area The statistic duration 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 in each matrix calculation point The standard deviation, depending on the equipment quality and measurement post-processing The average number of points collected in 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 in each matrix calculation point The volume of information Whether the interference information (probabilities) correspond to traffic or surface area

For matrices based on reselection statistics from the OMC

For matrices based on handover statistics from the OMC

For matrices based on RXLEV statistics from the OMC

For matrices based on test mobile data

For matrices based on CW measurements

For matrices based on scan data drive tests

The context of an interference matrix is not included in the interference matrix files. That is why Atoll asks the user to setup the type and quality indicators of the interference matrix manually.

454

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.9.3.2.2

Interference Matrix Scope

The scope of an interference matrix is a mapping between a transmitter ID and the following information: Transmitter name BSIC (as was when IM statistics were gathered) BCCH (as was when IM statistics were gathered) % of victim coverage (an integer between 0 and 100) % of interferer coverage (an integer between 0 and 100)

It is visualized as following:

Figure 6.267: Interference Matrix Scope The most important information of the scope is contained in the columns "% of victim coverage" and "% of interferer coverage". In order to understand their significance as well as their use, the following should be kept in mind: Interference matrices must provide interference information between each pair of subcell in the network. A large amount of memory would be required for a simple sequential representation of the interference matrix, which would make it impossible to work with such interference matrices in large networks. Therefore, interference matrices are represented as a set of entries for which interference exists. If an entry (i, j) does not exist in the set: Either j does not interfere with i (no-interference), Or the interference information is missing in the interference matrix because at least one of the two was out of the scope of the interference matrix (unknown-interference).

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 then no interference = unknown interference. If there is more than one interference matrix, the information missing in one matrix could be available in another. Therefore, it becomes very important to distinguish between the two cases in order to intelligently combine different interference matrices. If for a certain entry you combine { 60%, Unknown, Unknown } you will get 60%. Yet if you combine { 60%, 0%, 0% } you will get 20%. The ideal method for differentiating between no-interference and unknown-interference cases would be to keep a matrix of values in memory, which depicts the reliability of each of the matrix entries, and thus, depicts the entries for which the interference is "Unknown" as unreliable entries. It is not practically possible to implement such a method simply because this matrix of values will be too large to work with. Therefore, Atoll includes 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: VictimCoverage(Transmitter(i)) * InterfererCoverage(Transmitter(j))

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

455

Atoll User Manual This implementation is simple, compact, 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 299). This means that even when only one transmitter is present inside the computation zone, many other transmitters may 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 externalising the interference matrix in the .clc format and editing it. The .clc format can store all the interference matrix information (see the Technical Reference Guide for more information). Notes: 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 ID's 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 ID's. There are no restrictions on transmitter ID's 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 % 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 % of victim and interferer coverage, while the others would not.

Use of the BSIC and BCCH in the Scope

The BSIC and BCCH fields in the scope are used for the cases where the BSIC and BCCH allocation, during the period when the interference matrix information was gathered, was different from the current BSIC and BCCH allocation.

6.9.3.2.3

Keeping the Interference matrix Up to Date

An interference matrix is no longer valid once the network has changed. However, currently this fact is left under the user responsibility. Atoll will try to perform some matrix maintenance in order to reduce overhead, yet this help is not guaranteed. When a .clc file (and its corresponding .dct) are imported, the transmitter indexes in the files can be arbitrary. In order to improve access time, Atoll changes these indexes to the ADO record ID as index. When you rename or delete a transmitter, or when the ADO index is changed, the interference matrix is automatically updated, and saved when the Atoll document is saved. 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 externalized, Atoll does not always manage to keep it updated as described above. Note: Calculate your Interference Matrices as often as you calculate your path loss matrixes.

6.9.3.2.4

Interference Matrix Combination in Atoll AFP Module

Interference matrices are combined in a manner that follows these two important guidelines: 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 Atoll AFP Interference Matrices Tab" on page 435) available in the Atoll AFP Module properties dialog displays and lets to modify the weights that control the interference matrix combination.

456

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks 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 equasions are different for the different classes of types since the quality indicators are different as well: i. Interference matrix based on propagation: 75 7.5 Component C = -------------- ------r + 25 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 Which gives a weight of 1 for 8 days of measurements. iii. Interference matrix based on drive test analysis: (1 + n r + 1) Component C = --------------------------------------------4 ( + 1)
0.4

3 parameters determine the weight: i.The standard deviation , which is assumed to be lower than the one of a propagation model. ii.The number of measurements considered at each calculation point, r iii.The number of calculation points per transmitter, n iv. Interference matrixes of other types do not participate in the weighting, since they are or Upper bound IMs or Lower bounds IMs.

6.9.3.3

The Storage of a frequency plan in Atoll

Currently Atoll stores a single frequency plan. It is stored in its TRX table records, and also in its subcell and transmitter tables. Some AFP Quality indicators can even be stored in the Site table. In the future, Atoll will permit the storage of multiple frequency plans. In this chapter we will depict the various issues concerning this storage.

6.9.3.3.1

The TRX table particularity

Atoll's TRX table enables the following: Support of an external ID space of the TRXs of a transmitter (important for import and export utilities). MAL/channel at TRX level. MAIO at TRX level. Fine 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.

6.9.3.3.2

Multi-level AFP directives

There are various AFP directives that are multi level, meaning that they can be set both at "high level" as well as "low level": Example 1: You can lock an entire transmitter for the assignment of channels and MAIOs by checking it locked in the transmitter table. In addition you can lock/delock TRX by TRX using the TRX table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

457

Atoll User Manual Example 2: The AFP weighing can be set both at transmitter levels as at subcell levels. Example 3: The domain definition can be re-defined at subcell level by the help of the field "excluded channels". In each of these multi level cases the resulting directive is clear: Ex1: A TRX is locked if it is locked itself, or if its transmitter is locked. Ex2: the final AFP weight is the multiplication of both level weights.

6.9.3.3.3

Redundancy and the Subcell Audit

Atoll incorporates some deliberate redundancies between the subcells and TRX levels, and the Transmitters table: The channel list in the Transmitters table is the intersection of all channels appearing in the TRXs of a transmitter. 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 to deduce the central frequency), is read from the domain of the BCCH subcell of the transmitter.

Atoll considers the low level to be the accurate source of information. For example: Atoll will automatically update the TRX table if the channel list of a transmitter in the transmitter table is changed. The frequency band of a transmitter cannot be edited.

These redundancies provide some additional features (for example, grouping transmitters according to the frequency bands). On the other hand, there is a chance of mistakes and bugs which may damage a redundancy in the ATL file. Therefore, it is recommended that the audit tool be used from time to time in order to fix these problems (right click the Transmitters folder, choose Audit from the Subcells menu) If the report contains alarming issues, run this audit again, this time with the "fix" option on.

6.9.3.3.4

AFP Performance Indicators (AFP PI's)

The AFP can be used to generate different AFP performance indicators (AFP PI's). The AFP PIs are visible in the AFP results window, and once commit is applied, they can be seen in Atoll's TRXs, subcells, transmitters and sites tables. The most important AFP PIs are found in the subcell table, and are now visible in a dedicated read only table view.

The TRX rank PI, and it's use

The AFP TRX Rank provides a ranking of the TRXs in a subcell. If a TRX rank is high, it implies that the frequency (channel) corresponding to this TRX has bad usage conditions. TRX ranks indicate the best and worst quality TRXs in each subcell. The best TRX might be a candidate for extensive EGPRS usage. The worst TRX will be the TRX that is potentially removable. The OMC might use rank (or preference) information for better RRM (first charge the good TRXs, only after charge the bas ones ). Notes: Rank = 1 is the best rank. TRX Rank is the corresponding field in the TRX table.

As it is during an AFP process that frequencies and MALs/MAIOs for different TRXs of a subcell are chosen, the AFP tool stores and manipulates the information about TRXs in good and in bad conditions. If you choose AFP Rank indicator to be allocated when starting an AFP session, each cost improving solution will go through a TRX rank assignment. If no improving plan is found, TRX rank will be assigned for the initial plan (like BSIC). TRX ranking within a subcell is performed on the basis of TRX costs. 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 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 pre-defined.

6.9.3.3.5

The AFP COST PI's

Total cost and separation violation cost component at the TRX, subcell, transmitter and site levels can be computed and displayed as AFP performance indicators. These are the cumulated total costs and the cumulated separation violation costs of each TRX, subcell, transmitter and site.

458

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

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

6.9.3.3.6

The AFP subcell PI's

From the 2.8.0 and on 4 AFP PIs can be committed into 4 subcell fields. These fields are then displayed in a separate view of the subcell table. And also in a separate page in the AFP output dialogue.

6.9.3.4
6.9.3.4.1

Various tips and tricks

We bring here a small collection of important issues which did not manage to find their place in the overall framework. Even though, they are interesting, and you will not regret reading them.

Focusing the AFP on the hard spots.

In this small paragraph we propose a simple strategy for obtaining improved frequency plans. Let us assume that we have X hours of available computation time: 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 were the interference is strongest.

6.9.3.4.2

Learning the Network and Solving the hard Spots at the same time
1. Apply this technique to networks having 12000 to 120000 Erlangs (2500 to 25000 TRXs). Make sure that the AFP is configured to maintain its learned experience (execution page in the AFP property pages). 2. Run the AFP for at least 10 solutions, on the entire network, specifying a short time period, commit the plan knowing it is of basic quality. If this quality satisfies you, you do not need to continue. 3. Find the areas that generate problems. For example, some sites with separation violations, high congestion, or high interferences. 4. Create a calculation zone around these areas. 5. Create a filtering zone including the computation zone + the first ring of neighbours. 6. Make sure that this representative part of the network is not too big nor too small. For example: 100 to 200 transmitters in the computation zone, plus an additional 50 to 100 of locked neighbours. 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 minimize 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: Duplicate your AFP model. Give a meaningful name to the duplicated model. In its execution property page, switch off the experience learning option. (So that this model does not get altered by other AFP users) Archive to database the new AFP model, yet not the old one. The new model can be used by the other AFP users. The old model which you didn't archive is not affected by your modifications.

6.9.3.4.3

Better understanding the Point analysis tool

It is often useful to know what exactly causes interference conditions at a point. This is one of the important roles of the point analysis tool. Yet because of its complexity, some users are afraid to use it, which is a pity. The point analysis is complicated only because it is a very rich tool. It provides the user with the information of how are the interferers of a TRX at a point, what are the different gains (power offsets, burst collision probability, DTX, adjacency suppression), and how do the different components combine to a "total interference" on a channel or on a mobile allocation.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

459

Atoll User Manual

Example 1: Combination of Interference Effects

This figure depicts the case where two adjacent interferences are combined to create total interference (the gain value (the empty part - 18 dB) shows that they are adjacent). For each of the two adjacent interferers, C/I > 12 dB, while for their combination, the total interference, C/I < 12 dB. This example demonstrates the fact that geographic interference combination is more accurate than the interference cost of the AFP. Assuming the required quality to be 12 dB, this specific point would not contribute to the AFP cost, while it would be considered as interfered in the interference study.

Figure 6.268: Combination of Interference Effects

Example 2: Counting Strong Interference Only Once

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

Figure 6.269: Counting Strong Interference Only Once

460

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 6: GSM/GPRS/EDGE Networks

6.9.3.4.4

Why aren't the traffic loads incorporated in the interference matrix?

Atoll maintains the traffic load separate from the interference information. Before justifying this choice we must depict the two alternatives: 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 size. Incorporating this gain in the IM (as a result of the mixed option) means that the IMs become hopping-mode and MALsize 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.

6.9.3.5

The role of the AFP administrator

The AFP administrator is the person who knows the AFP better than anybody else in the company. It is the AFP administrator that evaluates the AFP, and therefore it his him that decides how it should be configured. The AFP administrator has a very powerful control tool which is the centralized database. It is there that he can publish his pre-defined and pre-configured AFP models. The AFP administrator must also be a GSM Expert in general, and is therefore one of the people that should be in contact with our support teem in order to issue problems (if some occur) or feature requests, (if any are needed). The two first sub-sections in the section above are typical "administrator" paragraphs, since they talk about AFP training, and how to share this information among AFP users. The AFP R&D projects below are also interesting for an AFP administrator. (Because of its role as feature requestor).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

461

Atoll User Manual

462

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7
UMTS HSPA Networks

RF Planning & Optimisation Software

Atoll

Chapter 7: UMTS HSPA Networks

UMTS HSPA Networks

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

7.1

Designing a UMTS Network

Figure 7.270 depicts the process of planning and creating a UMTS HSPA network.

Open an Existing Project or Create a New One

Network Configuration - Add Network Elements - Change Parameters Basic Predictions (Best Server, Signal Level) Neighbour Allocation 4

Traffic Maps

5a

Monte-Carlo Simulations

5b 5

User-defined values Cell Load Conditions

5c

UMTS/HSPA Predictions 7

6a Prediction Study Reports

Scrambling Code Plan

Figure 7.270: Planning a UMTS network - workflow The steps involved in planning a UMTS HSPA network are described below. The numbers refer to Figure 7.270. 1. Open an existing radio-planning document or create a new one ( 1

).

You can open an existing Atoll document by selecting File > Open. Creating a new a new Atoll document is explained in Chapter 2: Starting an Atoll Project.
2

2. Configure the network by adding network elements and changing parameters ( You can add and modify the following elements of base stations: "Creating or Modifying a Site" on page 473 "Creating or Modifying a Transmitter" on page 474 "Creating or Modifying a Cell" on page 474.

).

You can also add base stations using a base station template (see "Placing a New Station Using a Station Template" on page 475). 3. Carry out basic coverage predictions ( 3

"Making a Point Analysis to Study the Profile" on page 488 "Studying Signal Level Coverage" on page 490 and "Signal Level Coverage Predictions" on page 498

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

465

Atoll User Manual 4. Allocate neighbours, automatically or individually ( "Planning Neighbours" on page 528.
5

).

5. Before making more advanced coverage predictions, you need to define cell load conditions ( You can define cell load conditions in the following ways: -

).

You can generate realistic cell load conditions by creating a simulation based on a traffic map ( 5a and 5b ) (see "Studying Network Capacity" on page 549). You can define them manually either on the Cells tab of each transmitters Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 474) (
5c

).
6

6. Make UMTS-specific coverage predictions using the defined cell load conditions ( "UMTS-Specific Studies" on page 509 "HSDPA Coverage Prediction" on page 525 "HSUPA Coverage Prediction" on page 527.
7

).

7. Allocate scrambling codes ( -

).

"Planning Scrambling Codes" on page 541.

7.2

Planning and Optimising UMTS Base Stations

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

Antenna
- Azimuth - Mechanical tilt

TMA Antenna
- Height

Feeder Cable

BTS
- BTS noise figure - Power

Site
- X, Y coordinates

Figure 7.271: A transmitter Atoll lets you create one site, transmitter, or cell at a time, or create several at once by creating a station template. Using a station template, you can create one or more base stations at the same time. In Atoll, a base station refers to a site with its transmitters, antennas, equipment, and cells. Atoll allows you to make a variety of coverage predictions, such as signal level or transmitter coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, or studied. 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 studies, such as effective service area, noise, or handover status predictions, on the network. In this section, the following are explained: "Creating a UMTS Base Station" on page 467 "Creating a Group of Base Stations" on page 481 "Modifying Sites and Transmitters Directly on the Map" on page 482 "Display Tips for Base Stations" on page 482 "Creating a Dual-Band UMTS Network" on page 483 "Creating a Repeater" on page 483 "Creating a Remote Antenna" on page 486

466

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks "Setting the Working Area of an Atoll Document" on page 488 "Studying a Single Base Station" on page 488 "Studying Base Stations" on page 492 "Planning Neighbours" on page 528 "Planning Scrambling Codes" on page 541.

7.2.1

Creating a UMTS Base Station

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

7.2.1.1

Definition of a Base Station

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

7.2.1.1.1

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

Figure 7.272: New Site dialogue Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you want to change the default name that Atoll gives to new sites, see the Administrator Manual. Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of the site here.

Tip:

While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.

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 wish. If an altitude is specified here, Atoll will use this value for calculations. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

467

Atoll User Manual Comments: You can enter comments in this field if you wish. 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 656. If no equipment is assigned to the site, Atoll considers the following default values: Rake efficiency factor = 1 MUD factor = 0 Carrier selection = UL minimum noise Downlink and uplink overhead resources for common channels = 0 The option AS Restricted to Neighbours is not selected, and Atoll uses one channel element on the uplink or downlink for any service during power control simulation.

The Equipment tab:

7.2.1.1.2

Transmitter Description
The parameters of a transmitter can be found in the transmitters Properties dialogue. When you create a transmitter, the Properties dialogue has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Properties dialogue has three additional tabs: the Cells tab (see "Cell Definition" on page 470), the Propagation tab (see Chapter 5: Managing Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 32). 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. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site on which the transmitter will be located. For information on the site Properties dialogue, see "Site Description" on page 467. You can click the New button to create a new site on which the transmitter will be located. Frequency Band: You can select a Frequency Band for the transmitter. Once you have selected the frequency band, you can click the Browse button ( ) to access the properties of the band. For information on the frequency band Properties dialogue, see "Defining Frequency Bands" on page 652. 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 positions, and then enter the x-axis and y-axis coordinates, X and Y, respectively.

468

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks The Transmitter tab (see Figure 7.273):

Figure 7.273: Transmitter dialogue - Transmitter tab Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder of the Data tab. Note: Only active transmitters are taken into consideration during calculations.

Transmission/Reception: Under Transmission/Reception, you can see the total losses and the noise figure of the transmitter. Atoll calculates losses and noise according to the characteristics of the equipment assigned to the transmitter. Equipment can be assigned by using the Equipment Specifications dialogue which appears when you click the Equipment button. On the Equipment Specifications dialogue (see Figure 7.274), the equipment you select and the gains and losses you define are used to initialise total transmitter UL and DL losses: TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button ( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equipment" on page 147. 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 147. BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defining BTS Equipment" on page 148. Feeder Length: You can enter the feeder length at transmission and reception. Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value you enter must be positive. Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter must be positive.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

469

Atoll User Manual

Figure 7.274: The Equipment Specifications dialogue Note: 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 prediction studies even if they are different from the values in the Computed boxes. The information in the real BTS Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total Losses at transmission and reception and the real BTS Noise Figure at reception if you wish. 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. The other fields, Azimuth, Mechanical Downtilt, and Additional Electrical Downtilt, display additional antenna parameters. 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 660. R99 bearers only support transmit and receive diversities. You can define the transmit diversity method from the Transmission list when more than one transmission antenna port is available. The receive diversity method depends on the number of reception antenna ports selected (2RX for two reception antenna ports and 4RX for four reception antenna ports). Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is the percentage of power reserved for this particular antenna. For example, for a transmitter with one secondary antenna, if you reserve 40% of the total power for the secondary antenna, 60% is available for the main antenna. For information on working with data tables, see "Working with Data Tables" on page 53.

7.2.1.1.3

Cell Definition
In Atoll, a cell is defined as a carrier, with all its characteristics, on a transmitter; the cell is the mechanism by which you can configure a UMTS multi-carrier network. In other words, a transmitter has one cell for every carrier. When you create a transmitter, Atoll reminds you to create at least one cell for the transmitter. The following explains the parameters of a UMTS cell, including the parameters for HSDPA and HSUPA functionality. As you create a cell, Atoll calculates appropriate values for some fields based on the information you have entered. You can, if you wish, modify these values. The properties of a UMTS cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned. The Cells tab has the following options: 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 InterCarrier 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.

470

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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. Name: By default, Atoll names the cell after its transmitter, adding the carrier number in parentheses. If you change transmitter name or carrier, Atoll does not update the cell name. You can enter a name for the cell, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names cells, see the Administrators Manual. ID: You can enter an ID for the cell. This is a user-definable network-level parameter for cell identification. Carrier: The number of the carrier. Active: If this cell is to be active, you must select the Active check box. Max Power (dBm): The maximum available downlink power for the cell. Pilot Power (dBm): The pilot power. SCH power (dBm): The average power of both the synchronisation channels (P-SCH and S-SCH). Note: 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. DL Peak Rate per User (kbps): The downlink peak rate per user in kbps. The DL peak rate per user is the maximum connection rate in the downlink for a user. The DL and UL peak rates are taken into account during power control simulation. UL Peak Rate per User (kbps): The uplink peak rate per user in kbps. The UL peak rate per user is the maximum connection rate in the uplink for a user. The DL and UL peak rates are taken into account during power control simulation. Max DL Load (% Pmax): The percentage of the maximum downlink power (set in Max Power) not to be exceeded. This limit will be taken into account during the simulation if the option DL Load is selected. If the DL load option is not selected during a simulation, this value is not taken into consideration. Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit can be taken into account during the simulation. Total Power (dBm or %): The total transmitted power on downlink is the total power necessary to serve R99 and HSDPA users. This value can be a simulation result or can be entered by the user. Note: 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 Transmitters folder on the Data tab of the Explorer window and selecting Properties from the context menu. Then, on the Global Parameters tab of the Properties dialogue, under DL Load, you can select % Pmax. The total power value is automatically converted and set as a percentage of the maximum power.

UL Load Factor (%): The uplink cell load factor. This factor corresponds to the ratio between the uplink total interference and the uplink total noise. This is the global value of uplink load factor including 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. Comments: If desired, you can enter any comments in this field. Max Number of Intra-carrier Neighbours: The maximum number of intra-carrier neighbours for this cell. This value is used by the intra-carrier neighbour allocation algorithm. Max Number of Inter-carrier Neighbours: The maximum number of inter-carrier neighbours for this cell. This value is used by the inter-carrier neighbour allocation algorithm. Max Number of Inter-technology Neighbours: The maximum number of inter-technology neighbours for this cell. This value is used by the inter-technology neighbour allocation algorithm. Inter-technology UL Noise Rise: This noise rise represents the interference 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 uplink interference-based calculations involving this cell in the simulation. It is not used in predictions (AS Analysis and coverage predictions). In predictions, Atoll calculates the uplink total interference from the UL load factor which includes

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

471

Atoll User Manual inter-technology uplink interference. For more information on inter-technology interference, see "Modelling InterTechnology Interference" on page 662. Inter-technology DL Noise Rise: This noise rise represents the interference created by mobiles of an external network on the mobiles served by this cell on the downlink. This noise rise will be taken into account in all downlink interference-based calculations involving this cell. For more information on inter-technology interference, see "Modelling Inter-Technology Interference" on page 662. Neighbours: You can access a dialogue in which you can set both intra-technology (intra-carrier and inter-carrier) and inter-technology neighbours by clicking the Browse button ( "Planning Neighbours" on page 528. ). For information on defining neighbours, see

Tip:

The Browse button ( ) might not be visible in the Neighbours box if this is a new cell. You can make the Browse button appear by clicking Apply.

HSPA Support: The HSPA functionality supported by the cell. You can choose between None (i.e., R99 only), HSDPA, HSPA (i.e., HSDPA and HSUPA), HSPA+ with transmit diversity or HSPA+ with spatial multiplexing. When HSDPA is supported, the following fields are available: HSDPA Dynamic Power Allocation: If you are modelling dynamic power allocation, the HSDPA Dynamic Power Allocation should be checked. During a simulation, Atoll first allocates power to R99 users and then dynamically allocates the remaining power of the cell to the HS-PDSCH and HS-SCCH of HSDPA users. At the end of the simulation, you can commit the calculated available HSDPA power and total power values to each cell. Note: In the context of dynamic power allocation, the total power cannot exceed the maximum power minus the power headroom.

Available HSDPA Power (dBm): When you are modelling static power allocation, the HSDPA Dynamic Power Allocation check box is cleared and the available HSDPA power is entered in this box. This is the power available for the HS-PDSCH and HS-SCCH of HSDPA users. Power Headroom (dB): The power headroom is a reserve of power that Atoll keeps for Dedicated Physical Channels (DPCH) in case of fast fading. During simulation, HSDPA users will not be connected if the cell power remaining after serving R99 users is less than the power headroom value. HS-SCCH Dynamic Power Allocation: If you are modelling dynamic power allocation the HS-SCCH Dynamic Power Allocation check box should be checked and a value should be entered in HS-SCCH Power (dBm). During power control, Atoll will control HS-SCCH power in order to meet the minimum quality threshold (as defined for each mobility type). The value entered in HS-SCCH Power (dBm) is the maximum power available for each HS-SCCH channel. The calculated power for each HSDPA user during the simulation cannot exceed this maximum value. HS-SCCH Power (dBm): The value for each HS-SCCH channel will be used if you are modelling dynamic power allocation. If you have selected the HS-SCCH Dynamic Power Allocation check box and modelling dynamic power allocation, the value entered here represents a maximum for each HSDPA user. If you have not selected the HS-SCCH Dynamic Power Allocation check box and are modelling static power allocation, the value entered here represents the actual HS-SCCH power per HS-SCCH channel. Number of HS-SCCH Channels: The maximum number of HS-SCCH channels for this cell. Each packet (HSDPA) and packet (HSPA) service 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 HSSCCH channels per cell. Note: HS-SCCH-less operation (i.e., HS-DSCH transmissions without any accompanying HSSCCH) is performed for packet (HSPA - Constant Bit Rate) service users. Therefore, the number of HS-SCCH channels is not taken into account to manage the number of packet (HSPA - Constant Bit Rate) service 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) service users, packet (HSPA) service users and packet (HSPA - Constant Bit Rate) service 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. 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). Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

472

Chapter 7: UMTS HSPA Networks Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order according to a random parameter which corresponds to a combination of the user rank in the simulation and the channel quality indicator (CQI). The random parameter is calculated by giving both the user simulation rank and the CQI a weight of 50%. You can change the default weights by setting the appropriate options in the atoll.ini file. For more information, see the Administrator Manual.

Note:

When HSUPA is supported, the following fields are also available: DL HSUPA Power: The power (in dBm) allocated to HSUPA DL channels (E-AGCH, E-RGCH, and E-HICH). This value must be entered by the user. Max Number of HSUPA Users: The maximum number of HSUPA bearer users (i.e., packet (HSPA) service users and packet (HSPA - Constant Bit Rate) service 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. Note: 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 Transmitters folder on the Data tab of the Explorer window and selecting Properties from the context menu. Then, on the Global Parameters tab of the Properties dialogue, under DL Powers, you can select Relative to Pilot. The SCH power, the CCH power, the HS-SCCH power, and the HSUPA power values are automatically converted and set as relative to the pilot power.

MBMS: You can access a dialogue in which you can set MBMS channel powers and channel data rates by clicking the Browse button ( ). This option is only available if MBMS has been activated. Activating MBMS requires data structure modifications (for more information, see the Administrator Manual). If an MBMS SCCPCH is not used, you should leave the field corresponding to its transmission power empty. The MBMS channel powers are used to calculate the optional MBMS service area Eb/Nt coverage prediction and are taken into account in other calculations in the same way as the other common control channel power, i.e., for the calculation of interference.

Tip:

The Browse button ( ) might not be visible in the MBMS box if this is a new cell. You can make the Browse button appear by clicking Apply.

7.2.1.2

Creating or Modifying a Base Station Element

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: "Creating or Modifying a Site" on page 473 "Creating or Modifying a Transmitter" on page 474 "Creating or Modifying a Cell" on page 474.

7.2.1.2.1

Creating or Modifying a Site

You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 467, through the sites Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create or modify a site: 1. If you are creating a new site: a. Click the Data tab in the Explorer window. b. Right-click the Sites folder. The context menu appears. c. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 7.272 on page 467). 2. If you are modifying the properties of an existing site: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Sites folder.

c. Right-click the site you want to modify. The context menu appears. d. Select Properties from the context menu. The sites Properties dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

473

Atoll User Manual 3. Modify the parameters described in "Site Description" on page 467. 4. Click OK.

Tip:

If you are creating several sites at the same time, or modifying several existing sites, you can do it quickly by editing or pasting the data directly in the Sites table. You can open the Sites table by right-clicking the Sites folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

7.2.1.2.2

Creating or Modifying a Transmitter

You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 468, through the transmitters Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create or modify a transmitter: 1. If you are creating a new transmitter: a. Click the Data tab in the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 7.273). 2. If you are modifying the properties of an existing transmitter: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Transmitters folder.

c. Right-click the transmitter you want to modify. The context menu appears. d. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Modify the parameters described in "Transmitter Description" on page 468. 4. 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 474.

Tips: 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 right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. 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.3

Creating or Modifying a Cell

You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Definition" on page 470, through the Properties dialogue of the transmitter where the cell is located. To create or modify a cell: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Definition" on page 470. 7. Click OK.

474

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Tips: If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 59), or import data into the table (see "Importing Tables from Text Files" on page 63). If you want to add a cell to an existing transmitter on the map, you can add the cell by rightclicking the transmitter and selecting New Cell from the context menu.

7.2.1.3

Placing a New Station Using a Station Template

In Atoll, a station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio toolbar, select a template from the list.

2. Click the New Transmitter or Station button (

) in the Radio toolbar.

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.

Tips:

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 38. If you let the pointer rest over the station you have placed, Atoll displays its tip text with its exact coordinates, allowing you to verify that the location is correct.

You can also place a series of stations using a Atoll template. You do this by defining an area on the map where you want to place the stations. Atoll calculates the placement of each station according to the defined hexagonal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 476. To place a series of stations within a defined area: 1. In the Radio toolbar, select a template from the list. 2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of stations created from the same station template.

Note:

If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this template is not defined. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 476.

3. Draw a zone delimiting the area where you want to place the series of stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

475

Atoll User Manual Atoll fills the delimited zone with new stations and their hexagonal shapes. Station objects such as sites and transmitters are also created and placed into their respective folders. You can work with the sites and transmitters in these stations as you work with any station object, adding, for example, another antenna to a transmitter.

Placing a Station on an Existing Site

When you place a new station using a station template as explained in "Placing a New Station Using a Station Template" on page 475, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place a station on an existing site: 1. On the Data tab, clear the display check box beside the Hexagonal Design folder. 2. In the Radio toolbar, select a template from the list. 3. Click the New Station button ( ) in the Radio toolbar.

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

Managing Station Templates

Atoll comes with UMTS station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio toolbar (see Figure 7.275).

Figure 7.275: The Radio toolbar In this section, the following are explained: "Creating or Modifying a Station Template" on page 476 "Copying Properties from One Station Template to Another" on page 480 "Modifying a Field in a Station Template" on page 480 "Deleting a Station Template" on page 481.

7.2.1.4.1

Creating or Modifying a Station Template

When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. As well, you can modify the properties of any station template. To create or modify a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. You can now create a new station template or modify an existing one: To create a new station template: Under Station Templates, select the station template that most closely resembles the station template you want to create and click Add. The Properties dialogue appears. To modify an existing station template: Under Station Templates, select the station template whose properties you want to modify and click Properties. The Properties dialogue appears.

4. Click the General tab of the Properties dialogue. On this tab (see Figure 7.276), you can modify the following: the Name of the station template, the number of Sectors, each with a transmitter, and the Hexagon Radius, i.e., the theoretical radius of the hexagonal area covered by each sector.

476

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.276: Station Template Properties dialogue General tab Under Main Antenna, you can modify the following: the antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Height of the antenna 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 Mechanical Downtilt, and the Additional Electrical Downtilt. Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

5. Click the Transmitter tab. On this tab (see Figure 7.277), if the Active check box is selected, you can modify the following: Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station (BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 468. The information in the real Total Losses in transmission and reception boxes is calculated from the information you entered in the Equipment Specifications dialogue (see Figure 7.274 on page 470). 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 prediction studies 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 wish. Any value you enter must be positive. The information in the real BTS Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if you wish. 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 660. 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).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

477

Atoll User Manual

Figure 7.277: Station Template Properties dialogue Transmitter tab 6. Click the W-CDMA/UMTS tab. In this tab (see Figure 7.278), you modify the Carriers (each corresponding to a cell) that this station supports. For information on carriers and cells, see "Cell Definition" on page 470. You can select the Carrier numbers for each sector of the station template. To select the carriers to be added to the sectors of a base station created using this station template: i. Click the Browse button ( ). The Carriers per Sector dialogue appears.

ii. In the Carriers per Sector dialogue, select the carriers to be created for each sector of the station. iii. Click OK.

Figure 7.278: Station Template Properties dialogue W-CDMA/UMTS tab Under Primary Scrambling Code, you can modify the Reuse Distance, and the scrambling code Domain. Under Power, you can select the Power Shared Between Cells check box. As well, you can modify the Pilot, the SCH, the Other CCH powers, and the AS Threshold.

478

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Under Simulation Constraints, you can modify the Max Power, the Max DL Load (defined as a percentage of the maximum power), the DL Peak Rate/User, the Max UL Load Factor, and the UL Peak Rate/User. Under Load Conditions, you can modify the Total Transmitted Power, the UL Load Factor, and the UL Reuse Factor. Under Inter-technology Interferences, you can modify the UL and DL noise rise which respectively model the effect of terminals and stations of an external network on the network cells and the effect of terminals of an external network interfering the mobiles served by the network cells. For more information on inter-technology interferences, See "Modelling Inter-Technology Interference" on page 662. You can also modify the Number of Uplink and Downlink Channel Elements, the Max Iub Uplink and Downlink Backhaul Throughputs and select the Equipment.

7. Click the HSPA/HSPA+ tab. On this tab (see Figure 7.279), you can define the HSPA functionality supported by the cells. You can choose between None (i.e., R99 only), HSDPA, HSPA (i.e, HSDPA and HSUPA), HSPA+ (transmit diversity) or HSPA+ (spatial multiplexing). When HSDPA functionality is supported, you can modify the following under HSDPA (for more information on the fields, see "Cell Definition" on page 470): 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, you let Atoll allocate the HSDPA power to cells during the simulation. Atoll first allocates power to R99 users and then dynamically allocates the remaining power of the cell to the HS-PDSCH and HS-SCCH of HSDPA users. At the end of the simulation, you can commit the calculated available HSDPA power and total power values to each cell. Under 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, and the Number of Users.

Under HSUPA, if HSUPA functionality is supported, you can modify the following (for more information on the fields, see "Cell Definition" on page 470): You can modify the DL Power, the UL Load, the Max Number of Users, and the Number of Users.

Figure 7.279: Station Template Properties dialogue HSDPA tab 8. Click the Neighbours tab. In this tab (see Figure 7.280), you can modify the Max Number of Intra- and Inter-Carrier Neighbours and the Max Number of Inter-Technology Neighbours. For information on defining neighbours, see "Planning Neighbours" on page 528.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

479

Atoll User Manual

Figure 7.280: Station Template Properties dialogue Neighbours tab 9. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Sites table, or if you have defined an additional field in the Station Template Properties dialogue. 10. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.

7.2.1.4.2

Copying Properties from One Station Template to Another

You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Station Templates from the context menu. The Station Templates table appears. 4. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy from and paste them into the row corresponding to the station template you want to modify.

7.2.1.4.3

Modifying a Field in a Station Template

To modify a field in a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Select the template in the Available Templates list. 4. Click the Fields button. 5. In the dialogue that appears, you have the following options: Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Types Data Table" on page 54) for it to appear as an option in the station template properties. To add a new field: i. Click the Add button. The Field Definition dialogue appears.

ii. Enter a Name for the new field. This is the name that will be used in database. iii. If desired, you can define a Group that this custom field will belong to. When you open an Atoll document from a database, you can then select a specific group of custom fields to be loaded from the database, instead of loading all custom fields. iv. In Legend, enter the name for the field that will appear in the Atoll document. v. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/ Time, and Currency. If you choose text, you can also set the field Size (in characters), and create a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER after each one. vi. Enter, if desired, a Default value for the new field. vii. Click OK to close the Field Definition dialogue and save your changes. Delete: To delete a user-defined field: i. Select the user-defined field you want to delete.

ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you close the dialogue. Properties: To modify the properties of a user-defined field: i. Select the user-defined field you want to modify.

ii. Click the Properties button. The Field Definition dialogue appears. iii. Modify any of the properties as desired. iv. Click OK to close the Field Definition dialogue and save your changes. 6. Click OK.

480

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

7.2.1.4.4

Deleting a Station Template

To delete a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Under Station Templates, select the station template you want to delete and click Delete. The template is deleted. 4. Click OK.

7.2.1.5

Duplicating an Existing Base Station

You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same site, transmitter, and cell parameter values as the original one. Duplicating a base station allows you to: Quickly create a new base station with the same settings as the original base station in order to study the effect of a new base station on the coverage and capacity of the network, and Quickly create a homogeneous network with stations that have the same characteristics.

To duplicate an existing base station: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Sites folder.

3. Right-click the site you want to duplicate. The context menu appears. 4. From the context menu, select one of the following: Select Duplicate > 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. 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.

You can now place the new base station on the map using the mouse. 5. In the map window, move the pointer over the map to where you would like to place the new base station. The exact coordinates of the pointers current location are visible in the Status bar.

Figure 7.281: Placing a new base station

Tips:

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 38. If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact coordinates, allowing you to verify that the location is correct.

6. Click to place the duplicate base station. A new base station is placed on the map. The site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original base station with each name marked as "Copy of." The site, transmitters, and cells of the duplicate base station have the same settings as those of the original base station. All the remote antennas and repeaters of any transmitter on the original site are also duplicated. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate station. For more information on the site, transmitter, subcell, and TRX properties, see "Definition of a Base Station" on page 467.

7.2.2

Creating a Group of Base Stations

You can create base stations individually as explained in "Creating a UMTS Base Station" on page 467, or you can create one or several base stations by using station templates as explained in "Placing a New Station Using a Station Template" on page 475. However, if you have a large data-planning project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

481

Atoll User Manual

Note:

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 96.

You can import base station data in the following ways: Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files" on page 61. For information on importing table data, see "Importing Tables from Text Files" on page 63. Note: You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio toolbar. For information, see "Placing a New Station Using a Station Template" on page 475.

7.2.3

Modifying Sites and Transmitters Directly on the Map

In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu on the Data tab of the Explorer window. However, in a complex radio-planning project, it can be difficult to find the data object in the Data tab, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. If there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: "Selecting One of Several Transmitters" on page 31 "Moving a Site Using the Mouse" on page 31 "Moving a Site to a Higher Location" on page 31 "Changing the Azimuth of the Antenna Using the Mouse" on page 31 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32.

7.2.4

Display Tips for Base Stations

Atoll allows to you to display information about base stations in a number of different ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object types data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information will lead to a cluttered display. For information on defining the label, see "Defining the Object Type Label" on page 35. Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip 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 every field in that object types data table, including from fields that you add. For information on defining the tooltips, see "Defining the Object Type Tip Text" on page 36. 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 "Defining the Display Type" on page 33.

482

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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 "Defining the Display Type" on page 33.

7.2.5

Creating a Dual-Band UMTS Network

In Atoll, you can model a dual-band UMTS network, i.e., a network consisting of 2100 MHz and 900 MHz transmitters, in one document. Creating a dual-band UMTS network consists of the following steps: 1. Defining the two frequency bands in the document (see "Defining Frequency Bands" on page 652). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Managing Calculations in Atoll). 3. Assigning a frequency band, with its propagation model, to each transmitter (see "Transmitter Description" on page 468). 4. Defining the frequency bands with which terminals are compatible (see "Modelling Terminals" on page 513).

7.2.6

Creating a Repeater
A repeater receives, amplifies, and re-transmits the radiated or conducted RF carrier both in downlink and uplink. It has a donor side and a server side. The donor side receives the signal from a donor transmitter, repeater, or remote antenna. This signal may be carried by different types of links such as radio link or microwave link. The server side re-transmits the received signal. Atoll models RF repeaters and microwave repeaters. The modelling focuses on: The additional coverage these systems provide to transmitters in the downlink. The UL total gain value in service areas studies (effective service area and UL Eb/Nt service area) and the noise rise generated at the donor transmitter by the repeater.

In this section, the following are explained: "Creating and Modifying Repeater Equipment" on page 483 "Placing a Repeater on the Map Using the Mouse" on page 484 "Creating Several Repeaters" on page 484 "Defining the Properties of a Repeater" on page 484 "Tips for Updating Repeater Parameters" on page 485. Note: Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor transmitter are amplified.

7.2.6.1

Creating and Modifying Repeater Equipment

You can define repeater equipment to be assigned to each repeater in the network. To create or modify repeater equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Repeaters > Equipment from the context menu. The Repeater Equipment table appears. 4. To create repeater equipment, enter the following in the row marked with the New Row icon ( a. Enter a Name and Manufacturer for the new equipment. b. Enter a Noise Figure. The repeater causes a rise in noise at the donor transmitter, so the noise figure is used to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive value. c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain using the buttons to the right of the Amplification box ( dialogue. ) on the General tab of the repeater Properties ):

e. Enter the maximum power that the equipment can transmit on the downlink in the 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

483

Atoll User Manual 5. To modify repeater equipment, change the parameters in the row containing the repeater equipment you wish to modify.

7.2.6.2

Placing a Repeater on the Map Using the Mouse

In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder of the Explorer windows Data tab, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Repeater from the menu. 4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tooltip and label display the same information as displayed for the donor. As well, its tooltip identifies the repeater and the donor. In the Explorer window, the repeater is found in the Transmitters folder of the Data tab under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 484. Note: You can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter, repeater, or remote antenna. ) on the Radio toolbar.

7.2.6.3

Creating Several Repeaters

In Atoll, the characteristics of each repeater are stored in the Repeaters table. You can create several repeaters at the same time by pasting the information into the Repeaters table: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document. Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

7.2.6.4

Defining the Properties of a Repeater

To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or from the Transmitters folder of the Explorer windows Data tab. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: You can change the Name of the repeater. By default, repeaters are named "RepeaterN" where "N" is a number assigned as the repeater is created. You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another repeater, or a remote antenna. Clicking the Browse button ( ) opens the Properties dialogue of the donor.

You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Properties dialogue of the site. You can enter a Position relative to site location, if the repeater is not located on the site itself. You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties dialogue of the equipment. You can change the Amplification gain. The amplification gain is used in the link budget to evaluate the repeater total gain.

4. Click the Donor Side tab. You can modify the following parameters: Under Donor-Repeater Link, select a Link Type. If you select Microwave Link, enter the Propagation Losses and continue with step 5. If you select Air Link, 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.

484

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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. Important: If you want to create a remote antenna, you must select Optical Fibre Link. If you selected Air Link under Donor-Repeater Link, enter the following information under Antenna: i. Select a Model from the list. You can click the Browse button ( antenna. ) to access the properties of the

ii. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the transmitter as given by the DTM. iii. Enter the Azimuth and the Mechanical Downtilt. Note: You can click the Calculate button to update azimuth and downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.

If you selected Air Link 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 ( the feeder. ) to access the properties of

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 Data tab of the Explorer window) are calculated. Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received from the repeater. The UL total gain value is considered in UL Eb/Nt service area studies. The DL total gain is applied to each power (pilot power, SCH power, etc.). It takes into account losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder losses). The UL total gain is applied to each terminal power. It takes into account losses between the donor transmitter and the repeater, donor part characteristics (donor antenna gain, transmission feeder losses), amplification gain and coverage part characteristics (coverage antenna gain and reception feeder losses). Under Antennas, you can modify the following parameters: i. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the site as given by the DTM.

ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and, if applicable, the Additional Electrical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater coverage side correspond to the characteristics of the donor. iii. 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. For information on working with data tables, see "Working with Data Tables" on page 53. Under Feeders, you can modify the following information: i. Select a Type of feeder from the list. You can click the Browse button ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at Reception. Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.

6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

7.2.6.5

Tips for Updating Repeater Parameters

Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: You can update the calculated azimuth and downtilt of the donor-side antennas of all repeaters by selecting Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

485

Atoll User Manual You can update the UL and DL total gains of all repeaters by selecting Repeaters > Calculate Gains from the Transmitters context menu. Note: You can prevent Atoll from updating the UL and DL total gains of selected repeaters by creating a custom field called "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 31) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32).

7.2.7

Creating a Remote Antenna

Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optic fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise. In certain cases, you may want to model a remote antenna with equipment or a remote antenna connected to a base station that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a Repeater" on page 483. In this section, the following are explained: "Placing a Remote Antenna on the Map Using the Mouse" on page 486 "Creating Several Remote Antennas" on page 486 "Defining the Properties of a Remote Antenna" on page 487 "Tips for Updating Remote Antenna Parameters" on page 487.

7.2.7.1

Placing a Remote Antenna on the Map Using the Mouse

In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the Transmitters folder of the Explorer windows Data tab, or directly on the map. Note: Ensure that the remote antennas donor transmitter does not have any antennas.

2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Remote Antenna from the menu.

) on the Radio toolbar.

4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tooltip and label display the same information as displayed for the donor transmitter. As well, its tooltip identifies 5. the remote antenna and the donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 487. Note: You can see to which base station the remote antenna is connected by clicking it; Atoll displays a link to the donor transmitter.

7.2.7.2

Creating Several Remote Antennas

In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. You can create several remote antennas at the same time by pasting the information into the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document.

486

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

7.2.7.3

Defining the Properties of a Remote Antenna

To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or from the Transmitters folder of the Explorer windows Data tab. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: You can change the Name of the remote antenna. By default, remote antennas are named "RemoteAntennaN" where "N" is a number assigned as the remote antenna is created. You can change the Donor transmitter by selecting it from the Donor list. Clicking the Browse button ( opens the Properties dialogue of the donor transmitter. )

You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the site. You can enter a Position relative to site location, if the remote antenna is not located on the site itself. Note: 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 Data tab of the Explorer window) are calculated. Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received from the remote antenna. The UL total gain value is considered in UL EbNt service area studies. The DL total gain is applied to each power (pilot power, SCH power, etc.). It takes into account losses between the donor transmitter and the remote antenna. The UL total gain is applied to each terminal power. It takes into account losses between the donor transmitter and the remote antenna. Under Antennas, you can modify the following parameters: i. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the transmitter as given by the DTM. ) to access the

ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( properties of the antenna. Then, enter the Azimuth and the Mechanical Downtilt.

iii. 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. For information on working with data tables, see "Working with Data Tables" on page 53. Under Feeders, you can modify the following information: i. Select a Type of feeder from the list. You can click the Browse button ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at 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 5: Managing Calculations in Atoll.

7.2.7.4

Tips for Updating Remote Antenna Parameters

Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: You can update the UL and DL total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from the Transmitters context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

487

Atoll User Manual

Note:

You can prevent Atoll from updating the UL and DL total gains of selected remote antennas by creating a custom field called "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 31) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32).

7.2.8

Setting the Working Area of an Atoll Document

When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the sites that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of sites covered by a coverage prediction, each with its own advantages: Filtering the desired sites You can simplify the selection of sites to be studied by using a filter. You can filter sites according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 84. This enables you to keep only the base stations with the characteristics you want to study. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 74. Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated studies in order to see the effects of small changes in site configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot zone. The computation zone defines the area where Atoll computes path loss matrices, coverage studies, Monte Carlo, power control simulations, etc., while the focus zone or hot spot zone is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 496. You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.

7.2.9

Studying a Single Base Station

As you create a site, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of sites can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the site you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of sites once you have optimised the settings for each individual site. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Atoll enables you to assign both a main propagation model, with a shorter radius and a higher resolution, and an extended propagation model, with a longer radius and a lower resolution. By using a calculation radius, Atoll limits the scope of calculations to a defined area. By using two matrices, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter, while reducing calculation time by using an extended matrix with a lower resolution. You can assign a propagation model to all transmitters at once, to a group of transmitters, or to a single transmitter. Assigning a propagation model is explained in "Assigning a Propagation Model" on page 494. In this section, the following are explained: "Making a Point Analysis to Study the Profile" on page 488 "Studying Signal Level Coverage" on page 490.

7.2.9.1

Making a Point Analysis to Study the Profile

In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a UMTS user. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic

488

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks data into account and computes losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 494. To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Profile tab. 5. The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude (in metres) is reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional attenuations peaks. The total attenuation is displayed above the main peak. The results of the analysis are displayed at the top of the Profile tab: The received signal strength of the selected transmitter The propagation model used The shadowing margin and the cell edge coverage probability used for calculating it The distance between the transmitter and the receiver.

You can change the following options at the top of the Profile tab: Transmitter: Select the transmitter from the list. Carriers: Select the carrier to be analysed. Display Geo Data Only: Select the Display Geo Data Only check box if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate nor display signal levels and losses.

6. Right-click the Profile tab to choose one of the following commands from the context menu: Properties: Select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. You can change the following: - Change the X and Y coordinates to change the present position of the receiver. - Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Select Signal Level, Path loss, and Total losses from the Result Type list. - You can select the Indoor Coverage check box to add indoor losses. Link Budget: Select Link Budget to display a dialogue with the link budget. Model Details: Select Model Details to display a text document with details on the displayed profile analysis. Model details are only available for the standard propagation model.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

489

Atoll User Manual Displays data, including received signal, shadowing margin, cell edge coverage probability, propagation model used, and transmitter-receiver distance.

You can select a different transmitter, and choose to display a profile only with a selected carrier.

Fresnel ellipsoid

Line of sight Figure 7.282: Point Analysis Tool - Profile tab

Attenuation with diffraction.

7.2.9.2

Studying Signal Level Coverage

As you are building your radio-planning project, you may want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single site. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. Note: You can use the same procedure to study the signal level coverage of several sites by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 69.

To study the signal level coverage of a single base station: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder and select Group by > Site from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated.

Tip:

If you wish to study only sites by their status, at this step you could group them by status.

3. Select the propagation parameters to be used in the coverage prediction: a. Click the Expand button ( ) to expand the Transmitters folder.

b. Right-click the group of transmitters you want to study. The context menu appears. c. Select Open Table from the context menu. A table appears with the properties of the selected group of transmitters. d. In the table, you can configure two propagation models: one for the main matrix, with a shorter radius and a higher resolution, and another for the extended matrix, with a longer radius and a lower resolution. By calculating two matrices you can reduce the time of calculation by using a lower resolution for the extended matrix and you can obtain more accurate results by using for the main and extended matrices propagation models best suited for each distance. e. In the Main Matrix column: f. Select a Propagation Model Enter a Radius and Resolution.

If desired, in the Extended Matrix column: Select a Propagation Model Enter a Radius and Resolution.

g. Close the table. 4. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. The Study Types dialogue lists the studies available. They are divided into Standard Studies, supplied with Atoll, and Customised Studies. Unless you have already created some customized studies, the Customised Studies list will be empty. 5. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears.

490

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 6. You can configure the following parameters in the Properties dialogue: General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient:

Size of the Coverage Prediction

City Centre City County State Country

Display Resolution
5m 20 m 50 m 100 m According to the size of the country

Note:

If you create a new coverage prediction from the context menu of either the Transmitters or Predictions folder, you can select the sites using the Group By, Sort, and Filter buttons under Configuration. Because you already selected the target sites, however, only the Filter button is available.

Condition tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel (see Figure 7.283). At the top of the Condition tab, you can set the signal level range to be considered. In Figure 7.283, a signal level less than or equal to -120 dBm will be considered. Under Server, select "All" to consider signal levels from all servers. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "All" to have all carriers taken into account. The coverage prediction displays the strength of the received pilot signal.

Figure 7.283: Condition settings for a signal level coverage prediction Display tab: You can modify how the results of the coverage prediction will be displayed. Under Display Type, select "Value Intervals." Under Field, select "Best Signal Level." Selecting "All" or "Best Signal Level" on the Conditions tab will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 32. You can create a tooltip 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 tooltip. You can select the Add to Legend check box to add the displayed value intervals to the legend.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

491

Atoll User Manual

Note:

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.

7. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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 on the Data tab. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button ( ) beside the coverage prediction in the Predictions ). ), Atoll only calculates unlocked coverage predictions (

7.2.10

Studying Base Stations

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Figure 7.284 gives an example of a computation zone. In Figure 7.284, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction.

Figure 7.284: An example of a computation zone Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main propagation model with a shorter radius (displayed with a blue square in Figure 7.284) and a higher resolution and an extended propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower resolution path loss matrices outside the area covered by the main propagation model. In this section, the following are explained: "Path Loss Matrices" on page 493 Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

492

Chapter 7: UMTS HSPA Networks "Assigning a Propagation Model" on page 494 "The Calculation Process" on page 496 "Creating a Computation Zone" on page 496 "Setting Transmitters or Cells as Active" on page 497 "Signal Level Coverage Predictions" on page 498 "Analysing a Coverage Prediction" on page 501 "UMTS-Specific Studies" on page 509 "HSDPA Coverage Prediction" on page 525 "HSUPA Coverage Prediction" on page 527 "Printing and Exporting Coverage Prediction Results" on page 528.

7.2.10.1

Path Loss Matrices

Path loss is caused by objects in the transmitter-receiver path and is calculated by the propagation model. In Atoll, the path loss matrices are needed for all base stations that are active, filtered and whose propagation zone intersects a rectangle containing the computation zone (for an explanation of the computation zone, see "Studying Signal Level Coverage" on page 490) and must be calculated before predictions and simulations can be made.

Storing Path Loss Matrices

Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. in the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: One file per transmitter with the extension LOS for its main path loss matrix A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.

To set the storage location of the path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss matrices and the location for the shared path loss matrices: Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are loading path loss matrices from a shared location, where you store your changes to shared path loss matrices. Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally. Note: Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private Directory.

Caution:

When you save the path loss files externally, the external files are updated as soon as calculations are performed and not only when you save the Atoll document. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it, if you have updated the path loss matrices.

Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the common path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see The Administrator Manual.

5. Click OK.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

493

Atoll User Manual

Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 5. Select one of the following display options: Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.

The Available Results table lists the following information for each displayed path loss matrix: Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a boolean field indicating whether or not the path loss matrix is valid. Origin of Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed.

6. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 7.285) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.

Figure 7.285: Path loss matrix statistics

7.2.10.2

Assigning a Propagation Model

In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 496, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 495, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 495, this is the propagation model that will be used for all transmitters, except for those to which you have assigned a propagation model either individually or as part of a group. Important: 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. 3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 170, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used.

494

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks In this section, the following are explained: "Assigning a Propagation Model to All Transmitters" on page 495 "Assigning a Propagation Model to a Group of Transmitters" on page 495 "Assigning a Propagation Model to One Transmitter" on page 496.

Assigning a Propagation Model to All Transmitters

In Atoll, you can choose a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

6. If desired, under Extended Matrix: Select a Propagation Model Enter a Radius and Resolution.

7. Click OK. The selected propagation models will be used for all transmitters. Note: Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 496 will override this entry.

Assigning a Propagation Model to a Group of Transmitters

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

4. Click the Expand button (

) to expand the Transmitters folder.

5. Right-click the group of transmitters to which you want to assign a main and extended propagation model. The context menu appears. 6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected group. For each transmitter, you can set the propagation model parameters in the following columns: Main Propagation Model Main Calculation Radius (m) Main Resolution (m) Extended Propagation Model Extended Calculation Radius (m) Extended Resolution (m)

7. To enter the same values in one column for all transmitters in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

495

Atoll User Manual

Assigning a Propagation Model to One Transmitter

If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

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

8. Click OK. The selected propagation models will be used for the selected transmitter.

7.2.10.3

The Calculation Process

When you create a coverage prediction and click the Calculate button ( ), Atoll follows the following process: 1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button ( ). ) beside the coverage prediction 3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( in the Predictions folder. Notes: You can stop any calculations in progress by clicking the Stop Calculations button ( the toolbar. ) in

When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.

7.2.10.4

Creating a Computation Zone

To create a computation zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Computation Zone folder. The context menu appears. 4. Select Draw from the context menu. 5. Draw the computation zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. The computation zone is delimited by a red line. If you clear the computation zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a computation zone as follows: Vector Edition toolbar: You can use the New Polygon ( Vector Edition toolbar to draw the computation zone. ) and New Rectangle ( ) buttons available in the

496

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and selecting Use as > Computation Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a computation zone the size of the map window by selecting Fit to Map Window from the context menu. Note: You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: Saving the computation zone in the user configuration: For information on exporting the computation zone in the user configuration, see "Exporting a User Configuration" on page 79. Exporting the computation zone: You can export the computation zone by rightclicking the Focus Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

7.2.10.5

Setting Transmitters or Cells as Active

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Before you define a coverage prediction, you must ensure that all the transmitters on the sites you wish to study have been activated. In the Explorer window, active transmitters are indicated with a red icon ( ) in the Transmitters folder and with the defined colour on the map and inactive transmitters are indicated with an empty icon ( )in the Transmitters folder and on the map. In Atoll, you can also set individual cells on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zones context menu. To set an individual transmitter as active: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter you want to activate. The context menu appears. 4. Select Active Transmitter from the context menu. The transmitter is now active. To set more than one transmitter as active using the Transmitters context menu: 1. Click the Data tab of the Explorer window. 2. Select the transmitters you want to set as active: To set all transmitters as active, right-click the Transmitters folder. The context menu appears. To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and right-click the group of transmitters you want to set as active. The context menu appears.

3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one transmitter as active using the Transmitters table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitters parameters in a second row. 4. For each transmitter that you want to set as active, select the check box in the Active column. To set more than one cell as active using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cells parameters in a row. 4. For each cell that you want to set as active, select the check box in the Active column. To set transmitters as active using a zone: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder.

3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. Note: If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 41.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

497

Atoll User Manual 4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll. Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects. Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the Atoll computing server application on other workstations or on servers. Once the computing server application is installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on the network. For information on distributed calculations, see the Administrator Manual.

7.2.10.6

Signal Level Coverage Predictions

Atoll offers a series of standard coverage predictions that are common to all radio technologies. Coverage predictions specific to UMTS are covered in "UMTS-Specific Studies" on page 509, "HSDPA Coverage Prediction" on page 525, and "HSUPA Coverage Prediction" on page 527. 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 study which will appear in the Study Types dialogue. You can also select Duplicate from the coverage predictions context menu to create a copy. By duplicating an existing prediction that has the parameters you wish 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 import 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 "Exporting a User Configuration" on page 79. The following standard coverage predictions are explained in this section: "Making a Coverage Prediction by Signal Level" on page 498 "Making a Coverage Prediction by Transmitter" on page 499 "Making a Coverage Prediction on Overlapping Zones" on page 500.

7.2.10.6.1

Making a Coverage Prediction by Signal Level

A coverage prediction by signal level allows you to predict the best signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by signal level: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 7.286). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 7.286, a signal level less than or equal to -120 dBm will be considered. Under Server, select "All" to consider all servers. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "All" to have all carriers taken into account. The coverage prediction displays the strength of the received pilot signal.

498

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.286: Condition settings for a coverage prediction by signal level 7. Click the Display tab. 8. Choose to display the results by best signal level. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. Selecting "All" or "Best Signal Level" on the Conditions tab will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. 9. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 7.287).

Figure 7.287: Coverage prediction by signal level

7.2.10.6.2

Making a Coverage Prediction by Transmitter

A coverage prediction by transmitter allows the user to predict which server is the best at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by transmitter: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

499

Atoll User Manual 4. Select Coverage by Transmitter and click OK. The Coverage by Transmitter Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 7.288). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 7.288, a signal level less than or equal to -120 dBm or greater then -85 dBm will be considered. Under Server, select "Best signal level." You can also define a Margin. Atoll will then consider the best signal level on each pixel and any other signal level within the defined margin of the best one. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "All" to have all carriers taken into account.

Figure 7.288: Condition settings for a coverage prediction by transmitter 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Note: 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.

7.2.10.6.3

Making a Coverage Prediction on Overlapping Zones

Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction of overlapping zones on the signal level, path loss, or total losses within a defined range. To make a coverage prediction on overlapping zones: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears.

500

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Overlapping Zones and click OK. The Overlapping Zones Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 7.289). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 7.289, a signal level less than or equal to -120 dBm will be considered. Under Server, select "Best signal level" and define a Margin. Atoll will then consider the best signal level on each pixel and any other signal level within the defined margin of the best one. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "All" to have all carriers taken into account. The coverage prediction displays the strength of the received pilot signal.

Figure 7.289: Condition settings for a coverage prediction on overlapping zones 7. Click the Display tab. For a coverage prediction on overlapping zones, the Display Type "Value Intervals" based on the Field "Number of Servers" is selected by default. Each overlapping zone will then be displayed in a colour corresponding to the number of servers received per pixel. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Note: By changing the parameters selected on the Condition 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.10.7

Analysing a Coverage Prediction

Once you have completed a study, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 490). If several coverage predictions are visible on the map, it may be difficult to clearly see the results of the coverage prediction you wish to analyse.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

501

Atoll User Manual You can select which studies to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following tools are explained: "Displaying the Legend Window" on page 502 "Displaying Coverage Prediction Results Using Tooltips" on page 502 "Using the Point Analysis Reception Tab" on page 502 "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 503 "Viewing Coverage Prediction Statistics" on page 505 "Comparing Coverage Predictions: Examples" on page 506.

7.2.10.7.1

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

7.2.10.7.2

Displaying Coverage Prediction Results Using Tooltips

You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltips. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 490). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined in the Display tab of the coverage prediction properties (see Figure 7.290).

Figure 7.290: Displaying coverage prediction results using tooltips

7.2.10.7.3

Using the Point Analysis Reception Tab

Once you have calculated the coverage prediction, you can use the Point Analysis tool. 1. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 7.291). The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer location is displayed in the tooltip. 3. At the top of the Reception tab, select the carrier to be analysed.

502

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.291: Point Analysis Tool - Reception tab 4. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue appears. Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select the Indoor Coverage check box to add indoor losses.

You can also click the Results tab to get even more information than in the Reception tab. The results tab displays the current position and height of the receiver, the clutter class it is situated on, and for each transmitter, its signal level (or RSCP), its path loss, Ec/Io, DL and UL Eb/Nt values, Scrambling Code.

7.2.10.7.4

Creating a Focus or Hot Spot Zone for a Coverage Prediction Report

The focus and hot spot zones define an area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spot zones in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the area where Atoll computes path loss matrices, coverage studies, Monte Carlo, power control simulations, etc., while the focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones. To define a focus zone or hot spot zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. Select Draw from the context menu. 5. Draw the focus or hot spot zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the focus or hot spot zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot zone by right-clicking it and selecting Use as > Focus Zone or Use as > New Hot Spot from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot spot zones, you can import the name given to each zone as well. Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map Window from the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

503

Atoll User Manual

Notes: You can save the focus zone or hot spot zones, so that you can use it in a different Atoll document, in the following ways: Saving the focus zone in the user configuration: For information on exporting the focus zone in the user configuration, see "Exporting a User Configuration" on page 79. - Exporting the focus zone or hot spot zones: You can export the focus zone or hot spot zones by right-clicking the Focus Zone or the Hot Spot Zones folder on the Data tab of the Explorer window and selecting Export from the context menu.. You can include population statistics in the focus or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. -

7.2.10.7.5

Displaying a Coverage Prediction Report

Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage predictions Properties dialogue. The coverage prediction report is displayed in a table. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 58. Atoll bases the report on the area covered by the focus zone and hot spot zones; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot zone must be defined before you display a report; it is not necessary to define it before computing coverage. The focus or hot spot zone does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 503. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. The Open dialogue appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the focus zone if available or on the hot spot zones and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. 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 to move it up or

504

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. a appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 4. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. 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 spot zone: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. 2. Display the report as explained above. 3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears. 4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the population map: "Population" (Population): The number of inhabitants covered. "Population" (% Population): The percentage of inhabitants covered. "Population" (Population [total]: The total number of inhabitants inside the zone.

Atoll saves the names of the columns you select and will automatically select them the next time you create a coverage prediction report. 5. Click OK. If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be value data (revenue, number of customers, etc.) or density data (revenue/km, number of customer/km, etc.). Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable Versus Non Integrable Data" on page 129.

7.2.10.7.6

Viewing Coverage Prediction Statistics

Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage study colours, interval steps, and shading as defined in the Display tab of the coverage predictions Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spot zones are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before computing coverage. For information on defining a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 503. To display the statistics on a coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction whose statistics you want to display. The context menu appears. 4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined by the focus zone (see Figure 7.292). Under Histogram Based on Covered Areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Detailed Results section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics Based on Study Conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

505

Atoll User Manual

Figure 7.292: Histogram of a coverage prediction by signal level

7.2.10.7.7

Comparing Coverage Predictions: Examples

Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison study coverage in one of the following ways: Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both studies 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 studies are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).

To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. 6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage between them. In this section, the following examples are explained: "Example 1: Studying the Effect of a New Base Station" on page 506 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 508.

Example 1: Studying the Effect of a New Base Station

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how you can verify if a newly added base station improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 498. The results are displayed in Figure 7.293. An area with poor coverage is visible on the right side of the figure.

506

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.293: Signal level coverage prediction of existing network A new base station is added, either by creating the site and adding the transmitters, as explained in "Creating a UMTS Base Station" on page 467, or by placing a station template, as explained in "Placing a New Station Using a Station Template" on page 475. Once the new site base station been added, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new site (see Figure 7.294).

Figure 7.294: Signal level coverage prediction of network with new base station Now you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be displayed. You can choose among:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

507

Atoll User Manual Intersection Union Difference

In order to see what changes adding a new base station made, you should choose Difference. 5. Click OK to create the comparison. The comparison in Figure 7.295, shows clearly the area covered only by the new base station.

Figure 7.295: Comparison of both signal level coverage predictions

Example 2: Studying the Effect of a Change in Transmitter Tilt

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 499. The results are displayed in Figure 7.296. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated with a red oval in the figure.

Figure 7.296: Coverage prediction by transmitter of existing network You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue. Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original coverage prediction by can be copied by selecting Duplicate from its context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see Figure 7.297).

508

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.297: Coverage prediction by transmitter of network after modifications As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change in coverage, you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be displayed. You can choose among: Intersection Union Difference

In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The increase in coverage, seen in only the second coverage prediction, will be immediately clear. 5. Click OK to create the comparison. The comparison in Figure 7.298, shows clearly the increase in coverage due to the change in antenna tilt.

Figure 7.298: Comparison of both transmitter coverage predictions

7.2.10.8

UMTS-Specific Studies
In UMTS, the quality of the signal and the size of the area that can be covered are influenced by the network load. As the network load increases, the area a cell can effectively cover decreases. For this reason, the network load must be defined in order to calculate UMTS-specific studies. If you have traffic maps, you can do a Monte-Carlo simulation to model power control and evaluate the network load for a generated user distribution. If you do not have traffic maps, Atoll can calculate the network load using the UL load factor and DL total power defined for each cell.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

509

Atoll User Manual In this section, the UMTS-specific coverage predictions will be calculated using UL load factor and DL total power parameters defined at the cell level. For the purposes of these studies, each pixel is considered a non-interfering user with a defined service, mobility type, and terminal. Before making a coverage prediction, you will have to set the UL load factor and DL total power and the parameters that define the services and users. These are explained in the following sections: "Setting the UL Load Factor and the DL Total Power" on page 510. "Service and User Modelling" on page 510.

Several different types of UMTS-specific coverage predictions are explained in this section. The following quality studies are explained: "Making a Pilot Signal Quality Prediction" on page 515 "Studying Service Area (EbNt) Downlink or Uplink" on page 516 "Studying Effective Service Area" on page 517.

The following noise studies, also coverage predictions, are explained: "Studying Downlink Total Noise" on page 520 "Calculating Pilot Pollution" on page 521 "Studying Inter-Technology Downlink Noise" on page 522.

Another type of coverage prediction, the handover study, is also explained: "Making a Handover Status Coverage Prediction" on page 522.

You can also make a point analysis using the Point Analysis window. The analysis is calculated using UL load factor and DL total power parameters defined at the cell level and provided for a user-definable probe receiver which has a terminal, a mobility and a service: "Making an AS Analysis" on page 523.

You can define a RSCP threshold to further define how results are displayed. Atoll uses the RSCP threshold to calculate coverage predictions and to make the AS analysis. Atoll checks which pixels have a pilot signal level which exceeds the defined RSCP threshold. Defining the RSCP threshold is explained in the following section: "Defining the RSCP Threshold" on page 515

Interference from an external project can also be modelled. For an explanation of modelling external interference, see "Modelling Inter-Technology Interference" on page 662.

7.2.10.8.1

Setting the UL Load Factor and the DL Total Power

If you are setting the UL load factor and the DL total power for a single transmitter, you can set these parameters on the Cells tab of the transmitters Properties dialogue. However, you can set the UL load factor and the DL total power for all cells using the Cells table. To set the UL load factor and the DL total power using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Enter a value in the following columns: Total Power (dBm) UL Load Factor (%) For a definition of the values, see "Cell Definition" on page 470. 5. To enter the same values in one column for all cells in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

7.2.10.8.2

Service and User Modelling

Before you can model services, you must already have R99 radio bearers defined in your Atoll document. Only the following R99 radio bearer parameters are used in predictions: Max TCH Power (dBm) The type of bearer.

For information on defining R99 radio bearers, "Defining R99 Radio Bearers" on page 654. In this section, the following are explained: "Modelling Services" on page 511 "Creating a Mobility Type" on page 513

510

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks "Modelling Terminals" on page 513.

Modelling Services
Services are the various services available to subscribers. These services can be either circuit-switched or packetswitched services. This section explains how to create a service. However, only the following parameters are used in predictions: R99 bearer parameters Downgrading capabilities Handover capabilities HSPA capabilities Body loss HSPA application throughput parameters

Before you can model services, you must have defined R99 bearers. For information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 654. To create or modify a service: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. Note: You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.

5. You can edit the fields on the General tab to define the new service. Some fields depend on the Type of service you choose. You can change the following parameters: Name: Atoll proposes a name for the new service, but you can change the name to something more descriptive. R99 Radio Bearer: Select an R99 radio bearer from the list. If you want to edit the settings of the selected R99 radio bearer, click the Browse button ( ) to open the bearers Properties dialogue. Type: Select a service type. You can choose between Circuit (R99), Packet (R99), Packet (HSDPA), Packet (HSPA) and Packet (HSPA-Constant Bit Rate). For circuit services, select Circuit (R99). You have the following options: Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for each user during Monte-Carlo simulations. Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate is the average rate obtained by a user of the service. It is used in simulations during user distribution generation to calculate the number of users attempting a connection and to determine their activity status.

For packet services that can only use R99 channels, select Packet (R99). You have the following options: Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for each user during Monte-Carlo simulations. This parameter is used when working with sector traffic maps and user density traffic maps. Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate is the average rate obtained by a user of the service. It is used in simulations during user distribution generation to calculate the number of users attempting a connection and to determine their activity status.

For packet services that can use HSDPA channels, select Packet (HSDPA). Note: The HSDPA service is linked to a R99 bearer in order to manage the connection to the R99-dedicated channel A-DPCH.

You have the following options: 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. Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate is the requested average rate which guarantees a minimum average downlink rate during an HSDPA call. It is used twice in a simulation: once during user distribution generation in order to calculate the number of HSDPA users attempting a connection and then during power control as a quality target to be compared to the real obtained average throughput. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

511

Atoll User Manual For packet services that can use HSDPA and HSUPA channels, select Packet (HSPA). You have the following options: 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. Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate is the requested average rate which guarantees a minimum average rate during an HSUPA call. It is used twice in a simulation: once during user distribution generation in order to calculate the number of HSUPA users attempting a connection and then during power control as a quality target to be compared to the real obtained average throughput. 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.

For packet services requiring a minimum bit rate and using HSPA channels (e.g., Voice Over IP), select Packet (HSPA - Constant Bit Rate). You have the following options: Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for each user during Monte-Carlo simulations. This parameter is used when working with sector traffic maps and user density traffic maps. Guaranteed Bit Rate: Enter the minimum required bit rate that the service should have in order to be available in the uplink and downlink. 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 uplink and downlink E-DPCCH/A-DPCH activity factors have been fixed to 0.1 and cannot be changed. These values are used to estimate the average power on E-DPCCH and A-DPCH channels.

Note:

Preferred Carrier: You can select one of the available carriers or all carriers. The specified carrier is considered in simulation when admitting a transmitter to the mobile active set. If the transmitter uses the specified carrier, Atoll selects it. Otherwise, it will choose another one, using the carrier selection mode defined in the site equipment properties. The carrier specified for the service is not used in predictions (i.e., AS analysis and coverage predictions). In predictions, Atoll considers the carrier selection mode defined in the site equipment properties. If no preferred carrier is specified in the service properties, it will consider the carrier selection mode defined in the site equipment properties. Bearer Downgrading: Select the Bearer Downgrading check box if the service supports bearer downgrading on uplink and downkink. Soft Handoff Allowed: Select the Soft Handoff Allowed check box if you want the network to be able to use soft handoff with this service. Note: 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 in soft handover, select the Soft Handoff Allowed check box. Soft handover will be applied to R99 and HSUPA channels only.

Priority: Enter a priority for this service. "0" is the lowest priority. Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be 3dB.

6. If you selected Circuit (R99) as the Type in step 5., continue to step 7. If you selected either Packet (R99), or Packet (HSDPA), or Packet (HSPA) or Packet (HSPA - Constant Bit Rate) as the Type in step 5., an additional tab, the Packet tab, appears. Parameters available in the Packet tab are used to determine the probability of activity for each user during Monte-Carlo simulations. These parameters are used when working with user profile traffic maps only. Click the Packet tab. In the Packet tab, 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. Under Session, you can set: 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): Enter the minimum size of a packet call in kilobytes in the uplink and downlink. Max Size (Kbytes): Enter the maximum size of a packet call in kilobytes in the uplink and downlink. Average Time Between Two Packets (ms): Enter the average time between two packets in milliseconds in the uplink and downlink.

Under Packet Calls, you can set: -

512

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Under Packet, you can set: Size (Bytes): Enter the packet size in bytes in the uplink and downlink.

7. Click OK.

Creating a Mobility Type

In UMTS, information about receiver mobility is important to efficiently manage the active set: a mobile used by someone travelling a certain speed and a mobile used by a pedestrian will not necessarily be connected to the same transmitters. EcI0 requirements and Eb/Nt targets per radio bearer and per link (up and down) are largely dependent on mobile speed. The following parameters are used in predictions: EcI0 threshold HS-SCCH EcNt Threshold

To create or modify a mobility type: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Mobility Types folder. The context menu appears. 4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears. Note: You can modify the properties of an existing mobility type by right-clicking the mobility type in the Mobility Types folder and selecting Properties from the context menu.

5. On the General tab, you can enter or modify the following parameters in the Mobility Types New Element Properties dialogue: Name: Enter or modify the descriptive name for the mobility type. Average Speed: Enter or modify an average speed for the mobility type. This field is for information only; the average speed is not used by any calculation. EcI0 Threshold: 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: 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.

6. On the MBMS tab, you can define the Eb/Nt versus throughput graph in the Eb/Nt = f(Throughput) field. Clicking the Graph button opens a dialogue in which you can view and edit the Eb/Nt versus. throughput graph. This tab is only available if MBMS has been activated. Activating MBMS requires data structure modifications (for more information, see the Administrator Manual). 7. Click OK.

Modelling 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 onboard navigation device. The following parameters are used in predictions: Receiver equipment Main and secondary bands Maximum terminal power Gain and losses Noise figures Active set size DL rake factor Rho factor Compressed mode capability HSPA capability and HSPA-specific categories: UE category Number of reception antenna ports MUD factor (for HSDPA only).

To create or modify a terminal: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select New from the context menu. The Terminals New Element Properties dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

513

Atoll User Manual

Note:

You can modify the properties of an existing terminal by right-clicking the terminal in the Terminal folder and selecting Properties from the context menu.

5. Click the General tab. You can modify the following parameters: Name: You can change the name of the terminal. Reception Equipment: Select a type of reception equipment from the list. You can create a new type of reception equipment by opening the Reception Equipment table. To open the Reception Equipment table, right-click the Terminals folder in the UMTS Parameters folder on the Data tab and select Reception Equipment from the context menu. Main Band: Select the frequency band with which the terminal is compatible and enter the terminal Noise Figure for the main frequency. Secondary Band: Select a second frequency band with which the terminal is compatible and enter the terminal Noise Figure for the second frequency. Leave the Secondary Band field empty if the terminal works only on one frequency band. Note: There are two different ways of defining dual-band terminals. Depending on the configuration, Atoll processes dual-band terminal users differently in the Monte-Carlo simulation. The first one consists of defining main and secondary frequency bands. This enables you to give a higher priority to one frequency band in the Monte-Carlo simulation (the main frequency band will have the higher priority). A user with such a dual-band terminal will be connected to transmitters using the main frequency band if carriers on this frequency band are not overloaded. In case of overloading, he will be connected to transmitters using the secondary frequency band. The second consists of selecting "All" as main frequency band. This means that the terminal works on any frequency band without any priority. In this case, the user can be connected to transmitters using any frequency band.

In coverage predictions, both configurations give the same results. The priority of frequency bands is not taken into account. Min. Power: Set the minimum transmission power. The minimum and maximum transmission power make up the dynamic range for uplink power control. Max Power: Set the maximum transmission power. Gain: Set the antenna gain. Losses: Set the reception losses. Active Set Size: Set the active set size. The active set size is the maximum number of transmitters to which a terminal can be connected at one time. DL Rake Factor: Set the DL rake factor. This enables Atoll to model the rake receiver on DL. Note: 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 656.

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. Compressed Mode: Check the Compressed Mode check box if the terminal uses compressed mode. Compressed mode is generally used to prepare hard-handover of users with single receiver terminals.

6. Click the HSPA tab. You can define if the terminal supports HSPA. You can choose between None (i.e., R99 support only), HSDPA or HSPA (i.e., HSDPA and HSUPA). Under HSDPA, you can modify the following parameters: UE Category: Select a user equipment category. HSDPA user equipment capabilities are standardised into 22 different categories according to 3GPP specifications. 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 you have selected the HSPA option, you can modify the following parameter under HSUPA:

514

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks UE Category: Select a user equipment category. HSUPA user equipment capabilities are standardised into 7 different categories according to 3GPP specifications.

7. Click OK.

7.2.10.8.3

Defining the RSCP Threshold

To define the minimum pilot RSCP threshold: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Predictions tab. 5. Under Calculation Limitation, enter a Min. Pilot RSCP Threshold. 6. Click OK.

7.2.10.8.4

Making Quality Studies

In Atoll, you can make several predictions to study the quality. In this section, the following quality predictions are explained: "Making a Pilot Signal Quality Prediction" on page 515 "Studying Service Area (EbNt) Downlink or Uplink" on page 516 "Studying Effective Service Area" on page 517 "Studying Service Area (EbNt) for MBMS" on page 518 "Creating a Quality Study Using Quality Indicators" on page 519. Note: A table listing quality indicators (BER, BLER, etc.) to be analysed is available. Quality studies proposed by Atoll depend on quality indicators specified in this table.

Making a Pilot Signal Quality Prediction

A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is received sufficiently well to be added to the probe mobile active set. Atoll calculates the best pilot quality received on each pixel. Then, depending on the coverage prediction definition, it compares this value either to the EcI0 threshold defined for the selected mobility type, or to user-defined EcI0 thresholds. The pixel is coloured if the condition is fulfilled (in other words, if the best EcI0 is higher than the EcI0 mobility threshold or specified EcI0 thresholds). To make a pilot signal quality prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Pilot Reception Analysis (Ec/I0) and click OK. The Pilot Reception Analysis (Ec/I0) Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 7.299). 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. Note: 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 510. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction on a specific carrier or on all carriers of any frequency band for the selected terminal, or for all the carriers of all the frequency bands. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

515

Atoll User Manual

Figure 7.299: Load condition settings for a coverage prediction on pilot quality 7. 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 "Display Properties of Objects" on page 32. 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 quality relative to the EcI0 threshold: Select "Value Intervals" as the Display Type and "EcI0 margin (dB)" as the Field.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying Service Area (EbNt) Downlink or Uplink

Atoll calculates the traffic channel quality (as defined by EbNt) when using the maximum power allowed, i.e., the maximum traffic channel power allowed per cell for downlink and the maximum terminal power for uplink. In the coverage prediction, the downlink or uplink service area is limited by the maximum power allowed and by the pilot quality. If the received pilot quality is insufficient, Atoll will not display the traffic channel quality. The mobile handover status is taken in consideration to evaluate the downlink and uplink traffic channel quality (EbNt). Atoll combines the signal from each transmitter in the probe mobile active set. To make a coverage prediction on service area (Eb/Nt) downlink or uplink: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select one of the following studies and click OK: Service Area (Eb/Nt) Downlink Service Area (Eb/Nt) Uplink

The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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.

516

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Note:

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 510. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. 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. You can select the Downgrading Allowed 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. 7. 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 "Display Properties of Objects" on page 32. 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 Condition tab, select "All" as the Mobility Type. The parameters on the Display tab are automatically set.

For a service area (EbNt) uplink 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.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying Effective Service Area

The effective service area is the intersection zone between the pilot reception area, and the uplink and downlink service areas. In other words, the effective service area prediction calculates where a service actually is available for the probe mobile. To make an effective service area prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Effective Service Area and click OK. The Effective Service Area Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

517

Atoll User Manual You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 510. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. If you want the effective service area prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box. You can also select the Indoor Coverage check box to add indoor losses. You can select the Downgrading Allowed 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. 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying Service Area (EbNt) for MBMS

This coverage prediction is only available if MBMS has been activated. Activating MBMS requires data structure modifications (for more information, see the Administrator Manual). MBMS (Multimedia Broadcast and Multicast Service) offers a solution for broadcasting television channels over SCCPCH channels in UMTS. SCCPCH (FACH) does not perform power control in order to cover the entire cell area. Atoll calculates the MBMS channel quality (as defined by EbNt) using the MBMS power defined for an MBMS SCCPCH channel. In the coverage prediction, the MBMS service area is limited by the maximum power allowed and by the pilot quality. If the received pilot quality is insufficient, Atoll will not display the MBMS channel quality. To make a coverage prediction on the MBMS service area (Eb/Nt): 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Service Area (Eb/Nt) MBMS and click OK. The Service Area (Eb/Nt) MBMS Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 Mobility as defined in "Service and User Modelling" on page 510. The coverage prediction is calculated for an MBMS service. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. You must also select an MBMS Channel. 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. 7. Click the Display tab.

518

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks For the MBMS service area (Eb/Nt) coverage prediction, the Display Type "Value Intervals" based on the Field "EbNt (dB)" is selected by default. Each pixel is displayed in a colour corresponding to the MBMS channel quality. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Creating a Quality Study Using Quality Indicators

You can create a quality study based on a given quality indicators (BER, BLER, or FER). The coverage prediction will show for each pixel the measurement of the selected quality indicator. This type of coverage prediction is not available in the list of standard studies; you can, however, use quality indicators in a study by first ensuring that the parameters of the quality indicators have been correctly set and then creating a coverage prediction, selecting display parameters that use these quality indicators. Before you define the quality study, you must ensure that the parameters of the quality indicators have been correctly set. To check the parameters of the quality indicators: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select Quality Indicators from the context menu. The Quality Indicators table appears. For each quality indicator in the Name column, you can set the following parameters: Used for Packet Services: Select the Used for Packet Services check box if the quality indicator is to be used for packet services. Used for Circuit Services: Select the Used for Circuit Services check box if the quality indicator is to be used for circuit services. Measured Parameter for 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.

5. Close the Quality Indicators table. 6. In the UMTS Parameters folder, right-click the Terminals folder. The context menu appears. 7. Select Reception Equipment from the context menu. The Reception Equipment table appears. "Standard" is the default reception equipment type for all terminals. 8. Double-click the reception equipment type for which you want to verify the correspondence between the measured quality and the quality indicator. The reception equipment types Properties dialogue appears. 9. Click the Quality Graphs tab. 10. Ensure that a Quality Indicator has been chosen for each R99 Bearer. You can edit the values in the DL and UL Quality Indicator Tables by clicking directly on the table entry, or by selecting the Quality Indicator and clicking the Downlink Quality Graphs or the Uplink Quality Graphs buttons. 11. Click OK to close the reception equipment types Properties dialogue. Once you have ensured that the parameters of the quality indicators have been correctly set, you can use the measured quality to create a quality study. How you define a coverage prediction according to the measured quality indicator, depends several parameters: The settings made in the Quality Indicators table The service you want to study The quality indicator you want to use (BER, BLER, or FER) The coverage prediction you want to use (Pilot Reception Analysis, the Service Area Downlink, or Service Area Uplink).

In the following example, you will create a quality study showing BLER, for a user on foot, and with mobile internet access. To create a quality study showing BLER for a user on foot, and with mobile internet access: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Service Area (EbNt) Downlink and click OK. The Service Area (EbNt) Downlink Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name and Resolution of the service area (EbNt) downlink prediction, and add some Comments. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

519

Atoll User Manual 6. Click the Condition 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. Note: 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 a carrier of a frequency band or a frequency band if you want to study a specific carrier or all the carriers of a frequency band for the selected terminal. Otherwise, select "All."

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. You can select the Downgrading Allowed 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. 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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).

7.2.10.8.5

Studying Noise
Atoll has several coverage predictions that enable you to study the downlink total noise, downlink noise rise or pilot pollution. In this section, the following noise predictions are explained: "Studying Downlink Total Noise" on page 520 "Calculating Pilot Pollution" on page 521 "Studying Inter-Technology Downlink Noise" on page 522.

Studying Downlink Total Noise

In the downlink total noise prediction, Atoll calculates and displays the areas where the downlink total noise or the downlink noise rise exceeds a set threshold. To make a downlink total noise or downlink noise rise prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Downlink Total Noise and click OK. The Downlink Total Noise Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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.

520

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 510. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. If you want the downlink total noise or downlink 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. 7. 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. Downlink total noise prediction: When making a downlink total noise prediction, select one of the following in the Field list: Min. Noise Level Average Noise Level Max Noise Level

Downlink noise rise prediction: When making a downlink noise rise prediction, select one of the following in the Field list: Min. Noise Rise Average Noise Rise Max Noise Rise

For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Calculating Pilot Pollution

A transmitter which fulfils all the criteria to enter a mobiles active set but which is not admitted because the active set limit has already been reached is considered a polluter. In the pilot pollution prediction, Atoll calculates and displays the areas where the probe mobile is interfered by the pilot signal from polluter transmitters. To make a pilot pollution prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Pilot Pollution and click OK. The Pilot Pollution Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 510. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

521

Atoll User Manual 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. 7. Click the Display tab. For a pilot pollution prediction, the Display Type "Value Intervals" and the Field "Number of Polluters" are selected by default. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying Inter-Technology Downlink Noise

In the inter-technology downlink noise prediction, Atoll calculates and displays the areas where the downlink noise or noise rise from external base stations and mobiles exceeds a set threshold. For more information on the modelling on intertechnology interference, see "Modelling Inter-Technology Interference" on page 662. To make an inter-technology downlink noise or noise rise prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Inter-technology Downlink Interference and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 a Service, as defined in "Service and User Modelling" on page 510. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. 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. 7. Click the Display tab. The Display Type "Value Intervals" is selected by default. The Field you choose determines which information the prediction makes available, Noise Level or Noise Rise. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

7.2.10.8.6

Making a Handover Status Coverage Prediction

In the handover status prediction, Atoll calculates and displays the zones where a handover can be made. For a handover to be possible, there must be a potential active transmitter, i.e., a transmitter that fulfils all the criteria to enter the mobile active set, and the service chosen by the user must be available.

522

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks You can also use the handover status coverage prediction to display the number of potential active transmitters. To make a handover status coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Handoff Status and click OK. The Handoff Status Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 510. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. If you want the downlink total noise or downlink 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. 7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. To display the handover status: a. Select "Discrete Values" from the Display Type list. b. Select "Status" from the Field list. Depending on the active set size of the terminal and the service capabilities in terms of soft handover, the coverage prediction can display the following values: No handoff: one cell in the mobile active set. Softer: two cells in the mobile active set belonging to the same site. Soft: two cells in the mobile active set, one from Site A and the other from Site B. Softer-Softer: three cells in the mobile active set, belonging to the same site. Softer-Soft: three cells in the mobile active set, two from Site A and the third one from Site B. Soft-Soft: three cells in the mobile active set, one from Site A, one from Site B and one from Site C. Not connected: no cell in the mobile active set.

To display the number of potential active transmitters: a. Select "Value Intervals" from the Display Type list. b. Select "Potential Active Transmitters" from the Field list. The coverage prediction will display the number of potential active transmitters. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

7.2.10.8.7

Making an AS Analysis
The Point Analysis window gives you information on reception for any point on the map. The AS Analysis tab gives you 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 analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. Analysis is based on: The UL load percentage and the DL total power of cells for R99 bearer connection, Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

523

Atoll User Manual The available HSDPA power of cells for HSDPA bearer users, The uplink reuse factor, the uplink load factor due to HSUPA, the maximum uplink load factor of cells and the number of HSUPA users in the cells in case of HSUPA bearer users.

You can make an AS analysis to verify a coverage prediction. In this case, before you make the AS analysis, ensure the coverage prediction you want to use in the AS analysis is displayed on the map. For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 661. To make an AS analysis: 1. Click the Point Analysis button ( Figure 7.301). 2. Click the AS Analysis tab. 3. At the top of the AS Analysis tab, select "Cells Table" from Load Conditions. 4. If you are making an AS analysis to verify a coverage prediction, you can recreate the conditions of the coverage prediction: a. Select the same Terminal, Service, and Mobility studied in the coverage prediction. b. Select the Carrier to be considered. You can make the AS analysis for a specific carrier or for all carriers of the main frequency band of the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. 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. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select the Indoor Coverage check box to add indoor losses. ) on the toolbar. The Point Analysis Tool window appears (see

e. Click OK to close the Properties dialogue. 5. Move the pointer over the map to make an active set analysis for the current location of the pointer. As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 7.300). Information on the current position is given on the AS Analysis tab of the Point Analysis window. See Figure 7.301 on page 525 for an explanation of the displayed information.

Figure 7.300: Point analysis on the map 6. Click the map to leave the point analysis pointer at its current position. To move the pointer again, click the point analysis pointer on the map and drag it to a new position. 7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.

524

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Select the load conditions to use in this analysis (DL Power, UL Load, Select the parameters of the probe user to etc.) from simulations or from the be studied. Cells table. This vertical bar represents the lower boundary of the active set (defined as the signal value of the best server at the current point minus the AS_Threshold defined in the properties of the best server).

The pilot reception in terms of active set components for the set conditions. The active set is displayed in grey. Solid bars indicate the cells which respect the active set constraints. Even if more cells respect the constraints, the active set size is limited to the number defined in the terminal properties and is a function

This vertical bar represents the EcI0 threshold to become the best server (threshold defined in the mobility

The connection status (pilot and uplink and downlink traffic) for the current point. : successful connection : failed connection

Figure 7.301: Point Analysis Tool - AS Analysis tab The bar graph displays the following information: The pilot quality (EcI0) reception of all transmitters using the selected carrier (the colour of the bar colour 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 transmitters in the active set. The pilot and the availability of service on UL and DL.

If there is at least one successful connection (for pilot, downlink, or uplink), double-clicking the icons in the right-hand frame will open a dialogue with additional information.

7.2.10.9

HSDPA Coverage Prediction

The HSDPA coverage prediction allows you to study many HSDPA-related parameters, depending on the parameters defined. Each HSDPA bearer user is associated to an R99-dedicated channel A-DPCH in the uplink and downlink, and must first initiate a A-DPCH connection in order to be able to use HSDPA channels. In the coverage prediction, the HSDPA service area is limited by the pilot quality and the A-DPCH quality. The parameters used as input for the HSDPA coverage prediction are the available HSDPA power, and the total transmitted power for each cell. If the coverage prediction is not based on a simulation, these values are taken from the cell properties. For information about the cell parameters, see "Creating or Modifying a Cell" on page 474. For information on the formulas used to calculate different throughputs, see the Technical Reference Guide. To make an HSDPA coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select HSDPA Coverage and click OK. The HSDPA Coverage Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 Mobility, as defined in "Service and User Modelling" on page 510. For an HSDPA coverage prediction, under Terminal, you must chose an HSDPA-capable terminal and, under Service, you must chose a service with HSDPA. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal,

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

525

Atoll User Manual you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. Under HSDPA Radio Bearer, select either "All" to consider all possible HSDPA radio bearers in the study or an HSDPA radio bearer index to calculate the study for a certain bearer. Display options available in the Display tab depend on what you have selected here. If you want to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box. You can also select the Indoor Coverage check box to add indoor losses. 7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. If you have selected "All" as the HSDPA Radio Bearer in the Condition tab, you can set the following parameters: To analyse the uplink and downlink A-DPCH qualities on the map: 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. 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 analyse the HS-SCCH quality or power: -

To model fast link adaptation for a single HSDPA bearer user or for a defined number of HSDPA users: For a single HSDPA bearer user, Atoll considers one HSDPA bearer user on each pixel and determines the best HSDPA bearer that the user can obtain by considering the entire available HSDPA power of the cell. The HS-PDSCH Ec/Nt 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 Transmitter Properties dialogue (see "Creating or Modifying a Transmitter" on page 474). The MAC rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the MAC rate from the transport block size of the selected HSDPA bearer. The MAC throughput relative to the threshold: Select "MAC Throughput (kbps)" as the Field. The MAC throughput is calculated from the MAC rate. The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays the RLC peak rate that the selected HSDPA bearer can be supplied with. The RLC peak rate is a characteristic of the HSDPA bearer. The RLC peak throughput relative to the threshold: Select "RLC Peak Throughput (kbps)" as the Field. Atoll calculates the RLC peak throughput from the RLC peak rate. The average RLC throughput relative to the threshold: Select "Average RLC Throughput (kbps)" as the Field. The application throughput relative to the threshold: Select "Application Throughput (kbps)" as the Field. Using the RLC peak rate, the BLER, the HSDPA service scaling factor, and the throughput offset, Atoll calculates the application throughput. The application throughput represents the net throughput without coding (redundancy, overhead, addressing, etc.).

Atoll can consider several HSDPA bearer users per pixel. When the coverage prediction is not based on a simulation, this value is taken from the cell properties. Atoll considers the defined number of HSDPA bearer users on each pixel and determines the best HSDPA bearer that each user can obtain. The coverage prediction results displayed are the average results for one user. The available HSDPA power of the cell is shared between the HSDPA bearer users. You can display the following results: The average MAC throughput per mobile relative to the threshold: Select "MAC Throughput per Mobile (kbps)" as the Field. Atoll calculates the average MAC throughput per mobile from the from the MAC throughput of each user. The average RLC throughput per mobile relative to the threshold: Select "RLC Throughput per Mobile (kbps)" as the Field. Atoll calculates the average RLC throughput per mobile from the RLC throughput of each user. The average application throughput per mobile relative to the threshold: Select "Application Throughput per Mobile (kbps)" as the Field. Using the RLC peak rate, the BLER, the HSDPA service scaling factor, and the throughput offset, Atoll calculates the average application throughput per mobile from the application throughput of each user.

If you have selected an HSDPA radio bearer index as the HSDPA Radio Bearer on the Condition tab, you can define settings to display: Where a certain RLC peak rate is available with different cell edge coverage probabilities: On the Condition tab, do not consider shadowing and select an 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. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

526

Chapter 7: UMTS HSPA Networks 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

7.2.10.10

HSUPA Coverage Prediction

The HSUPA coverage prediction allows you to study several HSUPA-related parameters. The parameters used as input for the HSUPA study are the uplink load factor the uplink reuse factor, the uplink load factor due to HSUPA and the maximum uplink load factor for each cell. If the coverage prediction is not based on a simulation, these values are taken from the cell properties. For information about the cell parameters, see "Creating or Modifying a Cell" on page 474. For information on the formulas used to calculate required E-DPDCH Ec/Nt, required terminal power, and different throughputs, see the Technical Reference Guide. To make an HSUPA coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select HSUPA Coverage and click OK. The HSUPA Coverage Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 Mobility, as defined in "Service and User Modelling" on page 510. For an HSUPA coverage prediction, under Terminal, you must chose an HSUPA-capable terminal and, under Service, you must chose a service with HSUPA. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. 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.

When no value is defined in the Cells table, Atoll uses the following default values: Uplink load factor = 50 % Uplink reuse factor = 1 Uplink load factor due to HSUPA = 0 % Maximum uplink load factor = 75 % Number of HSUPA users = 1

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

527

Atoll User Manual 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. 7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. You can set parameters to display the following results: The required E-DPDCH EcNt 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 Ec/Nt. The MAC Rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the MAC rate from the transport block size of the selected HSUPA bearer. The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays the RLC peak rate that the selected HSUPA bearer can supply. The RLC peak rate is a property of the HSUPA bearer. The guaranteed RLC throughput relative to the threshold: Select "Min RLC Throughput (kbps)" as the Field. The average RLC throughput relative to the threshold: Select "Average RLC Throughput (kbps)" as the Field. Atoll calculates the average RLC throughput on the uplink using the early termination probabilities, defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request). The application throughput relative to the threshold: Select "Application Throughput (kbps)" as the Field. Using the RLC peak rate, the BLER, the HSUPA service scaling factor, and the throughput offset, Atoll calculates the application throughput. The application throughput represents the net throughput without coding (redundancy, overhead, addressing, etc.). The average application throughput relative to the threshold: Select "Average Application Throughput (kbps)" as the Field. Atoll calculates the average application throughput on the uplink using the early termination probabilities, defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request).

For information on selecting the best bearer, see the Technical Reference Guide. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

7.2.10.11

Printing and Exporting Coverage Prediction Results

Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. 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 65. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 46. 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 49.

7.2.11

Planning Neighbours
You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you set. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbours only to the cells within the computation zone. The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo tab in the Explorer window is selected. Usually, you will allocate neighbours globally during the beginning of a radio planning project. Afterwards, you will allocate neighbours to base stations or transmitters as you add them. You can use automatic allocation on all cells in the document, or you can define a group of cells either by using a focus zone or by grouping transmitters in the Explorer window. For

528

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks information on creating a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 503. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 69. Atoll supports the following neighbour types in a UMTS network: Intra-technology Neighbours: Intra-technology neighbours are cells defined as neighbours that also use UMTS. Intra-technology neighbours can be divided into: Intra-carrier Neighbours: Cells defined as neighbours which perform handover using the same carrier. Inter-carrier Neighbours: Cells defined as neighbours which perform handover using a different carrier.

Inter-technology Neighbours: Inter-technology neighbours are cells defined as neighbours that use a technology other than UMTS.

In this section, the following are explained: "Importing Neighbours" on page 529 "Defining Exceptional Pairs" on page 529 "Configuring Importance Factors for Neighbours" on page 529 "Allocating Neighbours Automatically" on page 530 "Checking Automatic Allocation Results" on page 533 "Allocating and Deleting Neighbours per Cell" on page 536 "Calculating the Importance of Existing Neighbours" on page 538 "Checking the Consistency of the Neighbour Plan" on page 540 "Exporting Neighbours" on page 541.

7.2.11.1

Importing Neighbours
You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Data tab of the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 63.

7.2.11.2

Defining Exceptional Pairs

In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs can be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Right-click the cell for which you want to define neighbour constraints. The context menu appears. 5. Select Record Properties from the context menu. The cells Properties dialogue appears. 6. Click the Intra-technology Neighbours tab. 7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( a. Select the cell from the list in the Neighbours column. b. In the Status column, select one of the following: Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell. ):

8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table by right-clicking the Transmitters folder and selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.

7.2.11.3

Configuring Importance Factors for Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible intra- and inter-carrier neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

529

Atoll User Manual To configure the importance factors for neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. Select the Intra-carrier Neighbours tab. On the Intra-carrier Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency Factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 530. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 530.

5. Select the Inter-carrier Neighbours tab. On the Inter-carrier Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 530.

6. Click OK.

7.2.11.4

Allocating Neighbours Automatically

Atoll can automatically allocate both intra- and inter-carrier neighbours in a UMTS network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. By setting an option in the atoll.ini file, you can prevent Atoll from allocating inter-carrier neighbours to cells located on sites whose equipment does not support the compressed mode. For more information, see the Administrator Manual. To automatically allocate intra-carrier UMTS neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Intra-Carrier Neighbours tab. You can set the following parameters: Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour. Max. Number of Neighbours: Set the maximum number of intra-carrier neighbours that can be allocated to a cell. This value can be either set here for all transmitters, or specified for each transmitter in the Cells table. Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. - Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A and possible neighbour cell B. - Min. EcI0: Enter the minimum EcI0 which must be provided by reference cell A in an overlapping area. Reference cell A must also be the best server in terms of pilot quality in the overlapping area. - EcI0 Margin: Enter the maximum difference of EcI0 between reference cell A and possible neighbour cell B in the overlapping area. - DL Load Contributing to I0: You can let Atoll base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). - Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations. % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must overlap the reference cells coverage area. -

5. Select the desired calculation parameters: Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers (Atoll will allocate neighbours to cells using the selected carriers). Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located on the same site as the reference cell to be automatically considered as neighbours. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

530

Chapter 7: UMTS HSPA Networks Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell is the best server, or where the possible neighbour cell is the second best server in the reference cells active set (respecting the handover margin). Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from the list of neighbours of the reference cell. Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 529. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.

6. Click the Importance Weighting button to set the relative importance of possible neighbours: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 5., set the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell. Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 5., set the minimum and maximum importance of a possible neighbour cell being located on the same site as reference cell.

7. Click Calculate. Atoll begins the process of allocating intra-carrier neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance as calculated with the options selected in step 6. Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the reference cell, as identified in the Cell column. Co-site Adjacency Symmetry Coverage Existing

Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell is best server or second best server.

8. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

531

Atoll User Manual To automatically allocate inter-carrier UMTS neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Inter-Carrier Neighbours tab. You can set the following parameters: Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour. Max. Number of Neighbours: Set the maximum number of inter-carrier neighbours that can be allocated to a cell. This value can be either set here for all transmitters, or specified for each transmitter in the Cells table. Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. - Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A and possible neighbour cell B. - Min. EcI0: Enter the minimum EcI0 which must be provided by reference cell A and possible neighbour B in an overlapping area. Possible neighbour B must also be the best server in terms of pilot quality in the overlapping area. - EcI0 Margin: Enter the EcI0 margin relative to the EcI0 of the reference cell A. See the Technical Reference Guide for an explanation of how the EcI0 margin is used in different inter-carrier handover scenarios. - 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. % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must overlap the reference cells coverage area. -

5. Select the desired calculation parameters: Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers (Atoll will allocate neighbours to cells using the selected carriers). Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located on the same site as the reference cell to be automatically considered as neighbours. Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from the list of neighbours of the reference cell. Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 529. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.

6. Click the Importance Weighting button to set the relative importance of possible neighbours: Coverage Factor: Set the minimum and maximum importance of the minimum percentage of shared coverage between the possible neighbour cell and the reference cell. Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 5., set the minimum and maximum importance of a possible neighbour cell being located on the same site as reference cell.

7. Click Calculate. Atoll begins the process of allocating inter-carrier neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance as calculated with the options selected in step 6. Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the reference cell, as identified in the Cell column. Co-site Symmetry Coverage Existing

532

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square kilometres.

8. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue. Notes A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint on the forbidden neighbour will be ignored by the algorithm because the neighbour already exists. When the options Force exceptional pairs and Force symmetry are selected, Atoll considers the constraints between exceptional pairs in both directions in order to respect symmetry. On the other hand, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event Viewer. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Exporting a User Configuration" on page 79.

7.2.11.4.1

Allocating Neighbours to a New Base Station

When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects with the coverage area of the cells of the new base station. To allocate neighbours to a new base station: 1. On the Data tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects" on page 69. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 530.

7.2.11.4.2

Allocating Neighbours to a New Transmitter

When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter. To allocate neighbours to a new transmitter: 1. Click the Data tab of the Explorer window. 2. In the Transmitters folder, right-click the new transmitter. The context menu appears. 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 530.

7.2.11.5

Checking Automatic Allocation Results

You can verify the results of automatic neighbour allocation in the following ways: "Displaying Neighbour Relations on the Map" on page 534 "Displaying the Coverage of Each Neighbour of a Cell" on page 535.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

533

Atoll User Manual

7.2.11.5.1

Displaying Neighbour Relations on the Map

You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

2. Select Display Options from the context menu. The Visual Management dialogue appears. 3. Under Intra-technology Neighbours, select the Display Links check box. 4. Click the Browse button ( ) beside the Display Links check box.

5. The Intra-technology Neighbour Display dialogue appears. 6. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours table, or according to the neighbour carrier. In this case, you can view intra-carrier and inter-carrier neighbour relations on the map. Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

Tip:

You can display the number of handoff attempts for each cell-neighbour pair by first creating a new field of the Type "Integer" in the Intra-Technology Neighbour table for the number of handoff attempts. Once you have imported or entered the values in the new column, you can select this field from the Field list along with "Value Intervals" as the Display Type. For information on adding a new field to a table, see "Adding a Field to an Object Types Data Table" on page 54.

Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you can display or hide neighbour link display types individually. For information on changing display properties, see "Display Properties of Objects" on page 32. 7. Select the Add to Legend check box to add the displayed neighbour links to the legend. 8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each neighbour link. 9. Click OK to save your settings. 10. Under Advanced, select which neighbour links to display: Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations where the selected cell is the reference cell and where the neighbour relation is not symmetric. Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations where the selected cell is neighbour and where the neighbour relation is not symmetric. Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the selected cell and the neighbour.

11. Click OK to save your settings. 12. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 14. Click the Visual Management button ( ) in the Radio toolbar.

15. Click a transmitter on the map to display the neighbour relations. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). Atoll displays the following information (see Figure 7.302) for the selected cell: The symmetric neighbour relations of the selected (reference) cell are indicated by a line. The outward neighbour relations are indicated with a line ending in an arrow pointing at the neighbour (e.g., see Site1_2(0)) in Figure 7.302.). The inward neighbour relations are indicated with a line ending in an arrow pointing at the selected cell (e.g., see Site9_3(0)) in Figure 7.302.).

In Figure 7.302, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is coloured as the reference transmitter as it is neighbour of Site9_3(0) here.

534

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.302: Intra-carrier Neighbours of Site 22_3(0) - Display According to the Neighbour In Figure 7.303, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and inter-carrier neighbour links. In Figure 7.303, all neighbour relations are symmetric.

Figure 7.303: Intra-carrier and Inter-Carrier Neighbours of Site 14_3(0) Note: You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

7.2.11.5.2

Displaying the Coverage of Each Neighbour of a Cell

By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cells neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a "Coverage by transmitter" prediction, with the Display Type set to "Discrete Values" and the Field set to Transmitter (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 499). 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

3. Select Display Options from the context menu. The Visual Management dialogue appears. 4. Under Intra-technology Neighbours, select the Display Coverage Areas check box. 5. Click the Browse button ( ) beside the Display Coverage Areas check box.

6. The Intra-technology Neighbour Display dialogue appears. 7. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neighbours with a unique colour.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

535

Atoll User Manual Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology Neighbours table. Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each coverage area. 9. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 11. Click the Visual Management button ( ) in the Radio toolbar.

12. Click a transmitter on the map to display the coverage of each neighbour. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). Note: Only intra-carrier neighbour coverage areas are displayed.

13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( Radio toolbar.

) in the

7.2.11.6

Allocating and Deleting Neighbours per Cell

Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of the Transmitter Properties dialogue. This section explains the following: "Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 536 "Allocating or Deleting Neighbours Using the Neighbours Table" on page 537 "Allocating or Deleting Neighbours on the Map" on page 538.

Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete UMTS neighbours using the Cells tab of the transmitters Properties dialogue: 1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cells Properties dialogue appears. 5. Click the Intra-technology Neighbours tab. 6. If desired, you can enter the maximum number of neighbours in the following boxes: Max Number Inter-Carrier Max Number Intra-Carrier

7. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." 8. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 9. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears.

536

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 11. Click OK.

Allocating or Deleting Neighbours Using the Neighbours Table

To allocate or delete UMTS neighbours using the Neighbours table: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. Note: For information on working with data tables, see "Working with Data Tables" on page 53.

4. To allocate a neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." 5. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 6. To make several neighbour relations symmetric: a. Click in the left margin of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. 7. To take into consideration all exceptionnal pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete some forced neighbours or some forbidden neighbours using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table, select the exceptional pairs, right-click the table and select Force Exceptional Pairs in the context menu. ), select a reference cell in the Cell column.

8. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 9. To delete several symmetric neighbour relations: a. Click in the left margin of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

537

Atoll User Manual 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour.

Allocating or Deleting Neighbours on the Map

You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 534. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters to the intra-technology neighbours list. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitters from the intra-technology neighbours. To add an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the intra-technology neighbour list of the reference transmitter. To remove an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the intra-technology neighbours list of the reference transmitter. To add an inward neighbour relation: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the intra-technology neighbours list of the reference transmitter. Notes: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

7.2.11.7

Calculating the Importance of Existing Neighbours

After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Select the Intra-carrier Neighbours tab. 5. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 529):

538

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference transmitters when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.

6. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the neighbour. Min. Ec/Io: Enter the minimum EcIo which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage. Ec/Io Margin: Enter the Ec/Io margin to define the area of coverage overlapping between UMTS cells. DL Load Contributing to Io: Under DL Load Contributing to Io, select whether you want Atoll to base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

7. Click OK to save your modifications and close the Coverage Conditions dialogue. 8. Select the Inter-carrier Neighbours tab. 9. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 529): 10. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the neighbour. Min. Ec/Io: Enter the minimum EcIo which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage. Ec/Io Margin: Enter the Ec/Io margin to define the area of coverage overlapping between UMTS cells. DL Load Contributing to Io: Under DL Load Contributing to Io, select whether you want Atoll to base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

11. Click OK to save your modifications and close the Coverage Conditions dialogue. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. Notes: You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

12. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table on each tab. The table contains the following information: Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 5. Cause: The reason Atoll has calculated the value in the Importance column. Co-site Adjacency Symmetry Coverage

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

539

Atoll User Manual Coverage: The amount of reference transmitters coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neighbour transmitter is best server or second best server. This information is not relevant for inter-carrier neighbours and is therefore not present on the Inter-carrier Neighbours tab. Distance: The distance in kilometres between the reference cell and the neighbour.

The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

7.2.11.8

Checking the Consistency of the Neighbour Plan

You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Intra-technology Neighbours tab. 5. Define the parameters of the audit: Neighbourhood Type: Select whether you want to perform an audit on Intra-Carrier or Inter-Carrier neighbour relations. Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Which cells having the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Lists > Max Number: Which cells having more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours > check box and enter the distance between neighbours that must not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax: |CELL|

Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax: Note: |CELL| |NUMBER| |MAX NUMBER| If the field Maximum number of intra-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.

540

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

7.2.11.9

Exporting Neighbours
The neighbour data of an Atoll document is stored in a series of tables. You can export the neighbour data to use it in another application or in another Atoll document. To export neighbour data: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours and then select the neighbour table containing the data you want to export from the context menu: Intra-Technology Neighbours: This table contains the data for the intra-technology (intra-carrier and intercarrier) neighbours in the current Atoll document. Inter-Technology Neighbours: This table contains the data for the inter-technology neighbours in the current Atoll document. Intra-technology Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document. Inter-technology Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs (forced and forbidden) in the current Atoll document.

4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files" on page 61.

7.2.12

Planning Scrambling Codes

In UMTS, 512 scrambling codes are available, numbered from 0 to 511. Although UMTS scrambling codes are displayed in decimal format by default, they can also be displayed and calculated in hexadecimal format, in other words using the numbers 0 to 9 and the letters A to F. Atoll facilitates the management of scrambling codes by letting you create groups of scrambling codes and domains, where each domain is a defined set of groups. You can also assign scrambling codes manually or automatically to any cell in the network. Once allocation is completed, you can audit the scrambling codes, view scrambling code reuse on the map, and make an analysis of scrambling code distribution. The procedure for planning scrambling codes for a UMTS project is: Preparing for scrambling code allocation "Defining the Scrambling Code Format" on page 542 "Creating Scrambling Code Domains and Groups" on page 542 "Defining Exceptional Pairs for Scrambling Code Allocation" on page 542. "Automatically Allocating Scrambling Codes to UMTS Cells" on page 543 "Allocating Scrambling Codes to UMTS Cells Manually" on page 545.

Allocating scrambling codes

"Checking the Consistency of the Scrambling Code Plan" on page 545. Displaying the allocation of scrambling codes "Using the Search Tool to Display Scrambling Code Allocation" on page 546 "Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 546 "Grouping Transmitters by Scrambling Code" on page 547 "Displaying the Scrambling Code Allocation Histogram" on page 547 "Making a Scrambling Code Interference Zone Prediction" on page 548. "Making a Scrambling Code Interference Analysis" on page 548 Notes Within the context of primary scrambling code allocation, "neighbours" refer to intra-carrier neighbours. According to 3GPP specifications, the 512 possible scrambling codes can be broken down into groups, each containing 8 codes. Because the term "group" in Atoll refers to user-defined sets of scrambling codes, these groups of 8 codes each are referred to as "clusters" in Atoll. As well, Atoll allows you to change the number of codes in a cluster.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

541

Atoll User Manual

7.2.12.1

Defining the Scrambling Code Format

Scrambling codes may be displayed in decimal or hexadecimal format. The selected format is used to display scrambling codes in dialogues and tables such as in the Domains and Groups tables, the Cells table, and the Scrambling Code Allocation dialogue. The decimal format is the default format in Atoll. The accepted decimal values are from 0 to 511. The decimal format is also used, even if you have chosen the hexadecimal format, to store scrambling codes in the database and to display scrambling code distribution or the results of a scrambling code audit. The hexadecimal format uses the numbers 0 to 9 and the letters A to F for its base characters. In Atoll, hexadecimal values are indicated by a lower-case "h" following the value. For example, the hexadecimal value "3Fh" is "63" as a decimal value. You can convert a hexadecimal value to a decimal value with the following equation, where A, B, and C are decimal values within the hexadecimal index ranges: A 16 + B 16 + C For example, the hexadecimal value "3Fh" would be calculated as shown below: 0 16 + 3 16 + 15 = 63 To define the scrambling code format for an Atoll document: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Primary Scrambling Codes > Format from the context menu and select either Decimal or Hexadecimal.
2 2

7.2.12.2

Creating Scrambling Code Domains and Groups

Atoll facilitates the management of scrambling codes by letting you create domains, each containing groups of scrambling codes. The procedure for managing scrambling codes in a UMTS document consists of the following steps: 1. Creating a scrambling code domain, as explained in this section. 2. Creating groups, each containing a range of scrambling codes, and assigning them to a domain, as explained in this section. 3. Assigning a scrambling code domain to a cell or cells. If there is no scrambling code domain, Atoll will consider all 512 possible scrambling codes when assigning codes. To create a scrambling code domain: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Primary Scrambling Codes > Domains. The Domains table appears. 4. In the row marked with the New Row icon ( ), enter a Name for the new domain.

5. Click in another cell of the table to create the new domain and add a new blank row to the table. 6. Double-click the domain to which you want to add a group. The domains Properties dialogue appears. 7. Under Groups, enter the following information for each group you want to create. Name: Enter a name for the new scrambling code group. Min.: Enter the lowest available primary scrambling code in this groups range. The minimum and maximum scrambling codes must be entered in the format, decimal or hexadecimal, set for the Atoll document (for information on setting the scrambling code format, see "Defining the Scrambling Code Format" on page 542). Max: Enter the highest available primary scrambling code in this groups range. Step: Enter the separation interval between each primary scrambling code. Excluded: Enter the scrambling codes in this range that you do not want to use. Extra: Enter any additional scrambling codes (i.e., outside the range defined by the Min. and Max fields) you want to add to this group. You can enter a list of codes separated by either a comma, semi-colon, or a space. You can also enter a range of scrambling codes separated by a hyphen. For example, entering, "1, 2, 3-5" means that the extra scrambling codes are "1, 2, 3, 4, 5."

8. Click in another cell of the table to create the new group and add a new blank row to the table.

7.2.12.3

Defining Exceptional Pairs for Scrambling Code Allocation

You can also define pairs of cells which cannot have the same primary scrambling code. These pairs are referred to as exceptional pairs. Exceptional pairs are used along with other constraints, such as neighbours, reuse distance, and domains, in allocating scrambling codes. To create a pair of cells that cannot have the same scrambling code: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears.

542

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 3. Select Cells > Primary Scrambling Codes > Exceptional Pairs. The Exceptional Separation Constraints table appears. For information on working with data tables, see "Working with Data Tables" on page 53. 4. 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. 5. Click in another cell of the table to create the new exceptional pair and add a new blank row to the table.

7.2.12.4

Allocating Scrambling Codes

Atoll can automatically assign scrambling codes to the cells of a UMTS network according to set parameters. For example, it takes into account the definition of groups and domains of scrambling codes, the selected scrambling code allocation strategy (clustered, distributed per cell, distributed per site and one cluster per site), minimum code reuse distance, and any constraints imposed by neighbours. You can also allocate scrambling codes manually to the cells of a UMTS network. In this section, the following methods of allocating scrambling codes are described: "Defining Automatic Allocation Constraint Violation Costs" on page 543 "Automatically Allocating Scrambling Codes to UMTS Cells" on page 543 "Allocating Scrambling Codes to UMTS Cells Manually" on page 545.

Defining Automatic Allocation Constraint Violation Costs

You can define the costs of the different types of constraints used in the automatic scrambling code allocation algorithm. To define the different constraint violation costs: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Primary Scrambling Codes > Constraint Costs. The Constraint Violation Costs dialogue appears. In this dialogue you can define the following costs of constraint violations for the automatic allocation process (the cost is a value from 0 and 1): Under Intra-technology Neighbours, you can set the constraint violation costs 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.

Automatically Allocating Scrambling Codes to UMTS Cells

The allocation algorithm enables you to automatically allocate primary scrambling codes to cells in the current network. You can choose among several automatic allocation strategies. The actual automatic allocation strategies available will depend on your network and options selected in the atoll.ini file. For more information on the atoll.ini file, see the Administrator Manual. For more information on automatic allocation strategies, see the Technical Reference Guide. Clustered: The purpose of this strategy is to choose for a group of mutually constrained cells, scrambling codes among a minimum number of clusters. In this case, Atoll will preferentially allocate all the codes from same cluster. Distributed per Cell Allocation: This strategy consists in using as many clusters as possible. Atoll will preferentially allocate codes from different clusters. One Cluster per Site: This strategy allocates one cluster to each base station, then, one code of the cluster to each cell of each base station. When all the clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the clusters at another base station. Distributed per Site: This strategy allocates a group of adjacent clusters to each base station in the network, then, one cluster to each transmitter of the base station according to its azimuth and finally one code of the cluster to each cell of each transmitter. The number of adjacent clusters per group depends on the number of transmitters per base station you have in your network; this information is required to start allocation based on this strategy. When all the groups of adjacent clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the groups of adjacent clusters at another base station.

To automatically allocate primary scrambling codes: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Primary Scrambling Codes > Automatic Allocation. The Primary Scrambling Codes dialogue appears. Under Constraints, you can set the constraints on automatic scrambling code allocation. Existing Neighbours: Select the Existing Neighbours check box if you want to consider intra-carrier neighbour relations and then choose the neighbourhood level to take into account: Neighbours of a cell are referred to as the first order neighbours, neighbours neighbours are referred to as the second order neighbours and neighbours neighbours neighbours as the third order neighbours.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

543

Atoll User Manual 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 528. Note: 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 650 Additional Overlapping Conditions: Select the Additional Overlapping Conditions check box, if you want to set overlapping coverage criteria. If cells meet the overlapping conditions to enter the reference cells active set, they will be not allocated the same scrambling code as the reference cell. Click Define to change the overlapping conditions. In the Coverage Conditions dialogue, you can change the following parameters: Min. 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. Reuse Distance: Select the Reuse Distance check box, if you want to the automatic allocation process to consider the reuse distance constraint. Enter the Default reuse distance within which two cells on the same carrier cannot have the same primary scrambling code. A reuse distance can be defined at the cell level (in the cell Properties dialogue or in the Cells table). If defined, a cell-specific reuse distance will be used instead of the value entered here. 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

Note:

From the Strategy list, you can select an automatic allocation strategy: -

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 wish, you can change the number of codes per cluster. When the allocation is based on a Distributed strategy (Distributed per Cell or Distributed per Site), this parameter can also be used to define the interval between the primary scrambling codes assigned to cells on a same site. The defined interval is applied by setting an option in the atoll.ini file. For more information about setting options in the atoll.ini file, see the Administrator Manual.

Use a Max of Codes: Select the Use a Max of Codes check box to make Atoll use the maximum number of codes. For example, if there are two cells using the same domain with two scrambling codes, Atoll will assign the remaining code to the second cell even if there are no constraints between these two cells (for example, neighbour relations, reuse distance, etc.). If you do not select this option, Atoll only checks the constraints, and allocates the first ranked code in the list. Delete Existing Codes: Select the Delete Existing Codes check box if you want Atoll to delete currently allocated scrambling codes and recalculate all scrambling codes. If you do not select this option, Atoll will Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

544

Chapter 7: UMTS HSPA Networks keep currently allocated scrambling codes and will only allocate scrambling codes to cells that do not yet have codes allocated. Allocate Carriers Identically: Select the Allocate Carriers Identically check box if you want Atoll to allocate the same primary scrambling code to each carrier of a transmitter. If you do not select this option, Atoll allocates scrambling codes independently for each carrier.

4. Click Run. Atoll begins the process of allocating scrambling codes. Once Atoll has finished allocating scrambling codes, the codes are visible under Results. Atoll only displays newly allocated scrambling codes. The Results table contains the following information. Site: The name of the base station. Cell: The name of the cell. Code: The primary scrambling code allocated to the cell.

5. Click Commit. The primary scrambling codes are committed to the cells. Note: 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 "Exporting a User Configuration" on page 79.

Tips:

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 Cells > Primary Scrambling Codes > Automatic Allocation from the transmitter groups context menu.

Allocating Scrambling Codes to UMTS Cells Manually

When you allocate scrambling codes to a large number of cells, it is easiest to let Atoll allocate scrambling codes automatically, as described in "Automatically Allocating Scrambling Codes to UMTS Cells" on page 543. However, if you want to add a primary scrambling code to one cell or to modify the primary scrambling code of a cell, you can do it by accessing the properties of the cell. To allocate a scrambling code to a UMTS cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a scrambling code. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Select the Cells tab. 4. Enter a Primary Scrambling Code in the cells column. 5. Click OK.

7.2.12.5

Checking the Consistency of the Scrambling Code Plan

Once you have completed allocating scrambling codes, you can verify whether the allocated scrambling codes respect the specified constraints by performing an audit of the plan. The scrambling code audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Primary Scrambling Codes > Audit. The Code and Cluster Audit dialogue appears. 4. In the Code and Cluster Audit dialogue, select the allocation criteria that you want to check: No. of Codes per Cluster: Enter the number of scrambling codes per cluster. Neighbours: Select Neighbours 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 Neighbours: Atoll will check that no cell has the same scrambling code as any of its neighbours or any of the neighbours of its neighbours. Third Order Neighbours: Atoll will check that no cell has the same scrambling code as any of its neighbours or any of the neighbours of its neighbours or any of the neighbours of its second order neighbours. The report will list the cells and the neighbours that do not meet one of these constraints. In addition, it will indicate the allocated primary scrambling code and the neighbourhood level.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

545

Atoll User Manual Neighbours in Different Clusters: If you select the Neighbours in different clusters check box, Atoll will check that neighbour cells have scrambling codes from different clusters. The report will list any neighbour cells that does have scrambling codes from the same cluster. Domain Compliance: If you select the Domain Compliance check box, Atoll will check if allocated scrambling codes belong to domains assigned to cells. The report will list any cells with scrambling codes that do not belong to domains assigned to the cell. Site Domains Not Empty: If you select the Site Domains Not Empty check box, Atoll will check for and list base stations for which the allocation domain (i.e., the list of possible scrambling codes) is not consistent with the "One cluster per site" strategy. If there is a base station with N cells, Atoll will check that the domains assigned to the cells contain at least one cluster consisted of N codes. If you plan to automatically allocate scrambling codes using the "One Cluster per Site" strategy, you can perform this test beforehand to check the consistency of domains assigned to cells of each base station. One Cluster per Site: If you select the One Cluster per Site check box, Atoll will check for and list base stations whose cells have scrambling codes coming from more than one cluster. Distance: If you select the Distance check box and set a reuse distance, Atoll will check for and list the cell pairs that do not respect the reuse distance condition. For any cell pair, Atoll uses the lowest of the reuse distance values among the ones defined for the two cells in their properties and the value that you set in the Code and Cluster Audit dialogue. Cell pairs that do not respect the reuse distance condition are listed in increasing order of the distance between them. The primary scrambling code and the reuse distance are also listed for each cell pair. Exceptional Pairs: If you select the Exceptional Pairs check box, Atoll will check for and display pairs of cells that are listed as exceptional pairs but still use the same scrambling code.

5. Click OK. Atoll displays the results of the audit in a text file called CodeCheck.txt, which it opens at the end of the audit. For each selected criterion, Atoll gives the number of detected inconsistencies and details each of them.

7.2.12.6

Displaying the Allocation of Scrambling Codes

Once you have completed allocating scrambling codes, you can verify several aspects of scrambling code allocation. You have several options for displaying scrambling codes: "Using the Search Tool to Display Scrambling Code Allocation" on page 546 "Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 546 "Grouping Transmitters by Scrambling Code" on page 547 "Displaying the Scrambling Code Allocation Histogram" on page 547 "Making a Scrambling Code Interference Zone Prediction" on page 548. "Making a Scrambling Code Interference Analysis" on page 548

Using the Search Tool to Display Scrambling Code Allocation

In Atoll, you can search for scrambling codes and scrambling code groups using the Search Tool. Results are displayed in the map window in red. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Scrambling codes and scrambling code groups and any potential problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 499. To find scrambling codes or scrambling code groups using the Search Tool: 1. Create, calculate, and display a coverage prediction by transmitter. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 499. 2. Click View > Search Tool. The Search Tool window appears. The Search Tool window is a docking window. For information on docking windows, see "Docking or Floating an Atoll Window" on page 26. 3. You can search either for a specific scrambling code or scrambling code group: To search for a scrambling code: a. Select Scrambling Code. b. Enter a scrambling code in the text box. To search for a scrambling code group: a. Select SC Group. b. Select a scrambling code group from the list. 4. Select the carrier you wish to search on from the For the Carrier list, or select "(All)" to search for the scrambling code or scrambling code group in all carriers. 5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match the search criteria are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.

Displaying Scrambling Code Allocation Using Transmitter Display Settings

You can use the display characteristics of transmitters to display scrambling code-related information.

546

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks To display scrambling code-related information on the map: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. You can display the following information per transmitter: Primary scrambling code: To display the primary scrambling code of a transmitters cell, select "Discrete values" as the Display Type and "Cells: Primary Scrambling Code" as the Field. Ranges of primary scrambling codes: To display ranges of primary scrambling codes, select "Value intervals" as the Display Type and "Cells: Primary Scrambling Code" as the Field. Scrambling code domain: To display the scrambling code domain of a transmitters cell, select "Discrete values" as the Display Type and "Cells: Scrambling Code Domain" as the Field.

You can display the following information in the transmitter label or tooltip: Primary scrambling code: To display the primary scrambling code of a transmitters cell in the transmitter label or tooltip, "Cells: Primary Scrambling Code" from the Label or Tip Text Field Definition dialogue. Scrambling code domain: To display the primary scrambling code domain of a transmitters cell in the transmitter label or tooltip, "Cells: Scrambling Code Domain" from the Label or Tip Text Field Definition dialogue. Scrambling code reuse distance: To display the scrambling code reuse distance of a transmitters cell in the transmitter label or tooltip, "Cells: SC Reuse Distance" from the Label or Tip Text Field Definition dialogue.

5. Click OK. For information on display options, see "Display Properties of Objects" on page 32.

Grouping Transmitters by Scrambling Code

You can group transmitters on the Data tab of the Explorer window by their primary scrambling code, their scrambling code domain, or by their scrambling code reuse distance. To group transmitters by scrambling code: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: Scrambling Code Domain Primary Scrambling Code SC Reuse Distance

7. Click to add the parameter to the Group these fields in this order 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 Group these fields in this order list and click will be grouped. . The selected parameter is removed from the list of parameters on which the transmitters

9. 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 b. Select a parameter and click to move it up to the desired position. to move it down to the desired position.

10. Click OK to save your changes and close the Group dialogue. Note: 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 scrambling code clusters as a function of the frequency of their use. To display the scrambling code histogram: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

547

Atoll User Manual 3. Select Cells > Primary Scrambling Codes > Scrambling Code Distribution. The Distribution Histograms dialogue appears. Each bar represents a scrambling code or a cluster, its height depending on the frequency of its use. 4. Select Scrambling Codes to display scrambling code use and Clusters to display scrambling code cluster use. 5. Move the pointer over the histogram to display the frequency of use of each scrambling code or cluster. The results are highlighted simultaneously in the Detailed Results list.

Making a Scrambling Code Interference Zone Prediction

You can make a scrambling code interference zone prediction to view areas covered by cells using the same scrambling code. Atoll checks on each pixel whether the best server and other servers satisfying the conditions to enter the user active set have the same scrambling code. If so, Atoll considers that there is scrambling code interference. To make a scrambling code interference zone prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Scrambling Zone Interference Zones and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 510. You must also select which Carrier is to be considered. If you want the scrambling code interference 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. 7. Click the Display tab. For a scrambling code interference zone prediction, the Display Type "Discrete Values" based on the Field "Transmitter" is selected by default. Each pixel where there is scrambling code interference is displayed with the same colour as that defined for the interfered transmitter. In the Explorer window, the coverage prediction results are first arranged by interfered transmitter and then by interferer. For information on defining display properties, see "Display Properties of Objects" on page 32. 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.

8. Click the Calculate button ( ) in the Radio toolbar to calculate the scrambling code interference zone prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Making a Scrambling Code Interference Analysis

The SC Interference tab of the Point Analysis window gives you information on reception for any point on the map where there is scrambling code interference. Scrambling code interference occurs when the best server and other servers satisfying the conditions to enter the user active set have the same scrambling code. When there is scrambling code interference, Atoll displays the pilot quality (EcI0) received from interfered and interferer transmitters. The analysis is based on the UL load percentage and the DL total power of each cell. The analysis is provided for a userdefinable probe receiver which has a terminal, a mobility, and a service.

548

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks You can make a scrambling code interference analysis to verify a scrambling code interference zone prediction. In this case, before you make the scrambling code interference analysis, ensure the coverage prediction you want to use in the scrambling code interference analysis is displayed on the map. To make a scrambling code interference analysis: 1. Click the Point Analysis button ( 2. Click the SC Interference tab. 3. At the top of the SC Interference tab, select "Cells Table" from Load Conditions. 4. If you are making a scrambling code interference analysis to verify a coverage prediction, you can recreate the conditions of the coverage prediction: a. Select the same Terminal, Service, and Mobility studied in the coverage prediction. b. Select the Carrier studied in the coverage prediction. c. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. 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. ) on the toolbar. The Point Analysis Tool window appears.

d. Click OK to close the Properties dialogue. Note: If you are making a scrambling code interference 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 interference 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 ( ) on the toolbar again to end the point analysis.

7.3

Studying Network Capacity

A UMTS network automatically regulates power on both uplink and downlink with the objective of minimising interference and maximising network capacity. In the case of HSDPA, the network uses A-DCH power control in the uplink and downlink and a fast link adaptation (in other words, the selection of an HSDPA bearer) in the downlink. Atoll can simulate these network regulation mechanisms, thereby enabling you to study the capacity of the UMTS network. In Atoll, a simulation is based on a realistic distribution of R99 and HSDPA users at a given point in time. The distribution of users at a given moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters such as the active set for each mobile, the required power of the mobile, the total DL power and DL throughput per cell, and the UL load per cell. Simulations are calculated in an iterative fashion. When several simulations are performed at the same time using the same traffic information, the distribution of users will be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to another. 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: "Defining Multi-service Traffic Data" on page 549 "Creating a Traffic Map" on page 550 "Calculating and Displaying Traffic Simulations" on page 559 "Analysing the Results of a Simulation" on page 578.

7.3.1

Defining Multi-service Traffic Data

The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: R99 radio bearers: Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists all the available radio bearers. You can create new R99 radio bearers and modify existing ones by using the R99 Radio Bearer table. For information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 654.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

549

Atoll User Manual 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 511. 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 "Creating a Mobility Type" on page 513. 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 513.

7.3.2

Creating a Traffic Map

The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atoll provides three types of traffic maps for UMTS projects. Sector traffic map User profile traffic map User density traffic map (number of users per km2)

These maps can be created using different types of traffic data sources as follows: Sector traffic maps can be used if you have live traffic data from the OMC (Operation and Maintenance Centre). The OMC (Operations and Maintenance Centre) collects data from all cells in a network. This includes, for example, the number of users or the throughput in each cell and the traffic characteristics related to different services. Traffic is spread over the best server coverage area of each transmitter and each coverage area is assigned either the throughputs in the uplink and in the downlink or the number of users per activity status or the total number of users (including all activity statuses). For more information, see "Creating a Sector Traffic Map" on page 550. User profile traffic maps can be used if you have marketing-based traffic data. User profile traffic maps, where each vector (polygon, line, or point) describes subscriber densities (or numbers of subscribers for points) with user profiles and mobility types, and user profile environment based traffic maps, where each pixel has an assigned environment class. For more information, see "Importing a User Profile Traffic Map" on page 553, "Importing a User Profile Environment Based Traffic Map" on page 554, and "Creating a User Profile Environment Based Traffic Map" on page 555. User density traffic maps (number of users per km2) can be used if you have population-based traffic data, or 2G network statistics. Each pixel has a user density assigned. The value either includes all activity statuses, or it corresponds to a particular activity status. For more information, see "Importing a User Density Traffic Map" on page 556, "Creating a User Density Traffic Map" on page 557, "Converting 2G Network Traffic" on page 558 and "Exporting Cumulated Traffic" on page 558.

7.3.2.1

Creating a Sector Traffic Map

This section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the uplink and in the downlink, the number of users per activity status, or the total number of users including all activity statuses. A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 499. To create a sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector Traffic Map. 5. Select the type of traffic information you want to input. You can choose between Throughputs in Uplink and Downlink, Total Number of Users (All Activity Statuses) or Number of Users per Activity Status. 6. Click the Create button. The Sector Traffic Map dialogue appears. Note: You can also import a traffic map from a file by clicking the Import button. You can import AGD (Atoll Geographic Data) format files that you have exported from an other Atoll document.

7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 8. Enter the data required in the Map per Sector dialogue: If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and downlink for each sector and for each listed service.

550

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks If you have selected Total Number of Users (All Activity Statuses), enter the number of connected users for each sector and for each listed service. If you have selected Number of Users per Activity Status, enter the number of inactive users, the number of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each service. Note: You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 63.

9. Click OK. The Sector Traffic Map Properties dialogue appears. 10. Select the Traffic tab. 11. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 12. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 13. Under Clutter Distribution, for each clutter class, enter: A weight to spread the traffic over the vector. The percentage of indoor users. An additional loss will be counted for indoor users during Monte-Carlo simulations.

14. Click OK. Atoll creates the traffic map in the Traffic folder. You can modify the sector traffic map after it has been created. To modify the sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 5. Select the Traffic tab. 6. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 7. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 8. Under Clutter Distribution, for each clutter class, enter a weight to spread the traffic over the clutter classes and the percentage of indoor users. 9. Click OK. Atoll saves the traffic map with its modifed values. You can update the information, throughput demands and the number of users, on the map afterwards. You can update sector traffic maps if you add or remove a base station. You must first recalculate the coverage prediction by transmitter. For more information, see "Making a Coverage Prediction by Transmitter" on page 499. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map that you want to update. The context menu appears. 4. Select Update from the context menu. The Sector Traffic Map dialogue appears. 5. Select the updated coverage prediction by transmitter and define traffic values for the new transmitter(s) listed at the bottom of the table. Deleted or deactivated transmitters are automatically removed from the table. 6. Click OK. The Sector Traffic Map Properties dialogue appears. If desired you can update the values under Terminals (%), Mobilities (%), and Clutter Distribution. 7. Click OK. The traffic map is updated on the basis of the selected coverage prediction by transmitter. If you wish 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 557.

7.3.2.2

Creating a User Profile Traffic Map

The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There might also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create user profile traffic maps.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

551

Atoll User Manual A user profile models the behaviour of different subscriber categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for circuit-switched calls) or uplink and downlink volume (for packet-switched calls). Environment classes are used to describe the distribution of subscribers on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km). The sections "Importing a User Profile Traffic Map" on page 553, "Importing a User Profile Environment Based Traffic Map" on page 554 and "Creating a User Profile Environment Based Traffic Map" on page 555 describe how to use traffic data from the marketing department in Atoll to model traffic. In this section, the following are explained: "Modelling User Profiles" on page 552 "Modelling Environments" on page 552.

Modelling User Profiles

You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user may be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. Note: 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.

5. You can modify the following parameters: Service: Select a service from the list. For information on services, see "Modelling Services" on page 511. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 513. Calls/Hour: For circuit-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 circuit-switched services, one call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each. For packet-switched services, the Calls/Hour value is defined as the number of sessions per hour. A session is like a call in that it is defined as the period of time between when a user starts using a service and when he stops using a service. In packet-switched services, however, he may not use the service continually. For example, with a 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 may be downloading web pages and other times he may not be using the application, or he may be browsing local files, but the session is still considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time. Note: In order for all the services defined for a user profile to be taken into account during traffic scenario elaboration, the sum of activity probabilities must be lower than 1.

Duration: For circuit-switched services, enter the average duration of a call in seconds. For packet-switched services, this field is left blank. UL Volume: For packet-switched services, enter the average uplink volume per session in kilobytes. DL Volume: For packet-switched services, enter the average downlink volume per session in kilobytes.

Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers for each clutter class. In a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss. To create or modify a UMTS environment: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Environments folder. The context menu appears. 4. Select New from the context menu. The Environments New Element Properties dialogue appears.

552

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Note:

You can modify the properties of an existing environment by right-clicking the environment in the Environments folder and selecting Properties from the context menu.

5. Click the General tab. 6. Enter a Name for the new UMTS environment. 7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility combination that this UMTS environment will describe: User: Select a user profile. Mobility: Select a mobility type. Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination of user profile and mobility type.

8. Click the Clutter Weighting tab. 9. For each clutter class, enter a weight that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

For example: An area of 10 km with a subscriber density of 100/km. Therefore, in this area, there are 1000 subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in the Building clutter class. 10. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss.

7.3.2.2.1

Importing a User Profile Traffic Map

User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscriberskm, or polygons with a number of subscriberskm) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Densities from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Density Traffic Map" on page 557.

7. Select the file to import. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab (see Figure 7.304). Under Traffic Fields, you can specify the user profiles to be considered, their mobility type (kmh), and their density. If the file you are importing has this data, you can define the traffic characteristics by identifying the corresponding fields in the file. If the file you are importing does not have data describing the user profile, mobility, or density, you can assign values. When you assign values, they apply to the entire map.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

553

Atoll User Manual

Figure 7.304: Traffic map properties dialogue - Traffic tab Define each of the following: User Profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the UMTS Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the UMTS Parameters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points. Important: 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 UMTS Parameters folder of the Data tab. If the imported user profile or mobility does not match, Atoll will display a warning. 12. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

13. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss. 14. Click OK to finish importing the traffic map.

7.3.2.2.2

Importing a User Profile Environment Based Traffic Map

Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map.

554

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 5. Select User Profile Environments from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 555.

7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, JPEG 2000, BIL, IST, BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Description tab. In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the Code column. 12. For each Code, select the environment it corresponds to from the Name column. The environments available are those available in the Environments folder, under UMTS Parameters on the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 552. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 32.

7.3.2.2.3

Creating a User Profile Environment Based Traffic Map

Atoll enables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 7.305).

Draw Map

Delete Map

Figure 7.305: Environment Map Editor toolbar 7. Select the environment class from the list of available environment classes. 8. Click the Draw Polygon button ( 9. Click the Delete Polygon button ( ) to draw the polygon on the map for the selected environment class. ) and click the polygon to delete the environment class polygon on the map.

10. Click the Close button to close the Environment Map Editor toolbar and end editing.

7.3.2.2.4

Displaying Statistics on a User Profile Environment Traffic Map

You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears. The Statistics window lists the surface (Si in km) and the percentage of surface (% of i) for each environment Si class "i" within the focus zone. The percentage of surface is given by: % of i = ------------- 100 Sk

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

555

Atoll User Manual You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.

7.3.2.3

Creating User Density Traffic Maps (No. Users/km2)

User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit of surface, i.e., the density of users, as input. This can be either the density of users per activity status or the density of users including all activity statuses. In this section, the following ways of creating a user density traffic map are explained: "Importing a User Density Traffic Map" on page 556 "Creating a User Density Traffic Map" on page 557.

User density traffic maps may be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. for more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 557.

7.3.2.3.1

Importing a User Density Traffic Map

The user density traffic map defines the density of users per pixel. For a traffic density of X users per km, Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined on the Traffic tab of the traffic maps properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (No. Users/km2). 5. Select the type of traffic information you input: All Activity Statuses: Select All Activity Statuses if the map you are importing provides a density of users with any activity status. Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.

6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Density Traffic Map" on page 557.

7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP, PlaNET, TIF, JPEG 2000, ISTAR, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab. 12. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 13. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 14. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal 100. 15. Under Clutter Distribution, enter the percentage of indoor users for each clutter class. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for user density traffic maps because the traffic is provided in terms of user density per pixel.

556

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 16. Click OK. Atoll creates the traffic map in the Traffic folder.

7.3.2.3.2

Creating a User Density Traffic Map

Atollenables you to create a user density traffic map by drawing it in the map window. To draw a user density traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (Number of users per km2). 5. Select the type of traffic information you input: All Activity Statuses: Select All Activity Statuses if the map you are drawing provides a density of users with any activity status. Active in Uplink: Select Active in Uplink if the map you are drawing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are drawing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are drawing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are drawing provides a density of inactive users.

6. Click the Create button. The traffic maps properties dialogue appears. 7. Select the Traffic tab. 8. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 9. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 10. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal 100. 11. Under Clutter Distribution, enter the percentage of indoor users for each clutter class. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for user density traffic maps because the traffic is provided in terms of user density per pixel. 12. Click OK. Atoll creates the traffic map in the Traffic folder. 13. Right-click the traffic map. The context menu appears. 14. Select Edit from the context menu. 15. Use the tools available in the Vector Edition toolbar to draw contours. For more information on editing contours, see "Editing Polygons, Lines, and Points" on page 46. Atoll creates an item called Density values in the User Density Map folder. 16. Right-click the Density values item in the User Density Map folder. The context menu appears. 17. Select Open Table from the context menu. 18. In the table, enter a traffic density value (i.e., the number of users per km2) for each contour you have drawn. 19. Right-click the item. The context menu appears. 20. Select Edit from the context menu to end editing.

7.3.2.3.3

Creating User Density Traffic Maps from Sector Traffic Maps

You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps 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. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map from which you want to create user density traffic maps. The context menu appears. 4. Select Create density maps from the context menu. Atoll creates as many user density traffic maps as the number of services present in the sector traffic map. The user density map files use the resolution of the coverage prediction used for the sector traffic map and are embedded in the document.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

557

Atoll User Manual

7.3.2.4

Converting 2G Network Traffic

Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as user density traffic maps into your UMTS document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 558, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 556. To import a 2G traffic map into a UMTS document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 254. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 558. 3. Import the traffic exported in step 2 in your UMTS document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 556.

7.3.2.5

Exporting Cumulated Traffic

Atollallows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: The Entire Project Area: This option allows you to export the cumulated traffic over the entire project. The Computation Zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible.

7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains at "0" and no data will be exported. 8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic data to be exported. Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal. Service: Select the service that will be exported, or select "All circuit services" to export traffic using any circuit service, or select "All 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 All Activity Statuses to export all users without any filter by activity status. Uplink: Select Uplink to export mobiles active in the uplink only. Downlink: Select Downlink to export mobiles active in the downlink only. Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity. Inactive: Select Inactive to export only inactive mobiles.

9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the cumulated traffic. 10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.

7.3.3

Exporting a Traffic Map

To export a traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map.

558

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 6. Click Save. If you are exporting a raster traffic map, you have to define: The Export Region: Entire Project Area: Saves the entire traffic map. Only Pending Changes: Saves only the modifications made to the map. Computation Zone: Saves only the part of the traffic map inside the computation zone.

An export Resolution.

7.3.4

Calculating and Displaying Traffic Simulations

Once you have modelled the network services and users and have created traffic maps, you can create simulations. The simulation process consists of two steps: 1. Obtaining a realistic user distribution: Atoll generates a user distribution using a Monte-Carlo algorithm; this user distribution is based on the traffic database and traffic maps and is weighted by a Poisson distribution between simulations of the same group. Each user is assigned a service, a mobility type, and an activity status by random trial, according to a probability law that uses the traffic database. The user activity status is an important output of the random trial and has direct consequences on the next step of the simulation and on the network interferences. A user may be either active or inactive. Both active and inactive users consume radio resources and create interference. Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the shadowing effect. Finally, another random trial determines user positions in their respective traffic zone (possibly according to the clutter weighting and the indoor ratio per clutter class). 2. Modelling network power control: Atoll uses a power control algorithm for R99 users, and an algorithm mixing A-DPCH power control and fast link adaptation for HSDPA users and an additional loop modelling noise rise scheduling for HSUPA users. The power control simulation algorithm is described in "The Power Control Simulation Algorithm" on page 559.

7.3.4.1

The Power Control Simulation Algorithm

The power control algorithm (see Figure 7.306) simulates the way a UMTS network regulates itself by using uplink and downlink power controls in order to minimize interference and maximize capacity. HSDPA users (i.e., Packet (HSDPA), Packet (HSPA) and packet (HSPA - Constant Bit Rate) service users) are linked to the A-DPCH radio bearer (an R99 radio bearer). Therefore, the network uses a A-DPCH power control on UL and DL and then it performs fast link adaptation on DL in order to select an HSDPA radio bearer. For HSUPA users (i.e., Packet (HSPA) and packet (HSPA - Constant Bit Rate) service users), the network first uses a E-DPCCH/A-DPCH power control on UL and DL, checks that there is an HSDPA connection on downlink and then carries out noise rise scheduling in order to select an HSUPA radio bearer on uplink. Atoll simulates these network regulation mechanisms for each user distribution. During each iteration of the algorithm, all the mobiles (i.e., Circuit (R99), Packet (R99), Packet (HSDPA), Packet (HSPA) and packet (HSPA - Constant Bit Rate) service users) selected during the user distribution generation attempt to connect one by one to network transmitters. The process is repeated until the network is balanced, i.e., until the convergence criteria (on UL and DL) are satisfied.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

559

Atoll User Manual

Initialisation

R99 part

Mi Best Server Determination

Mi Active Set Determination

For HSDPA users, this part of the algorithm is performed for the A-DPCH bearer (R99 bearer) For HSUPA users, this part is performed for the E-DPCCH/ADPCH bearer (R99 bearer)

For each R99, HSDPA and HSUPA mobile, Mi

UL Power Control

DL Power Control

UL and DL Interference Update

Congestion and Radio Resource Control HSDPA part For each HSDPA and HSUPA mobile, Mi

Fast Link Adaptation

Mobile Scheduling

Radio Resource Control HSUPA part Admission Control For each HSUPA mobile, Mi Noise Rise Scheduling

Radio Resource Control

Convergence Study

Figure 7.306: Schematic view of simulation algorithm As shown in Figure 7.306, the simulation algorithm is divided in three parts. All users are evaluated by the R99 part of the algorithm. HSDPA and HSUPA bearer users, unless they have been rejected during the R99 part of the algorithm, are then evaluated by the HSDPA part of the algorithm. Finally, HSUPA bearer users, unless they have been rejected during the R99 or HSDPA parts of the algorithm, are then evaluated by the HSUPA part of the algorithm.

Description of the R99 Portion of the Simulation

The R99 part of the algorithm simulates power control, congestion and radio resource control performed for R99 bearers for all users. Atoll considers each user in the order established during the generation of the user distribution and determines his best server and his active set. Atoll first calculates the required terminal power in order to reach the EbNt threshold requested by the R99 bearer on UL, followed by the required traffic channel power in order to reach the EbNt threshold requested by the R99 bearer on DL. After calculating power control, Atoll updates the cell load parameters. Atoll then carries out congestion and radio resource control, verifying the cell UL load, the total power transmitted by the cell, the number of channel elements, the Iub throughput and OVSF codes consumed by the cell. At this point, users can be either connected or rejected. They are rejected if: The signal quality is not sufficient: On the downlink, the pilot quality is not high enough (no cell in the user active set): 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"

Even if constraints above are respected, the network may be saturated:

Description of the HSDPA Portion of the Simulation

In the HSDPA part, Atoll processes all HSDPA bearer users, i.e., packet (HSDPA), packet (HSPA) and packet (HSPA Constant Bit Rate) service users. The HSDPA part of the algorithm simulates fast link adaptation, the scheduling of HSDPA bearer users, and radio resource control on downlink. HSDPA bearer selection is based on look-up tables, available by double-clicking the corresponding entry in the Reception Equipment table, found in the Terminals context menu. HSDPA bearer selection depends on reported CQI, UE and cell capabilities as detailed in the following diagramme.

560

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

[ Figure 7.307: 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 (in the table Best Bearer=f(HS-PDSCH CQI) defined for the terminal reception equipment and the user mobility) and checks if it is compatible with the user equipment and cell capabilities. If compatible, Atoll selects the HSDPA bearer. Otherwise, it downgrades the HSDPA bearer to a lower one until the selected HSDPA bearer is compatible with the user equipment and cell capabilities. The selected HSDPA bearer is the best HSDPA bearer that the user can obtain. For packet (HSPA - Constant Bit Rate) service users, HS-SCCH-less operation (i.e., HS-DSCH transmissions without any accompanying HS-SCCH) is performed. In this case, the UE is not informed about the transmission format and has to revert to blind decoding of the transport format used on the HS-DSCH. Complexity of blind detections in the UE is decreased by limiting the transmission formats that can be used (i.e., the HSDPA bearers available). Therefore, only HSDPA bearers using the QPSK modulation and two HS-PDSCH channels at the maximum can be selected and allocated to the user. Additionally, the selected HSDPA bearer must provide a RLC peak rate higher than the guaranted bit rate defined for the service. Packet (HSPA - Constant Bit Rate) service users have the highest priority and are processed first, in the order established during the generation of the user distribution. The schedulermanages the maximum number of users within each cell and shares the cells available HSDPA power between the users. Atoll determines the HSDPA bearer for each user. The selected HSDPA bearer must provide a RLC peak rate higher than the guaranted bit rate defined for the service. To achieve the highest cell capacity, the scheduler can hold several packets over a TTI (Transmission Time Interval). Atollmodels this "intelligent scheduling" by allowing several packet (HSPA - Constant Bit Rate) service users to share the same HSDPA bearer. Then, Atoll calculates the HSDPA bearer consumption for each user and takes into account this parameter when it determines the resources consumed by the user (i.e., the HSDPA power used, the number of OVSF codes and the Iub backhaul throughput). Atoll checks to see 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, packet (HSPA - Constant Bit Rate) service users can be connected or rejected. They are rejected if: The maximum number of HSDPA users per cell is exceeded: the status is "HSDPA Scheduler Saturation" The lowest HSDPA bearer they can obtain does not provide a RLC peak rate higher than the guaranted bit rate: the status is "HSDPA Resource Saturation" The HS-SCCH signal quality is not sufficient: the status is "HSDPA Resource Saturation" There are no more OVSF codes available: the status is "HSDPA Resource Saturation" The maximum Iub backhaul throughput allowed on the site in the downlink is exceeded: the status is "HSDPA Resource Saturation"

After processing the packet (HSPA - Constant Bit Rate) service users, Atoll processes the remaining HSDPA bearer users (i.e., packet (HSDPA) and packet (HSPA) service users) without exceeding the maximum number of users within each cell. AtollThe scheduler ranks the users according to the selected scheduling technique: Max C/I: "n" users (where "n" corresponds to the maximum number of HSDPA users defined for the cell minus the number of packet (HSPA - Constant Bit Rate) service users in the cell) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by the channel quality indicator (CQI). Round Robin: Users are scheduled in the same order as in the simulation (i.e., in random order). Proportional Fair: "n" users (where "n" corresponds to the maximum number of HSDPA users defined for the cell minus the number of packet (HSPA - Constant Bit Rate) service users in the cell) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order according to a random parameter which corresponds to a combination of the user rank in the simulation and the channel quality indicator (CQI).

Then, users are processed in the order defined by the scheduler and the remaining cells HSDPA power ( i.e., the HSDPA power available after all packet (HSPA - Constant Bit Rate) service users have been served) is shared between them. Atoll checks to see if enough codes and Iub backhaul throughput are available for the HSDPA bearer assigned to the user (taking into account the maximum number of OVSF codes defined for the cell and the maximum Iub backhaul throughput allowed on the site in the downlink). If not, Atoll allocates a lower HSDPA bearer ("downgrading") which needs fewer OVSF codes and consumes lower Iub backhaul throughput. If no OVSF codes are available, the user is delayed. At the same time, if the maximum Iub backhaul throughput allowed on the site in the downlink is still exceeded even by using the lowest HSDPA bearer, the user is delayed.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

561

Atoll User Manual At this point, packet (HSDPA) and packet (HSPA) service users can be connected, rejected, or delayed. They are rejected if the maximum number of HSDPA users per cell is exceeded (status is "HSDPA Scheduler Saturation") and delayed if: They cannot obtain the lower HSDPA bearer: the status is "No Compatible Bearer" The HS-SCCH signal quality is not sufficient: the status is "HSDPA Power Saturation" There are no more HS-SCCH channels available: the status is "HS-SCCH Channels Saturation" There are no more OVSF codes available: the status is "OVSF Code Saturation" The maximum Iub backhaul throughput allowed on the site in the downlink is exceeded: the status is "Iub Throughput Saturation"

Description of the HSUPA Portion of the Simulation

In the HSUPA part, Atoll processes packet (HSPA) service users and packet (HSPA - Constant Bit Rate) service users who are connected to an HSDPA bearer or were delayed in the previous step. It manages the maximum number of users within each cell. Packet (HSPA - Constant Bit Rate) service users have the highest priority and are processed first, in the order established during the generation of the user distribution. Then, Atoll considers packet (HSPA) service users in the order established during the generation of the user distribution. The HSUPA part of the algorithm simulates an admission control on the HSUPA bearer users followed by noise rise scheduling and radio resource control. Atoll first selects a list of HSUPA bearers that are compatible with the user equipment capabilities for each HSUPA bearer user. For packet (HSPA - Constant Bit Rate) service users, the list is restricted to HSUPA bearers that provide a RLC peak rate higher than the guaranteed bit rate. Then, during admission control, Atoll checks that the lowest compatible bearer in terms of the required E-DPDCH EcNt does not require a terminal power higher than the maximum terminal power allowed. Then, Atoll performs the noise rise scheduling on packet (HSPA - Constant Bit Rate) service users, followed by a radio resource control. The noise rise scheduling algorithm attempts to evenly share the remaining cell load between the users admitted in admission control; in terms of HSUPA, each user is allocated a right to produce interference. The remaining cell load factor on uplink depends on the maximum load factor allowed on uplink and how much uplink load is produced by the served R99 traffic. From this value, Atoll calculates the maximum E-DPDCH EcNt allowed and can select an HSUPA bearer. The HSUPA bearer is selected based on the values in a look-up table, and depends on the maximum E-DPDCH EcNt allowed and on UE capabilities. Note: You can open the HSUPA Bearer Selection table by right-clicking Terminals on the Data tab of the Explorer window and selecting Reception Equipment. Then, if you double-click the entry in the Reception Equipment table, that entrys Properties dialogue opens, from which you can select the HSUPA Bearer Selection tab.

Atoll selects the best HSUPA bearer from the HSUPA compatible bearers, in other words, the HSUPA bearer with the highest potential throughput where the required E-DPDCH Ec/Nt is lower than the maximum E-DPDCH EcNt allowed and the required terminal power is lower than the maximum terminal power. In this section, the potential throughput refers to the ratio between the RLC peak rate and the number of retransmissions. When several HSUPA bearers are available, Atoll selects the one with the lowest required E-DPDCH EcNt. Several packet (HSPA - Constant Bit Rate) service users can share the same HSUPA bearer. Then, Atoll calculates the HSUPA bearer consumption for each user and takes into account this parameter when it determines the resources consumed by the user (i.e., the terminal power used, the number of channel elements and the Iub backhaul throughput). Finally, Atoll carries out radio resource control on packet (HSPA - Constant Bit Rate) service users. Atoll checks to see if enough channel elements and Iub backhaul throughput are available for the HSUPA bearer assigned to the user (taking into account the maximum number of channel elements defined for the site and the maximum Iub backhaul throughput allowed on the site in the uplink). If not, Atoll allocates a lower HSUPA bearer ("downgrading") which needs fewer channel elements and consumes lower Iub backhaul throughput. If no channel elements are available, the user is rejected. On the same hand, if the maximum Iub backhaul throughput allowed on the site in the uplink is still exceeded even by using the lowest HSUPA bearer, the user is rejected. At this point, packet (HSPA - Constant Bit Rate) service users can be either connected, or rejected. They are rejected if: The maximum number of HSUPA users per cell is exceeded (the status is "HSUPA Scheduler Saturation") The terminal power required to obtain the lowest compatible HSUPA bearer exceeds the maximum terminal power in the admission control (the status is "Pmob > PmobMax"). The lowest compatible HSUPA bearer they can obtain does not provide a RLC peak rate higher than the guaranted bit rate: the status is "HSUPA Admission Rejection". There are no more channel elements available: the status is "Ch. Elts Saturation" The maximum Iub backhaul throughput allowed on the site in the uplink is exceeded: the status is "Iub Throughput Saturation".

Then, Atoll processes packet (HSPA) service users. It performs a new noise rise scheduling and distributes the remaining cell load factor available after all packet (HSPA - Constant Bit Rate) service users have been served. From this value, Atoll selects an HSUPA bearer for each packet (HSPA) service user. Then, Atoll checks that each packet (HSPA) service user has obtained the average requested rate (defined in the properties of the service). Atoll Finally, Atoll carries out radio resource control, verifying if enough channel elements and Iub backhaul throughput are available for the HSUPA bearer assigned to the user (taking into account the maximum number of channel elements defined for the site and the maximum Iub backhaul throughput allowed on the site in the uplink). If not, Atoll allocates a lower HSUPA bearer ("downgrading") which needs fewer channel elements and consumes lower Iub backhaul throughput. If no channel elements are available, the user is rejected. On the same hand, if the maximum Iub backhaul throughput allowed on the site in the uplink is still exceeded even by using the lowest HSDPA bearer, the user is rejected.

562

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks At this point, packet (HSPA) service users can be either connected, or rejected. They are rejected if: The maximum number of HSUPA users per cell is exceeded (the status is "HSUPA Scheduler Saturation") The terminal power required to obtain the lowest compatible HSUPA bearer exceeds the maximum terminal power in the admission control (the status is "Pmob > PmobMax"). There are no more channel elements available: the status is "Ch. Elts Saturation" The maximum Iub backhaul throughput allowed on the site in the uplink is exceeded: the status is "Iub Throughput Saturation".

Bearer Downgrading
If you select the option "Bearer Downgrading," when creating a simulation, R99, HSDPA and HSUPA service users can be downgraded under certain circumstances. When the downgrading is allowed, Atoll does not reject R99, HSDPA and HSUPA users directly; it downgrades them beforehand. The R99 to R99 bearer downgrading occurs when: The cell resources are insufficient when the user is admitted The maximum uplink load factor is exceeded The maximum uplink load factor is exceeded There is not enough power for cells There are not enough channel elements on the site The maximum Iub backhaul throughput on the site is exceeded There are no more OVSF codes available On the downlink, the maximum traffic channel power is exceeded On the uplink, the maximum terminal power is exceeded The cell resources are insufficient during congestion control

The user maximum connection power is exceeded during power control:

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.

7.3.4.2

Creating Simulations
In Atoll, simulations enable you to model UMTS HSPA network regulation mechanisms in order to minimise interference and maximise capacity. You can create one simulation or a group of simulations that will be performed in sequence. To create a simulation or a group of simulations: 1. Click the Data tab in the Explorer window. 2. Right-click the UMTS Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name and Comments for this simulation or group of simulations. 5. Under Execution on the General tab, you can set the following parameters: Number of Simulations: Enter the number of simulations to be carried out. All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. Information to retain: You can select the level of detail that will be available in the output: Only the Average Simulation and Statistics: None of the individual simulations are displayed or available in the group. Only an average of all simulations and statistics is available. Some calculation and display options available for coverage predictions are not available when the option "Only the Average Simulation and Statistics" is selected. No Information About Mobiles: All the simulations are listed and can be displayed. For each of them, a properties window containing simulation output, divided among four tabs Statistics, Sites, Cells, and Initial conditions is available. Standard Information About Mobiles: All the simulations are listed and can be displayed. The properties window for each simulation contains an additional tab with output related to mobiles.

Note:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

563

Atoll User Manual 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.

Tip:

When you are working on very large radio-planning projects, you can reduce memory consumption by selecting Only the Average Smulation and Statistics under Information to retain.

6. Under Cell Load Constraints on the General tab, you can set the constraints that Atoll must respect during the simulation: Number of CEs: Select the Number of CEs check box if you want Atoll to respect the number of channel elements defined for each site. Iub Throughputs: Select the Iub Throughputs check box if you want Atoll to respect the maximum Iub backhaul throughputs defined for each site. Number of Codes: Select the Number of Codes check box if you want Atoll to respect the number of OVSF codes available each cell. 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 Threshold. 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 Threshold. 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 ( select Defined per Cell. ) beside the box and

7. Under Bearer Negotiation on the General tab, check the Bearer Downgrading check box if you want to permit bearer downgrading during the simulation. When a constraint is not respected, user radio bearers with services supporting bearer downgrading are downgraded. If the constraint is still not satisfied after downgrading, users are rejected. If downgrading is not selected, users will be rejected immediately, starting with users with the lowest service priority, if a constraint can not be respected. 8. On the Source Traffic tab, enter the following: Global Scaling Factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). Select Traffic Maps to Be Used: Select the traffic maps you want to use for the simulation. You can select traffic maps of any type. However, if you have several different types of traffic maps and want to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 550. 9. Click the Advanced tab. 10. Under Generator Initialisation, enter an integer as the generator initialisation value. If you enter "0", the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value.

Tip:

Using the same generated user and shadowing error distribution for several simulations can be useful when you want to compare the results of several simulations where only one parameter changes.

11. Under Convergence, enter the following parameters: Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the uplink that must be reached between two iterations. DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the downlink that must be reached between two iterations.

12. Once you have defined the simulation, you can run it immediately or you can save it to run it later: Run: Click Run to save the defined simulation and run it immediately OK: Click OK to save the defined simulation without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

564

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. You can now use the completed simulations for specific UMTS and HSDPA coverage predictions (see "Making Coverage Predictions Using Simulation Results" on page 578) or for an AS analysis using the Point Analysis window (see "Making an AS Analysis of Simulation Results" on page 578).

7.3.4.3

Displaying the Traffic Distribution on the Map

Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to service, activity status, pilot signal strength, or soft handover gain. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 33. In this section are the following examples of traffic distribution: "Displaying the Traffic Distribution by Handover Status" on page 565 "Displaying the Traffic Distribution by Connection Status" on page 565 "Displaying the Traffic Distribution by Service" on page 566.

Tip:

You can make the traffic distribution easier to see by hiding geo data and predictions. For information, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.

7.3.4.3.1

Displaying the Traffic Distribution by Handover Status

In this example, the traffic distribution is displayed by the handover status. To display the traffic distribution by the handover status: 1. Click the Data tab in the Explorer window. 2. Right-click the UMTS Simulations folder. The context menu appears. 3. Select Properties from the context menu. The UMTS Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "HO Status (Sites/No. Transmitters Act. Set)" as the Field. 5. Click OK. The traffic distribution is now displayed by handover status (see Figure 7.308).

Figure 7.308: Displaying the traffic distribution by handover status

7.3.4.3.2

Displaying the Traffic Distribution by Connection Status

In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Click the Data tab in the Explorer window. 2. Right-click the UMTS Simulations folder. The context menu appears. 3. Select Properties from the context menu. The UMTS Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Connection Status" as the Field. 5. Click OK. The traffic distribution is now displayed by connection status (see Figure 7.309).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

565

Atoll User Manual

Figure 7.309: Displaying the traffic distribution by connection status

7.3.4.3.3

Displaying the Traffic Distribution by Service

In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Click the Data tab in the Explorer window. 2. Right-click the UMTS Simulations folder. The context menu appears. 3. Select Properties from the context menu. The UMTS Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 7.310).

Figure 7.310: Displaying the traffic distribution by service

7.3.4.4

Displaying the User Active Set on the Map

Atoll enables you to display on the map the active set for each user generated by a simulation. To display the active set for a user: On the map, click and hold the icon of the user whose best and second-best servers you want to display. The servers in the users active set are connected to the user with lines the same colour as the serving transmitter. The best server is indicated with the number "1", the second-best with number "2" and so on. Figure 7.311 shows a user with three servers in his active set.

566

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.311: The active set of a user

7.3.4.5

Displaying the Results of a Single Simulation

After you have created a simulation, as explained in "Creating Simulations" on page 563, you can display the results. To access the results of a single simulation: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( you want to access. ) to expand the UMTS Parameters folder. ) to expand the folder of the simulation group containing the simulation whose results

4. Right-click the simulation. The context menu appears. 5. Select Properties from the context menu. The simulation properties dialogue appears. One tab gives statistics of the results of the simulation. Other tabs in the simulation properties dialogue contain simulation results as identified by the tab title. A final tab lists the initial conditions of the simulation. The amount of detail available when you display the results depends on the level of detail you selected from the Information to retain list on the General tab of the properties dialogue for the group of simulations. For more information on the different options, see step 5. of "Creating Simulations" on page 563. The Statistics tab: The Statistics tab contains the following two sections: Request: Under Request, you will find data on the connection requests: Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet finished. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the UL and DL rates that all active users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL rates) is given. The number of iterations that were run in order to converge. The number and the percentage of rejected users is given along with the reason for rejection. These figures include rejected users only. These figures are determined at the end of the simulation and depend on the network design. The number and the percentage of delayed users is given along with the reason for delay. The number and percentage of R99 bearer users connected to a cell, the number of users per frequency band for a dual-band network, the number of users per activity status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA and HSUPA bearer users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm. These data are also given per service. The total number and the percentage of connected users with an HSDPA bearer, the number of users per frequency band for a dual-band network, the number of users per activity status, and the DL total rate that they generate. Packet (HSDPA), packet (HSPA) and packet (HSPA - Constant Bit Rate) service users are considered since they all request an HSDPA bearer. The total number of connected HSUPA bearer users and the percentage of users with an HSUPA bearer, the number of users per frequency band for a dual-band network, the number of users per activity status, and the UL total rate they generate. Only packet (HSPA) and packet (HSPA - Constant Bit Rate) service users are considered.

Results: Under Results, you will find data on connection results: -

The Sites tab: The Sites tab contains the following information per site: Max No. of DL and UL CEs: The maximum number of channel elements available on uplink and downlink for R99 bearers requested by the users. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

567

Atoll User Manual 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. Compressed Mode: Whether compressed mode is supported. This option is defined on the site equipment. Max Iub Downlink and Uplink Backhaul Throughput (kbps): The maximum Iub backhaul throughput in the downlink and uplink . Iub Downlink and Uplink Backhaul Throughput (kbps): The Iub backhaul throughput required on downlink and uplink to handle the traffic of current simulation. Overhead Iub Throughput (kbps): the Iub throughput required by the site for common channels in the downlink. It corresponds to the overhead Iub throughput per cell (defined on the site equipment) multiplied by the number of cells on the site. HSDPA Iub Backhaul Overhead (%): This parameter is defined on the site equipment. It corresponds to the percentage of the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corresponds to the Iub backhaul throughput required by the HSDPA bearer user for HS Channels in the downlink. Nb of Recommended E1/T1/Ethernet Link: The number of E1/T1/Ethernet links required to provide the total Iub backhaul throughput. Instantaneous HSDPA Rate (kbps): The Instantaneous HSDPA Rate (kbps). Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps). HSUPA Rate (kbps): The HSUPA peak rate in kbps. DL and UL Throughput for Each Service: The R99 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 Loss (dB): The reception loss as defined in the transmitter properties. Transmission Loss (dB): The transmission loss as defined in the transmitter properties. BTS Noise Figure (dB): The BTS 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. Note: 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 dialogue. 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 dialogue. UL load factor (%): The uplink cell load factor corresponds to the ratio between the uplink total interference and the uplink total noise. If the constraint "UL load factor" has been selected, UL cell load factor is not allowed to exceed the user-defined maximum UL load factor (either in the cell properties, or in the simulation creation dialogue).

568

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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). 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 RLC Peak Rate (kbps): The minimum HSDPA RLC peak rate corresponds to the lowest of RLC peak rates obtained by HSDPA bearer users connected to the cell. Max HSDPA RLC Peak Rate (kbps): The maximum HSDPA RLC peak rate corresponds to the highest of RLC peak rates obtained by HSDPA bearer users connected to the cell. Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA rate (kbps) is the average number of kbits per second that the cell supports on downlink to provide one connected user with an HSDPA bearer. Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate (kbps) is the number of kbits per second that the cell supports on downlink to provide simultaneous connected users with an HSDPA bearer. Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that the cell carries. 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. No. of HSDPA Users: The number of HSDPA users including the connected and delayed HSDPA bearer users. 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, Multiple Causes, 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: Note: The Mobiles tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 563, you select either "Standard information about mobiles" or "Detailed information about mobiles" under Information to Retain.

X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second random trial). Service: The service assigned during the first random trial during the generation of the user distribution. Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal and the user profile.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

569

Atoll User Manual User: 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: 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. Frequency Band: the frequency band used for the mobile-transmitter connection. DL and UL Total Requested Rate (kbps): For circuit and packet (R99) service users, the DL and UL total requested rates correspond to the DL and UL nominal rates of the R99 bearer associated to the service. For packet (HSDPA) service users, the uplink total requested rate corresponds to the nominal rate of ADPCHUL64 R99 bearer and the downlink total requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate that the selected HSDPA radio bearer can provide. Here, the HSDPA user is treated as if he is the only user in the cell and then, Atoll determines the HSDPA bearer the user would obtain by considering the entire HSDPA power available of the cell. For HSUPA bearer users (i.e., packet (HSPA) and packet (HSPA - Constant Bit Rate) service users), the uplink total requested rate is equal to the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate of the requested HSUPA radio bearer. The requested HSUPA radio bearer is selected from the HSUPA bearers compatible with the user equipment. Here, the HSUPA user is treated as if he is the only user in the cell and then, Atoll determines the HSUPA bearer the user would obtain by considering the entire remaining load of the cell. The downlink total requested rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate that the requested HSDPA radio bearer can provide. The requested HSDPA bearer is determined as explained in the previous paragraph. DL and UL Total Obtained Rate (kbps): For circuit and packet (R99) service users, the DL or UL total obtained rate is the same as the DL or UL total requested rate if he is connected without being downgraded. Otherwise, the total obtained rate is lower (it corresponds to the nominal rate of the selected R99 bearer). If the user was rejected, the total obtained rate is zero. For a packet (HSDPA) service user connected to an HSDPA bearer, the uplink total obtained rate equals the requested one and the downlink total obtained rate corresponds to the instantaneous rate; this is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearer after scheduling and radio resource control. If the user is delayed (he is only connected to an R99 radio bearer), uplink and downlink total obtained rates correspond to the uplink and downlink nominal rates of ADPCH-UL64 radio bearer. Finally, if the user is rejected either in the R99 part or in the HSDPA part (i.e., because the HSDPA scheduler is saturated), the uplink and downlink total obtained rates are zero. For a connected packet (HSPA) service user, on uplink, if the user is connected to an HSUPA bearer, the uplink total obtained rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSUPA radio bearer after noise rise scheduling. On downlink, if the user is connected to an HSDPA bearer, the downlink total obtained rate corresponds to the instantaneous rate. The instantaneous rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearer after scheduling and radio resource control. If the user is delayed, the downlink total obtained rate corresponds to the downlink nominal rate of ADPCH-EDPCCH radio bearer. If the user is rejected, the uplink and downlink total obtained rates are "0". For a connected packet (HSPA - Constant Bit Rate) service user, the uplink and downlink total obtained rates are the sum of the ADPCH-EDPCCH radio bearer nominal rate and the guaranteed bit rate defined for the service. If the user is rejected, the uplink and downlink total obtained rates are "0". Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the terminal. Connection Status: The connection status indicates whether the user is connected, delayed or rejected at the end of the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection cause is given. If delayed (for packet (HSDPA) and packet (HSPA) service users only), the status is "HSDPA delayed." Best Server: The best server among the transmitters in the mobile active set. HO Status (Sites/No. Transmitters Act. Set): The HO status is the number of sites compared to the number of transmitters in the active set. AS1, AS2, AS3, AS4: The name of the cell that is the best server, the second-best server, and so on is given in a separate column for each cell in the active set. Ec/I0 AS1, AS2, AS3, AS4, (dB): EcI0 is given in a separate column for each cell in the active set. The Ec/ I0 AS 1 column lists the Ec/I0 from the best server for the rejected mobiles as well. Indoor: This field indicates whether indoor losses have been added or not. Active Compressed Mode: This field indicates whether active compressed mode is supported by the mobile or not.

The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on page 563, you select "Detailed information about mobiles" under Information to Retain: DL and UL Requested RLC Peak Rates (kbps): Downlink and uplink requested RLC peak rates are not calculated for circuit and packet (R99) service users. For packet (HSDPA) service users, the uplink RLC peak rate is not calculated and the downlink requested RLC peak rate is the rate that the selected HSDPA radio bearer can provide. For HSUPA bearer users (i.e., packet (HSPA) and packet (HSPA - Constant Bit Rate) service users), the requested uplink RLC peak rate is the rate of the requested HSUPA radio bearer. If the user is connected to an HSDPA bearer in the downlink, the downlink requested RLC peak rate is the rate that the requested HSDPA radio bearer can provide.

570

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks DL and UL Obtained RLC Peak Rate (kbps): Downlink and uplink obtained RLC peak rates are not calculated for circuit and packet (R99) service users. For a packet (HSDPA) service user connected to an HSDPA bearer, the downlink obtained RLC peak rate is the rate provided by the selected HSDPA radio bearer after scheduling and radio resource control. The uplink obtained RLC peak rate is not calculated. For a connected packet (HSPA) service user, on uplink, if the user is connected to an HSUPA bearer, the obtained uplink RLC peak rate is the rate provided by the selected HSUPA radio bearer after noise rise scheduling. On downlink, if the user is connected to an HSDPA bearer, the downlink obtained RLC peak rate is the rate provided by the selected HSDPA radio bearer after scheduling and radio resource control. For a connected packet (HSPA - Constant Bit Rate) service user, the uplink and downlink obtained RLC peak rates are the uplink and downlink guaranteed bit rates defined for the service. HSDPA Application Throughput (kbps): The HSDPA application throughput is the net HSDPA throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the instantaneous HSDPA rate (i.e., the DL obtained rate), the BLER, the HSDPA service scaling factor and the throughput offset. Served HSDPA Power (dBm): This is the HSDPA power required to provide the HSDPA bearer user with the downlink obtained rate. Required HSDPA Power (dBm): The required HSDPA power is the HSDPA power required to provide the HSDPA bearer user with the downlink requested rate. If the HSDPA bearer allocated to the user is the best one, the required HSDPA power corresponds to the available HSDPA power of the cell. On the other hand, if the HSDPA has been downgraded in order to be compliant with cell and UE capabilities, the required HSDPA power will be lower than the available HSDPA power of the cell. No. of HSUPA Retransmissions (Required): The maximum number of retransmissions in order to have the requested HSUPA radio bearer with a given BLER. No. of HSUPA Retransmissions (Obtained): The maximum number of retransmissions in order to have the obtained HSUPA radio bearer with a given BLER. HSUPA Application Throughput (kbps): The HSUPA application throughput is the net HSUPA throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the UL obtained rate, the BLER, the HSUPA service scaling factor and the throughput offset. Cell TCH Power AS1, AS2, AS3, AS4 (DL) (dBm): The cell power transmitted on the downlink is given for each link between the mobile and a transmitter in the active set. DL Ntot AS1, AS2, AS3, AS4 (dBm): The total noise on the downlink for each link between the mobile and a transmitter in the \active set. Load Factor AS1, AS2, AS3, AS4 (DL) (%): The load factor on the downlink for each link between the mobile and a transmitter in the active set. It corresponds to the ratio between the total interference on the downlink and total noise at the terminal. Noise Rise AS1, AS2, AS3, AS4 (DL) (dB): The noise rise on the downlink for each link between the mobile and a transmitter in the active set. Reuse Factor AS1, AS2, AS3, AS4 (DL): The DL reuse factor for each link between the mobile and a transmitter in the active set. It is calculated from the interference received at the terminal from the intra cell area and the total interference received at the terminal from all the transmitters (intra and extra-cell and inter-carrier). Iintra AS1, AS2, AS3, AS4 (DL) (dBm): The intra-cell interference for each cell (I) of the active set.

PSCH DL I int ra = P DL (ic ) Fortho P DL (ic ) 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

PSCH P DL (ic ) Fortho P DL (ic ) 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

571

Atoll User Manual 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: Note: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 563, you select "Detailed information about mobiles" under Information to Retain.

Name: The name assigned to the mobile. Value at Receiver (dB): The value of the shadowing margin at the receiver. Clutter: The clutter class on which the mobile is located. Path To: The name of the potential transmitter. Value (dB): The shadowing value for the potential link in the corresponding Path To column. These values depend on the model standard deviation per clutter type on which the receiver is located and are randomly distributed on a gaussian curve.

The Initial Conditions tab: The Initial Conditions tab contains the following information: The global transmitter parameters: The spreading width Whether the power values on the downlink are absolute or relative to the pilot The default uplink soft handover gain Whether the MRC in softer/soft is defined or not The methods used to calculate I0 and Nt Parameters for compressed mode The methods used to calculate Nt and CQI for HSDPA. The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink convergence thresholds The simulation constraints such as maximum power, the maximum number of channel elements, the maximum Iub throughputs, the uplink load factor and the maximum load The name of the traffic maps used.

The input parameters specified when creating the simulation:

The parameters related to the clutter classes, including the default values.

7.3.4.6

Displaying the Average Results of a Group of Simulations

After you have created a group of simulations, as explained in "Creating Simulations" on page 563, you can display the average results of the group. If you wish to display the results of a single simulation of a group, see "Displaying the Results of a Single Simulation" on page 567. To access the averaged results of a group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the group of simulations whose results you want to access. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. The Statistics tab: The Statistics tab contains the following two sections: Request: Under Request, you will find data on the connection requests: Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet finished. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service. The UL and DL rates that all users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL rates) is given. The number of iterations that were run in order to converge. The number and the percentage of rejected users is given along with the reason for rejection. These figures include rejected users only. These figures are determined at the end of the simulation and depend on the network design. The number and the percentage of delayed users is given along with the reason for delay. The number and percentage of R99 bearer users connected to a cell, the number of users per frequency band for dual-band networks, the number of users per activity status, and the total UL and DL rates they generate. These figures include R99 users as well as HSDPA and HSUPA bearer users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm. These data are also given per service.

Results: Under Results, you will find data on the connection results: -

572

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks The total number and the percentage of connected users with an HSDPA bearer, the number of users per frequency band for dual-band networks, the number of users per activity status, and DL total rate that they generate. Packet (HSDPA), packet (HSPA) and packet (HSPA - Constant Bit Rate) service users are considered since they all request an HSDPA bearer. The total number of connected HSUPA bearer users and the percentage of users with an HSUPA bearer, the number of users per frequency band for dual-band networks, the number of users per activity status, and UL and DL total rates they generate. Only packet (HSPA) and packet (HSPA - Constant Bit Rate) service users are considered.

The Sites (Average) and Sites (Standard Deviation) tabs: The Sites (Average) and Sites (Standard Deviation) tabs contains the following average and standard deviation information, respectively, per site: Max No. of DL and UL CEs: The maximum number of channel elements available on uplink and downlink for R99 bearers requested by the users. No. of DL and UL CEs Used: The number of channel elements required on uplink and downlink for R99 bearers to handle the traffic of current simulation. No. of DL and UL CEs Due to SHO Overhead: The number of extra channel elements due to soft handover, on 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. Compressed Mode: Whether compressed mode is supported. This option is defined on the site equipment. Max Iub Downlink and Uplink Backhaul Throughput (kbps): The maximum Iub backhaul throughput in the downlink and uplink. Iub Downlink and Uplink Backhaul Throughput (kbps): The Iub backhaul throughput required on downlink and uplink to handle the traffic of current simulation. Overhead Iub Throughput/Cell (kbps): The Iub throughput required by the cell for common channels in the downlink, defined on the site equipment. HSDPA Iub Backhaul Overhead (%): This parameter is defined on the site equipment. It corresponds to the percentage of the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corresponds to the Iub backhaul throughput required by the HSDPA bearer user for HS Channels in the downlink. Nb of Recommended E1/T1/Ethernet Link: The number of E1/T1/Ethernet links required to provide the total Iub backhaul throughput. Instantaneous HSDPA Rate (kbps): The Instantaneous HSDPA Rate (kbps). Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps). HSUPA Rate (kbps): The HSUPA peak rate in kbps. DL and UL Throughput for Each Service: The R99 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 Loss (dB): The reception loss as defined in the transmitter properties. Transmission Loss (dB): The transmission loss as defined in the transmitter properties. BTS Noise Figure (dB): The BTS 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

573

Atoll User Manual

Note:

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 dialogue. 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 dialogue. UL Load Factor (%): The uplink cell load factor corresponds to the ratio between the uplink total interference and the uplink total noise. If the constraint "UL load factor" has been selected, UL cell load factor is not allowed to exceed the user-defined maximum UL load factor (either in the cell properties, or in the simulation creation dialogue). UL Load Factor due to HSUPA (%): The uplink cell load caused by HSUPA traffic. DL Load Factor (%): The DL load factor of the cell i corresponds to the ratio (DL average interference [due to 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 allocated dynamically, the DL R99 Load can not exceed the user-defined Max DL Load (defined either in the cell properties, or in the simulation). Reuse Factor (UL): The uplink reuse factor is the ratio between the uplink total interference and the intra-cell interference. Reuse Efficiency Factor (UL): The uplink reuse efficiency factor is the reciprocal of the uplink reuse factor. Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter links on the same carrier. This data is calculated on uplink and on downlink and indicates the number of users connected to the cell on uplink and downlink. Because of handover, a single user can use several radio links. Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total number of users in the cell. HSDPA Application Throughput (kbps): The HSDPA application throughput is the net HSDPA throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the instantaneous HSDPA rate (i.e., the DL obtained rate), the BLER, the HSDPA service scaling factor and the throughput offset. Min. HSDPA RLC Peak Rate (kbps): The minimum HSDPA RLC peak rate corresponds to the lowest of RLC peak rates obtained by HSDPA bearer users connected to the cell. Max HSDPA RLC Peak Rate (kbps): The maximum HSDPA RLC peak rate: It corresponds to the highest of RLC peak rates obtained by HSDPA bearer users connected to the cell. Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA rate (kbps) is the average number of kbits per second that the cell supports on downlink to provide one connected user with an HSDPA bearer. Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate (kbps) is the number of kbits per second that the cell supports on downlink to provide simultaneous connected users with an HSDPA bearer. Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that the cell carries. 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. No. of HSDPA Users: The number of HSDPA users include the connected and delayed HSDPA bearer users. 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.

574

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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, Multiple Causes, Code Saturation, Admission Rejection, HSDPA Delayed, HSDPA Scheduler Saturation, HSDPA Resource Saturation, HSUPA Admission Rejection, HSUPA Scheduler Saturation and Iub Throughput Saturation. Delayed users are regrouped under HSDPA Delayed. Connection Success Rate (%) For Each Service: For each service, the connection success rate gives the ratio of connected users over the total number of users of that service in the cell.

The Initial Conditions tab: The Initial Conditions tab contains the following information: The global transmitter parameters: The spreading width Whether the power values on the downlink are absolute or relative to the pilot The default uplink soft handover gain Whether the MRC in softer/soft is defined or not The methods used to calculate I0 and Nt Parameters for compressed mode The methods used to calculate Nt and CQI for HSDPA. The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink convergence thresholds The simulation constraints such as maximum power, the maximum number of channel elements, the uplink load factor and the maximum load The name of the traffic maps used.

The input parameters specified when creating the group of simulations:

The parameters related to the clutter classes, including the default values.

7.3.4.7

Updating Cell Values With Simulation Results

After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 563, you can update values for each cell with the results calculated during the simulation. The following values are updated: Total Transmitted Power UL Load Factor UL Reuse Factor Available HSDPA Power Number of HSDPA Users UL Load Factor due to HSUPA Number of HSUPA Users.

To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the UMTS Parameters folder.

c. Right-click the group of simulations whose results you want to access. d. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. To display the results for a single simulation: a. Click the Data tab in the Explorer window. b. Click the Expand button ( c. Click the Expand button ( sults you want to access. ) to expand the UMTS Parameters folder. ) to expand the folder of the simulation group containing the simulation whose re-

d. Select Properties from the context menu. The simulation properties dialogue appears. 2. Click the Cells tab. 3. On the Cells tab, click Commit Results. The following values are updated for each cell: Total Transmitted Power UL Load Factor UL Reuse Factor Available HSDPA Power Number of HSDPA Users UL Load Factor due to HSUPA Number of HSUPA Users.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

575

Atoll User Manual

7.3.4.8

Adding New Simulations to an Atoll Document

When you have created a simulation or group of simulations, you can re-examine the same conditions by adding new simulations to the Atoll document. In Atoll, there are the following ways of adding new simulations: Adding to a group: When you add one or more simulations to an existing group of simulations, Atoll reuses the same input (radio, traffic, and simulation parameters) as those used to generate the group of simulations. It then generates a new user distribution and performs the power control simulation. To add a simulation to a group of simulations, see "Adding a Simulation to a Group of Simulations" on page 576. Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution (users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shadowing error distribution between simulations is different. Traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) might or might not be taken into account. Finally, radio data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the power control (or rate/power control) simulation. To replay a group of simulations, see "Replaying a Simulation or Group of Simulations" on page 576. Using the Generator Initialisation Number: When you create groups of simulations using the same generator initialisation number (which must be an integer other than 0) Atoll generates the same user and shadowing error distributions (user with a service, a mobility, an activity status and a shadowing error) in all groups using the same number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers allowed, EbNt thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during the power control simulation. By creating and calculating one group of simulations, making a change to the network and then creating and calculating a new group of simulations using the same generator initialisation number, you can see the difference your parameter changes make. To create a new simulation to a group of simulations using the generator initialisation number, see "Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number" on page 577. Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation parameters as those used to generate the group of simulations. You can then modify the simulation parameters before calculating the group. To duplicate a group of simulations, see "Duplicating a Simulation or Group of Simulations" on page 577.

Adding a Simulation to a Group of Simulations

To add a simulation to an existing group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Simulations folder.

3. Right-click the group of simulations to which you want to add a simulation. The context menu appears. 4. Select New from the context menu. The properties dialogue of the group of simulations appears. Note: When adding a simulation to an existing group of simulations, the parameters originally used to calculate the group of simulations are used for the new simulations. Consequently, few parameters can be changed for the added simulation.

5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations. 6. Under Execution on the General tab, you can set the following parameter: Number of Simulations: Enter the number of simulations to added to this group of simulations.

7. Once you have added the simulation, you can run it immediately or you can save it to run it later: Run: Click Run to save the defined simulation and run it immediately OK: Click OK to save the defined simulation without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Replaying a Simulation or Group of Simulations

To replay an existing simulation or group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Simulations folder.

3. Right-click the group of simulations you want to replay. The context menu appears. 4. Select Replay from the context menu. The properties dialogue of the group of simulations appears.

576

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Note:

When replaying an existing group of simulations, some parameters originally used to calculate the group of simulations are reused for the replayed group. Consequently, few parameters can be changed for the replayed group.

5. In the General tab of the dialogue, you can set the following parameters: Select the level of detail as explained in "Creating Simulations" on page 563 that will be available in the output from the Information to retain list. Under Cell Load Constraints, you can set the constraints as explained in "Creating Simulations" on page 563 that Atoll must respect during the simulation. Under Bearer Negotiation, check the Bearer Downgrading check box if you want to permit bearer downgrading during the simulation.

6. In the Source Traffic tab of the dialogue, select the Refresh Traffic Parameters check box if you want to take into account traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) in the replayed simulation. 7. In the Advanced tab, you can set the following parameters: Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the uplink that must be reached between two iterations. DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the downlink that must be reached between two iterations.

8. Click Run. Atoll immediately begins the simulation.

Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number
To create a new simulation or group of simulations using the generator initialisation number: 1. Click the Data tab in the Explorer window. 2. Right-click the UMTS Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. Click the Advanced tab. 5. Under Generator Initialisation, enter an integer as the generator initialisation value. The integer must be the same generator initialisation number as used in the group of simulations with the user and shadowing error distributions you want to use in this simulation or group of simulations. If you enter "0", the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. 6. For information on setting other parameters, see "Creating Simulations" on page 563.

Tip:

You can create a new group of simulations with the same parameters as the original group of simulations by duplicating an existing one as explained in "Duplicating a Simulation or Group of Simulations" on page 577.

Duplicating a Simulation or Group of Simulations

To duplicate an existing simulation or group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Simulations folder.

3. Right-click the simulation or group of simulations you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The properties dialogue for the duplicated group of simulations appears. You can change the parameters for the duplicated simulation or group of simulations as explained in "Creating Simulations" on page 563.

7.3.4.9

Estimating a Traffic Increase

When you create a simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increased traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations by: Creating a new simulation or group of simulations as described in "Creating Simulations" on page 563. Duplicating an existing simulation or group of simulations as described in "Adding New Simulations to an Atoll Document" on page 576.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

577

Atoll User Manual 2. Click the Source Traffic tab of the properties dialogue. 3. Enter a Global Scaling Factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).

7.3.5

Analysing the Results of a Simulation

In Atoll, you have several methods available to help you analyse simulation results. You can make an active set analysis of a real-time probe user or you can make a coverage study where each pixel is considered as a probe user with a defined terminal, mobility, and service. The analyses are based on a single simulation or on an averaged group of simulations. You can find information on the analysis methods in the following sections: "Making an AS Analysis of Simulation Results" on page 578 "Making Coverage Predictions Using Simulation Results" on page 578.

7.3.5.1

Making an AS Analysis of Simulation Results

The Point Analysis window gives you information on reception for any point on the map. The AS Analysis tab gives you 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. Analysis is based on the UL load percentage and the DL total power of cells. In this case, these parameters can be either outputs of a given simulation, or average values calculated from a group of simulations. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 661. Before you make an AS analysis: Ensure the simulation or group of simulations you want to use in the AS analysis is displayed on the map. Replay the simulation or group of simulations you want to use if you have modified radio parameters since you made the simulation. Note: The AS analysis does not take possible network saturation into account. Therefore, there is no guarantee that a simulated mobile with the same receiver characteristics can verify the point analysis, simply because the simulated network may be saturated.

To make an AS analysis of simulation results: 1. Click the Point Analysis button ( 2. Click the AS Analysis tab. 3. At the top of the AS Analysis tab, select from the Load Conditions list, the simulation or group of simulations you want to base the AS analysis on. 4. Select the Terminal, Service, and Mobility. 5. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. 6. Select or clear the following options: Whether shadowing is to be taken into account (and, if so, the cell edge coverage probability). Whether indoor coverage is to be taken into account. Whether downgrading is allowed. ) on the toolbar. The Point Analysis window appears. (see Figure 7.282).

7. Click OK to close the Properties dialogue. 8. Move the pointer over the map to make an active set analysis for the current location of the pointer. As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 7.300 on page 524). Information on the current position is given on the AS Analysis tab of the Point Analysis window. See Figure 7.301 on page 525 for an explanation of the displayed information. 9. 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. 10. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.

7.3.5.2

Making Coverage Predictions Using Simulation Results

When no simulations are available, Atoll uses the UL load factor, the DL total power, the UL reuse factor, the available HSDPA power, the number of HSDPA users, the number of HSUPA users, and the UL load factor due to HSUPA defined for each cell to make coverage predictions. For information on cell properties, see "Creating or Modifying a Cell" on page 474; for information on modifying cell properties, see "Cell Definition" on page 470. Once you have made simulations, Atoll can use this information instead of the defined parameters in the cell properties to make coverage predictions where each pixel is considered as a probe user with a terminal, mobility, profile, and service.

578

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, choosing either an average analysis of all simulations in the group or a statistical analysis based on a defined probability. To be able to base a coverage prediction on a simulation or group of simulations, the simulation must have converged. The coverage predictions that can use simulation results are: Coverage predictions on the pilot or on a service: Pilot Reception Analysis: For information on making a pilot reception analysis, see "Making a Pilot Signal Quality Prediction" on page 515. Service Area Downlink: For information on making a coverage prediction on the downlink service area, see "Studying Service Area (EbNt) Downlink or Uplink" on page 516. Service Area Uplink: For information on making a coverage prediction on the uplink service area, see "Studying Service Area (EbNt) Downlink or Uplink" on page 516. Effective Service Area: For information on making a effective service area analysis, see "Studying Effective Service Area" on page 517. Downlink Total Noise: For information on making a downlink total noise coverage prediction, see "Studying Downlink Total Noise" on page 520. Pilot Pollution: For information on making a pilot pollution coverage analysis, see "Calculating Pilot Pollution" on page 521. Handoff Status: For information on making a handover status coverage prediction, see "Making a Handover Status Coverage Prediction" on page 522.

Coverage predictions on noise and interference: -

A handover status coverage prediction to analyse macro-diversity performance: -

An HSDPA coverage prediction to analyse A-DPCH qualities, HS-SCCH power or quality per HS-SCCH channel and to model fast link adaptation. HSDPA Coverage Prediction: For information on making an HSDPA coverage prediction, see "HSDPA Coverage Prediction" on page 525.

An HSUPA coverage prediction to analyse the required E-DPDCH Ec/Nt, the required terminal power, and the obtained HSUPA bearer. HSUPA Coverage Prediction: For information on making an HSUPA coverage prediction, see "HSUPA Coverage Prediction" on page 527.

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 Condition 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 Condition 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: 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.

7.4

Optimising Network Parameters Using the ACP

Atoll Automatic Cell Planning (ACP) enables radio engineers designing UMTS networks to automatically calculate the optimal network settings in terms of network coverage and capacity. Atoll ACP can also be used in co-planning projects where UMTS networks must both be taken into consideration when calculating the optimal network settings. Coverage maps are used for the optimisation process, however, traffic maps can be used for weighting network load distribution. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and cell pilot power. ACP can also be used during the initial planning stage of a UMTS network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only takes transmitters into account in optimisations but also any repeaters and remote antennas. ACP also enables you to select to select which sites can be added or removed to improve existing or new networks.

7.4.1

The ACP Module and Atoll

Atoll ACP can be used either with existing networks or with networks in the initial planning phases. With existing networks, it is most efficient to focus on tuning the parameters that can be easily changed remotely, for example: Antenna electrical tilt: ACP adjusts the electrical tilt by selecting the best antenna from the antenna group assigned to this transmitter. Pilot power for each cell: The pilot power is set within a defined minimum and maximum value for each cell.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

579

Atoll User Manual When optimising a network that is still in the planning phase, Atoll ACP can calculate how the network can be improved by: Selecting the antenna type for each transmitter: ACP selects the best antenna from the antenna group assigned to this transmitter. Changing the antenna azimuth: ACP sets the antenna azimuth using a defined range on either side of the currently defined azimuth. Changing the mechanical tilt of the antenna: ACP sets the mechanical tilt using a defined range on either side of the currently defined mechanical tilt. Changing the height of the antenna: ACP sets the optimal antenna height using a defined range on either side of the currently defined antenna height. Selecting sites: ACP adds or removes sites that you have indicated as candidates for addition or removal in order to improve existing or new networks.

In this section, the following are explained: "Using Zones with ACP" on page 580 "Using Traffic Maps with ACP" on page 580 "Shadowing Margin and Indoor Coverage" on page 581 "ACP and Antenna Masking" on page 581.

7.4.1.1

Using Zones with ACP

ACP uses different zones during the optimisation process for different purposes. ACP uses the computation zone to define the area of the network to be optimised. ACP always takes the entire computation zone into consideration, even if the zone selected for optimisation is the focus zone; the sites and transmitters included in the computation zone and not in the focus zone are still taken into consideration when calculating signal, interference, and best server status. ACP enables you to define different targets and different weights for each zone: for the computation zone, for the focus zone, for the hot spot zones, and for each clutter classes. In this section, the following are explained: "Using the Computation Zone and the Focus Zone" on page 580 "Using Hot Spots" on page 580 "Using the Filtering Zone" on page 580.

7.4.1.1.1

Using the Computation Zone and the Focus Zone

Atoll ACP optimises the settings for the sites in either the computation zone or the focus zone. If you have both a computation zone and a focus zone defined, you can select which zone will be used for the optimisation process. If there is no focus or computation zone, the ACP optimises the settings for the cells in a rectangle including all cells in the network. Atoll ACP allows you to define different targets for the computation zone and the focus zone, as well as for the hot spot zones. You can also define different weights for each zone. Note: It is recommended to define a computation zone. ACP uses the computation zone as the area in which the quality figures are calculated and improved during optimisation. Additionally, the zone defined by ACP might take into account areas outside of actual traffic boundaries.

7.4.1.1.2

Using Hot Spots

Atoll ACP also allows you to use hot spot zones, enabling you to specify different quality targets for each hot spot zone and display final results per zone. You can also define different weights for each zone. You can use the hot spot zones defined in the Atoll document, import ArcView SHP files to create hot spot zones, or you can create hot spot zones based on clutter classes.

7.4.1.1.3

Using the Filtering Zone

If there is a filtering zone defined, Atoll ACP will optimise all currently defined and active cells selected by the filtering zone.

Note:

ACP automatically considers all the cells that have an effect on the computation or focus zone, and ignores the rest (for example, cells that are too far away to have an impact on the selected cells). It is nonetheless recommended to use a filtering zone to speed up initial data extraction from the Atoll document.

7.4.1.2

Using Traffic Maps with ACP

Atoll ACP can use traffic maps to determine the traffic density on each pixel. The traffic density is used to weight each of the quality figures according to traffic and to put more emphasis on high traffic areas. You can set traffic weighting separately for each quality indicator. For example, you can use a uniform map for RSCP and a traffic-weighted map for EcIo. The calculation for network quality always uses traffic maps if they are present.

580

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.312: ACP traffic parameters When you use selected traffic maps, ACP allows you to define a resolution to extract the data from traffic maps. The resolution should usually be the same as the resolution of the traffic maps. To increase the accuracy of the data-extraction process, you can increase the resolution defined in the Extract traffic with resolution text box. In the ACP, each traffic map is converted into one or more traffic profiles. A traffic profile is a combination of: a service, terminal, and mobility a traffic distribution a relative load (expressed in Erlangs). Note: For the moment, traffic profiles are only used to evaluate the traffic weighting to apply to each pixel (by adding the load-scaled traffic distribution on each traffic profile). This information will also be used in the future to better manage cell load (and the evaluation of network quality).

7.4.1.3

Shadowing Margin and Indoor Coverage

Atoll ACP enables you to take indoor coverage and a shadowing margin into consideration. When indoor coverage is taken into consideration, all pixels marked as indoors have an additional indoor loss added to total losses. The indoor loss is defined per clutter class. By default, ACP considers all pixels to be indoors, but Atoll ACP allows you to specify which clutter class should be considered as indoors and which not. When the shadowing margin is taken into consideration, the defined shadowing margin is taken into consideration in the calculation of the received useful signal power and interfering signal power. For more information on how shadowing and macro-diversity gains are calculated, see the Technical Reference Guide. Note: You can set ACP to not take macro-diversity gains into consideration by setting the appropriate option in the acp.ini file. You will need to update the corresponding parameters in the atoll.ini file as well. For information on modifying the atoll.ini file, see the Administrator Guide.

7.4.1.4

ACP and Antenna Masking

When ACP performs any type of antenna reconfiguration, it must determine how attenuation to the path loss changes when the antenna is modified. ACP determines changes to path loss attenuation using antenna masking. Depending on the propagation model used to calculate the path loss matrices, ACP supports the following antenna masking methods: Natively supported propagation models: ACP calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. Because ACP is using the same propagation model as was used to calculate the original path loss matrices, the results are consistent and accurate. For this reason, using natively supported propagation models is the preferred method. For more information, see "Natively Supported Propagation Models" on page 581. ACPs default propagation model: If the propagation model used to calculate the original path loss matrices is not supported by ACP, ACP can use its own default propagation model. Because the ACP default propagation model is not the same as the one used to calculate the original path loss matrices, accuracy cannot be guaranteed. ACPs default propagation model is similar to Atolls Standard Propagation Model and should deliver acceptable results for any macro-type propagation model. For more information, see "ACPs Default Propagation Model" on page 582. Precalculated path loss matrices: ACP allows you to designate all propagation models in the project which are not supported by the native method. ACP will then prerecalculated path loss matrices for these propagation models. For more information, see "Precalculated Path Loss Matrices" on page 582. Note: Pilot power optimisation and site selection (without reconfiguration) are made independently of the method used to determine changes to path loss attenuation.

7.4.1.4.1

Natively Supported Propagation Models

During antenna optimisation, ACP must calculate how the attenuation to the path loss changes when the antenna is modified, i.e., when the antenna type, tile, or azimuth is modified.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

581

Atoll User Manual When ACP uses natively supported propagation models, it calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. The unmasking and remasking operations are strongly dependent on the propagation model that was used to calculate the path losses, especially to: Find the horizontal and vertical emission angles between a transmitter and the receiving pixel. The angles depend strongly on the radial method used to account for the height profile between the transmitter and receiver. Find the correct antenna gain for a given set of horizontal and vertical emission angles. The gain is usually based on a 3-D interpolation of the 2-D patterns and can be model-dependent.

How ACP calculates attenuation depends on the propagation model used by Atoll to generate the path loss. The propagation model parameters which affect processing are automatically extracted by ACP. ACP supports the propagation models commonly used in Atoll. For other propagation models, ACP uses a default model similar to Cost-Hata, however, you can always set ACP to use another propagation model, the SPM for example, if you feel it would give more accurate results. The raster data needed by ACP depends on the propagation model that Atoll used to generate the path loss.

Propagation Model
All Atoll Hata-based propagation models (Cost-Hata, Okumura-Hata, ITU, etc.)

Raster Data Required

DEM file DEM file Clutter Height file (optional) Clutter file (optional) DEM file

Atoll Standard Propagation Model

All other models.

Because the path loss information is not stored in the ACP optimisation setup but in the Atoll document where it is accessed by ACP, changes in the Atoll document can cause inconsistency between the optimisation results and the actual state of the network, for example, when transmitters are modified in the document. ACP deals with this situation by locking optimisation results. An optimisation can not be rerun on locked results if the path loss data are not consistent with the internal state of the optimisation. The results are automatically unlocked if the state of the Atoll document again becomes consistent with the ACP optimisation. The same mechanism applies when settings produced by an optimisation run are committed to the Atoll network. The results are locked after being committed and will be unlocked if the network is rolled back to the state on which the optimisation was based.

7.4.1.4.2

ACPs Default Propagation Model

ACP has an internal default propagation model that can be used if the propagation model used to calculate the original path loss matrices is not supported by ACP. Because the ACP default propagation model is not the same as the one used to calculate the original path loss matrices, accuracy can not be guaranteed, although it should deliver acceptable results for any macro-type propagation model. ACP offers a few parameters that enable you to improve the accuracy of the default propagation model: Use Clutter Height: By selecting Use Clutter Height, ACP will take into consideration clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on Top of Clutter: If the receiver is on top of the clutter, for example, if receivers are located on top of buildings, you can select Receiver on Top of Clutter. The receiver height will then be sum of the clutter height and the receiver height. Use Radial Method: You can select the Use Radial Method check box if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

These parameters can be set individually for each propagation model for which ACP will use the default propagation method. These parameters belong to the advanced parameters; to modify them, you must first make the advanced parameters visible. For information on making the advanced parameters visible, "Configuring the Default Settings" on page 583.

7.4.1.4.3

Precalculated Path Loss Matrices

After the ACP setup has been created, ACP calculates the path loss matrices necessary (i.e., for sites that are being optimised and do not use natively supported propagation models or the ACP's internal model) while the optimisation is loading. ACP does not calculate all path loss matrices for all possible combinations, for example, five possible changes in electrical tilt and five possible changes in azimuth, i.e., 25 path loss matrices to be calculated. ACP only calculates the path loss matrices for the most common optmisation changes, for example, changes to the electrical tilt. By pre-calculating only the most common changes, ACP reduces the number of path loss changes to be calculated and reduces the calculation time. While the optimisation is running, ACP uses the pre-calculated path loss matrices. If a change is made to a transmitter that was not taken into the consideration when the path loss matrices were calculated, ACP recalculates the path loss matrix for that change only. The end result are considerable savings in both time and computer resources. For information on natively supported propagation models, see "Natively Supported Propagation Models" on page 581.

582

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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, it is often similar enough to a supported propagation model so that ACP can still use it. 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. Notes: Precalculated path loss matrices can only be used when optimising the antenna type and azimuth. Optimising the mechanical tilt is not currently supported.

7.4.2

Configuring the ACP Module

You can change the default settings of the Atoll ACP module so that selected options are the default settings each time you run ACP. Additionally, you can base the default ACP settings on some or all of the settings of a given Atoll optimisation. In this section, the following are explained: "Configuring the Default Settings" on page 583 "Defining the Antenna Masking Method" on page 584 "Saving Settings to a User Configuration File" on page 585.

7.4.2.1

Configuring the Default Settings

To configure the default settings of the ACP module: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Default Settings tab. On the Default Settings tab, you can define the configuration files that contain the default settings. These settings are applied every time you run an optimisation project. Under Loading Default Settings: Global Configuration: The Global Configuration is the configuration file set up by the administrator. This configuration provides the same default settings to everyone on the network. For information on the ACP global configuration file, see the Administrator Manual. User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings you want to be the default settings for the ACP module.

5. Click the User Preferences tab. On the User Preferences tab (see Figure 7.313), you can define settings that are saved to the acp.ini configuration file found in the ACP installation folder. These settings will be applied every time you run a new configuration.

Figure 7.313: Setting ACP user preferences Under Setup Preferences: You can define the following settings:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

583

Atoll User Manual Enable automatic setting from custom table field (antennas, sites): Select the Enable automatic setting from custom table field (antennas, sites) check box if you want ACP to use the custom columns in the SITES and ANTENNAS tables. If you want ACP to use the custom columns, you must set the appropriate options in the acp.ini file. For more information on the acp.ini file, see the Administrator Manual. Show advanced optimisation settings: Select the Show advanced optimisation settings check box if you want the ACP to display the Advanced tab when you define an optimisation setup. When the Advanced tab is available, you can set a few additional options related to services, terminals, clutter, and propagation models. Calculation setting: Adjust the slider to define whether you want ACP to provide its results more quickly, at the expense of precision, or whether you want ACP to provide more accurate results, at the expense of speed. By selecting a higher speed, you will cause ACP to reduce the number of cells monitored for each pixel, some of which might only create a bit of interference at first, but which could possibly create significantly more interference after antenna parameters are changed during the optimisation process. Selecting a higher precision avoids this problem at the expense of more time and computer resources.

Under Result Preferences: You can define the following setting for report maps: Default map transparency: Define the default map transparency with the slider.

6. Click the Private Directory tab. On the Private Directory tab (see Figure 7.314), you can define the directory to be used by the ACP to store precalculated path loss matrices as well as the path loss matrices for antenna height optimisation.

Figure 7.314: Defining the directory for path loss matrices 7. Enter the name of the directory or click the the Browse button ( 8. Click OK to save your changes. When the propagation model used is not one natively supported by ACP, for example, complex ray-tracing propagation models, ACP can use precalculated path loss matrices to calculate attenuation. For more information, see "Defining the Antenna Masking Method" on page 584. ) to navigate to the directory.

7.4.2.2

Defining the Antenna Masking Method

You can define how Atoll ACP calculates path loss matrices, using either Atolls propagation models, ACPs internal propagation model, or precalculated path loss matrices. These parameters will be applied to all new and duplicated setups. To define how ACP calculates path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Antenna Masking Model tab (see Figure 7.315).

584

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.315: The Antenna Masking Model tab 5. If you are using a propagation model that ACP does not natively support, select the Enable precalculated path loss matrices check box. You will then be able to select the propagation model for which ACP will pre-calculate path attentuation. 6. Under Propagation Models, select the check boxes in each column to define how ACP will interact with that propagation model. Not all parameters are available for all propagation models:

Tip:

By default, all available propagation models are displayed. By selecting the Show only used propagation models check box, ACP will only display the propagation models that are actually used.

Antenna masking method: The Antenna masking method indicates whether ACP can use this propagation model natively, or whether ACP uses its own default method. The information in this column can not be edited. Use precalculated path loss: Select the check box in the Use precalculated path loss column corresponding to every propagation model that is not supported natively by ACP or that can not be replaced using ACPs internal default method. Use clutter height: Select the check box in the Use clutter height column if you want ACP to take clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on top of clutter: Select the check box in the Receiver on top of clutter column if you want the receiver height to be sum of the clutter height and the receiver height. This option can be used, for example, to model receivers on top of buildings. Use radial method: Select the check box in the Use radial method column if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

7. Click OK.

7.4.2.3

Saving Settings to a User Configuration File

To save the settings to a user configuration file: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Default Settings tab. On the Default Settings tab, you can define the configuration files that contain the default settings. These settings are applied every time you run an optimisation project. Under Loading Default Settings: Global Configuration: The Global Configuration indicates the configuration file set up by the administrator. This configuration provides the same default settings to everyone on the network. For information on the ACP global configuration file, see the Administrator Manual. User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings you want to be the default settings for the ACP module.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

585

Atoll User Manual 5. Click the Save Configuration File button under Saving Default Settings to save settings to a user configuration file. Note: The settings you save to a user configuration file are from an ACP optimisation from the current Atoll document. If you have not yet used ACP for an optimisation in the current document, the Save Configuration File button is not available.

When you click the Save Configuration File button, the Save Configuration File dialogue opens (see Figure 7.316).

Figure 7.316: The Save Configuration File dialogue 6. From the Save setting based on setup list, select the ACP setup on whose parameters you want to base the user configuration file. 7. Click the Browse button ( file. ) next to To configuration file to select where you will save the user configuration

8. Under Sections to save, select the check boxes of the types of parameters whose settings you want to save to the user configuration file. 9. Click Save.

7.4.3

Optimising Cell Planning with the ACP

Optimising cell planning with the Atoll ACP consists of defining the parameters that will be used during the optimisation process and then running the process. Each optimisation, with its parameters and results, is stored in a Setup folder in the ACP - Automatic Cell Planning folder on the Data tab of the Explorer window. In this section, the following are explained: "Creating an Optimisation Setup" on page 586 "Defining Optimisation Parameters" on page 587.

7.4.3.1

Creating an Optimisation Setup

In ACP, you can create an optimisation setup either by creating and running a new one, or by duplicating or opening an existing optimisation, editing the parameters, and then running it. In this section, the following are explained: "Creating a New Optimisation Setup" on page 586 "Running an Existing Optimisation Setup" on page 587 "Duplicating an Existing Optimisation Setup" on page 587.

Creating a New Optimisation Setup

To create a new optimisation setup: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 587. 4. After defining the optimisation setup:

586

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Click the Run button to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 611. Click the Create Setup button to save the defined optimisation. For information on running the optimisation, see "Running an Existing Optimisation Setup" on page 587.

Running an Existing Optimisation Setup

To run an existing optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

3. Right-click the optimisation you want to run. The context menu appears. Select Run from the context menu to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 611. Select Properties from the context menu to view or modify the parameters of the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 587.

Duplicating an Existing Optimisation Setup

To duplicate an existing optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

3. Right-click the setup you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The ACP Duplicate Options dialogue appears. 5. Under Data Synchronisation Option, select one of the following: Minimal: The duplicated ACP setup will have only the data that was changed by the ACP during optimisation. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid. Complete: The duplicated ACP setup will have have all the data from the ACP optimisation.

6. Run the existing optimisation setup as described in "Running an Existing Optimisation Setup" on page 587.

7.4.3.2

Defining Optimisation Parameters

In Atoll ACP, when you create a new optimisation setup, you must first define all the parameters. You can also modify the parameters of an existing optimisation setup before running it. Creating a new optimisation setup is explained in "Creating a New Optimisation Setup" on page 586. Running an existing optimisation is explained in "Running an Existing Optimisation Setup" on page 587. The optimisation parameters are grouped onto specific tabs of the dialogue. The parameters are the same whether you create a new optimisation setup or whether you modify the parameters of an existing one. In this section, the following parameters are explained: "Setting Optimisation Parameters" on page 587 "Setting Objective Parameters" on page 590 "Setting Traffic Parameters for Non-uniform Traffic" on page 593 "Setting Network Reconfiguration Parameters" on page 594 "Defining Site Selection Parameters" on page 600 "Defining Antenna Groups" on page 604 "Adding Comments to the Optimisation Setup" on page 608 "Setting Advanced Parameters" on page 608.

7.4.3.2.1

Setting Optimisation Parameters

The Optimisation tab allows you to define the various parameters related to the optimisation algorithm. To set the optimisation parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Optimisation tab (see Figure 7.317).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

587

Atoll User Manual

Figure 7.317: The Optimisation tab 3. Define the following: Number of Iterations: Set the number of iterations for the optimisation algorithm. ACP calculates a suggested number of iterations by multiplying the total number of parameters to optimise (i.e., cell pilot power, antennas, azimuth, mechanical tilt, sites subject to selection) by two. You can accept the number of iterations, or set your own value. Often one-half or one-quarter of the suggested number is sufficient for ACP to find the optimal configuration. Resolution (m): Specify the resolution for the optimisation. Each criterion will be evaluated on each of these pixels. The total number of pixels and the average number per site is indicated. This parameter has a large influence on the accuracy and speed of the optimisation process. You should either set a resolution that is consistent with the path loss and raster data in the Atoll document, or you should set a resolution that will result in between 300 and 3000 positions per site.

4. Under Setup, you can set the following optimisation-related objectives and parameters: a. In the pane on the left-hand side, click Layers. Under Layers (see Figure 7.317 on page 588), you can define the following for each layer to be optimised: Note: In UMTS, you can optimise only one carrier per frequency band in an optimisation; therefore, if you have one frequency band with more than one layer, each with a different carrier, you can only select one layer per optimisation. Use: You can select which layers are to be considered in the optimisation process by selecting their check box in the Use column. The signals and interference of the transmitters and sites in the selected layers will be taken into consideration during the optimisation process. If the transmitters and sites in the selected layers are within the area to be optimised (the computation zone or the focus zone, as selected under Zones on the Optimisation tab), these transmitters and cells will be optimised. Selecting layers to be taken into consideration is most useful when you want to take the signal and interference of several layers into consideration, but only want to optimise one of the layers. Selecting the layers here ensures that ACP will take them into consideration. Transmitters and sites in layers which are not selected are treated by 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. Note: If a transmitter on one selected layer that is optimised is linked with a transmitter on another selected layer that is not optimised, the second transmitter will still appear on the Reconfiguration tab and any changes to the first transmitter will be applied to the linked transmitter as well. Name: You can change the name of the layer by clicking it and entering a new name. Weight: You can change the weight assigned to the layer during optimisation by clicking it and entering a new weight. ACP will put more emphasis on increasing the quality of the layer with the greater weight. For example, if one layer has a weight of "2" and another layer has a weight of "1," ACP will consider increasing the quality of the first layer by 1% as equivalent to increasing the quality of the second layer by 2%.

588

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Reconfiguration: If you want the layer to be taken into consideration for reconfiguration, you can select the check box in the Reconfiguration column. Site Selection: If you want the layer to be taken into consideration for site selection, you can select the check box in the Site Selection column.

The following columns give information about the layer; they can not be edited: Technology: The technology (UMTS in this case) used by the layer. Freq. Band/Carrier: The frequency band and carrier (if applicable) used by the layer. Nb Tx/Cell: The number of sectors in the layer.

You can merge layers if you want to define identical objectives for both layers (for more information on objectives, see "Setting Objective Parameters" on page 590). To merge layers: i. Hold CTRL and click the layers you want to merge.

ii. Click the Merge button. b. In the pane on the left-hand side, click Zones. Under Zones (see Figure 7.319), you can define how the zones will be used during optimisation. The zones are used to define geographical objectives and weighting. The zones are taken into consideration in the following order: the hot spot zones in their defined order, the focus zone, and finally the computation zone. Filtering Zones: Select the Computation Zone check box to lock sectors outside the computation zone and the Focus Zone check box to lock sectors outside the focus zone. If there is no focus zone in the project to be optimised, the computation zone is automatically selected. Hot Spots: For each new hot spot, enter a Name in the row marked with the New Row icon ( click the Browse button ( ) and ) to open the Zone Definition dialogue. You can import an ArcView SHP file

by selecting From file and clicking the the Browse button ( ). Or, you can use an existing hot spot zone in the Atoll document by selecting From hot spot and selecting the hot spot zone from the list. Or, you can create a hot spot zone composed of all areas in the reconfiguration zones that are included in one or more clutter class by selecing From clutter classes and selecting the check box corresponding to the clutter class or classes you want to study.

Figure 7.318: The Zone Definition dialogue You can change the order in which the hot spots will be taken into consideration, by clicking the layers number in the Order column and then clicking the Up button ( ) or the Down button ( ).

Figure 7.319: Configuring zones on the Optimisation tab c. In the pane on the left-hand side, click Cost Control.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

589

Atoll User Manual Under Cost Control (see Figure 7.320), you can define how the costs will be calculated for each optimisation option. ACP will use the defined costs to calculate the optimisations that are the most cost-effective. You can select three types of cost control: No cost control: If you select No cost control, ACP will not take cost into consideration when optimising the network. Maximum cost: If you select Maximum cost, you can enter a maximum cost not to be exceeded and define the costs under Cost Setting. Quality/Cost trade-off: If you select Quality/Cost trade-off, ACP will find a compromise between cost and quality. You can use the slider to define whether ACP should put more emphasis on quality (Low) or cost (High).

Figure 7.320: Configuring costs on the Optimisation tab In the Reconfiguration Cost section, under Cost Setting, define the individual costs for each reconfiguration option. If reconfiguring an option can only be done at the physical location of the transmitter, select the check box in the Site Visit column. The cost will be increased by the defined Site Visit value. The site visit cost is incurred only once per site, independently of the number of reconfigurations that might be made to the same site, including sites supporting more than one technology. In the Site Selection Cost section, under Cost Setting, define the individual costs for each site selection option.

7.4.3.2.2

Setting Objective Parameters

The Objectives tab allows you to define the various parameters related to the objectives of the optimisation. ACP allows you to set different objectives for each layer selected in the Use column under Layers on the Optimisation tab. The objectives vary according to the technology used by the network being optimised. The options are given here. To set the objective parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Objectives tab (see Figure 7.321).

590

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.321: The Optimisation tab 3. Under Criteria, you can set the following objective-related objectives and parameters. a. Under Objective, click RSCP Coverage to define the RSCP coverage parameters. Computation zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for RSCP coverage in computation zone. Under Area Coverage, you can define the percentage by which the current RSCP coverage should be improved (Improve current coverage (+-)) or a target RSCP coverage (Target coverage (%)). Focus zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for RSCP coverage in focus zone. Hot Spot zone: Every hot spot zone defined under Zones on the Optimisation tab will appear under RSCP coverage. For each hot spot zone, select the check box in the Use column if you want to define a Minimum threshold (dBm) for RSCP coverage in the hot spot zone.

b. Under Objective, click Parameters under RSCP Coverage to define how ACP will calculate RSCP coverage. From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate RSCP coverage, or you can select Manual Configuration and define the settings yourself. Important: If you want to use a coverage prediction, the coverage prediction must have already been calculated. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own maps. However, if you have saved the display options of an ACP map as default, or if you are using a configuration file for ACP, these defined ranges and colours will be used as the default, overriding the settings in the selected coverage prediction. For information on setting ACP map display options as the default, see "Changing the Display Properties of ACP Maps" on page 623. For information on saving a configuration file, see "Configuring the Default Settings" on page 583. If you selected Manual Configuration from the Base prediction settings on list, define the following options: Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell edge coverage probability. When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Macro diversity is also taken into account during RSCP calculation. Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied. You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced Parameters" on page 608.

c. Under Objective, click EcIo Coverage to define the EcIo coverage parameters. Computation zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for EcIo coverage in the computation zone. Under Area Coverage, you can define the percentage by which the current EcIo coverage should be improved (Improve current coverage (+-)) or a target EcIo coverage (Target coverage (%)).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

591

Atoll User Manual Focus zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for EcIo coverage in the focus zone. Hot Spot zone: Every hot spot zone defined under Zones on the Optimisation tab will appear under EcIo Coverage. For each hot spot zone, select the check box in the Use column if you want to define a Minimum threshold (dBm) for EcIo coverage in the hot spot zone.

d. Under Objective, click Parameters under EcIo Coverage to define how ACP will calculate EcIo coverage. From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate EcIo coverage, or you can select Manual Configuration and define the settings yourself. Important: If you want to use a coverage prediction, the coverage prediction must have already been calculated. If you selected Manual Configuration from the Base prediction settings on list, define the following options: Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell edge coverage probability. When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Macro diversity is also taken into account during EcIo calculation. Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied. You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced Parameters" on page 608. Select a Service and a Terminal. The service and terminal specified are 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 terminal noise factor).

e. Under Criteria, click Weighting to set the importance of the objectives (see Figure 7.322). The network quality is improved by reducing interference. You can define the importance of reducing interference, and thereby of improving network quality, under Weighting.

Figure 7.322: Setting weighting options for UMTS i. Under Objective Weighting, move the slider to set the relative importance of EcIo and RSCP coverage. You can set meeting one objective as more important than meeting the other, or you can set meeting only the EcIo or RSCP objective as necessary.

ii. Under Perform interference minimization, move the slider to set the importance of reducing interference and thereby improving network quality. iii. Under Zone weighting, define the weight given to the computation zone, the focus zone, and any hot spot zone. With zone weighting, ACP adds an extra weight to all the pixels of a zone. Because one pixel can belong to several zones (for example, a pixel can be inside both the focus zone and the computation zone and in a hot spot zone, if there is one), the weight applied to that pixel is the weight of the zone with the highest priority: the hot spot zone, if it exists, then the focus zone, finally the computation zone.

592

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks Important: It is important to remember that, if every zone is assigned the same weight, the optimisation is made as if no weight is assigned to any zone. Defining a weight of "0" for a zone means that that zone will not be taken into consideration when trying to reach the set objectives. Zone weighting is used to focus optimisation on the appropriate areas. The assigned weights are used to weight the traffic parameters selected on the Traffic tab, unless the optimisation is based on uniform traffic. For information on the selected traffic parameters, see "Setting Traffic Parameters for Non-uniform Traffic" on page 593. However, if no traffic maps are available or if the optimisation is based on uniform traffic, zone weighting can be used to ensure that ACP prioritises the optimisation of areas of high traffic. With multiple layers, you might have a layer that is restricted geographically (for example, the UMTS 900 layer might only be available in rural areas). Because ACP always measures the quality target over the entire computation zone, such a situation would lead to a measurement of poor quality in the urban areas, where there are no UMTS 900 sectors. By defining a weight of "0" outside of the rural area for this layer, you can restrict the measurement of coverage only to the part of the layer with UMTS 900 sectors. This way, the global target (90% of coverage for instance) is measured in a meaningful way. iv. Under Objective, click Miscellaneous to define the overlap threshold margin. Enter an Overlap threshold margin. It will be used for traffic maps.

7.4.3.2.3

Setting Traffic Parameters for Non-uniform Traffic

By default, the traffic is assumed to be uniform within the computation zone. The Traffic tab enables you to select traffic maps in the Atoll document to define non-uniform traffic. The traffic maps describe the distribution of users in the network, along with their characteristics (i.e., services, terminals, and mobility types). Traffic maps can used to weight the quality figures measured on each pixel by using the traffic density on that pixel. You can use traffic maps to weight quality figures. For example, you can optimise RSCP coverage based only on area (defined on the Optimisation tab as explained in "Setting Optimisation Parameters" on page 587) while optimising EcIo coverage using traffic distribution. When using traffic maps, network quality is always optimised using traffic weighting. ACP supports all traffic maps used by Atoll. To set the traffic parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Traffic tab (see Figure 7.323).

Figure 7.323: Defining non-uniform traffic using the Traffic tab 3. Under Traffic Generated From, select one of the following methods for defining non-uniform traffic: Maps based on traffic densities: If you select Maps based on traffic densities, you can define the traffic weighting and traffic profiles.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

593

Atoll User Manual Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of EcIo or RSCP coverage or both. The weighting applied is the weighting defined on the Objectives tab. Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Terminal, select a Traffic Density File by clicking the Browse button ( ), and define a Weight.

Following traffic maps: If you select Following traffic maps, you can select the maps that will be used to generate traffic and define the resolution of the extracted traffic and the traffic weighting. Under Following traffic maps, select the maps that will be used to generate traffic. Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of EcIo or RSCP coverage or both. Under Traffic Profiles, the traffic profiles will be displayed after ACP has extracted them from the selected traffic maps.

4. If you want to view the traffic profiles without running the optimisation setup, click Create Setup. ACP will then create the traffic profiles based on the traffic maps selected and the traffic parameters defined.

7.4.3.2.4

Setting Network Reconfiguration Parameters

The Reconfiguration tab allows you to select the UMTS cells for which the pilot power will be reconfigured and the transmitters for which the antenna, azimuth, height, or tilt will be reconfigured. The Reconfiguration tab also allows you to select which sites can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly select sites for reconfiguration. For information on site selection, see "Defining Site Selection Parameters" on page 600. Atoll allows you to export the reconfiguration parameters, modify them in an external application and then reimport them into the Reconfiguration tab. In this section, the following are explained: "Setting UMTS Cell Reconfiguration Parameters" on page 594 "Setting Transmitter Reconfiguration Parameters" on page 595 "Linking Transmitters in Multi-layer Networks" on page 597 "Using Precalculated Path Loss Matrices to Calculate Path Loss Attenuation" on page 598 "Importing Network Reconfiguration Parameters" on page 599.

Setting UMTS Cell Reconfiguration Parameters

To set the UMTS cell reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the UMTS Cells tab (see Figure 7.325).

Figure 7.324: UMTS cell reconfiguration options 3. Select the Pilot power check box for the pilot power of each selected cell to be set within a defined minimum and maximum value and in the defined number of steps. 4. Select the Synchronise cell power on co-sector cells check box to ensure that all cells on the same sector are assigned the same cell power.

594

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Important: 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. 5. Define the pilot power settings for each cell. Use: Select the Use check box corresponding to the cell to include it in the optimisation of the pilot power. Current: The current pilot power for the cell. Min. and Max.: Set a minimum and maximum pilot power to be respected during the optimisation process. Note: If you selected the Power max/min as offset check box, you will set the Min. Offset and Max. Offset for each cell.

Step (dB): Set a Step in dB that ACP should use with attempting to find the optimal pilot power. Note: For pilot power optimisation, the pilot range is defined with minimum, maximum, and step values. Independently of the maximum defined on the UMTS Cells tab, there is an absolute maximum possible pilot power which depends on the other powers used in the cell (for control, traffic, and maximum cell power).

You can make the same changes to several cells by making the change for one item, selecting the others starting from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 59. You can select the cells to which the reconfiguration options are going to be applied using the Advanced section of the Reconfiguration tab. For more information, see "Selecting Sites for Reconfiguration" on page 603. You can sort the contents of any column by right-clicking the column and selecting Sort Ascending or Sort Descending from the context menu. Caution: Cells that have been filtered out, either by zone or by clearing their check box in the table, will not be optimised but are still present in the network and, therefore, continue to generate interference.

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. For information on importing network reconfiguration options, see "Importing Network Reconfiguration Parameters" on page 599.

Setting Transmitter Reconfiguration Parameters

To set the transmitter reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Reconfiguration tab (see Figure 7.325).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

595

Atoll User Manual

Figure 7.325: Transmitter reconfiguration options 3. Select the parameters that will be optimised: Antenna type: Select the Antenna type check box for ACP to adjust the antenna type by selecting the best antenna from the antenna group assigned to each selected transmitter. Electrical tilt: Select the Electrical tilt check box for ACP to select the best electrical tilt from the antenna group assigned to each selected transmitter within the defined range. Note: When ACP selects the best antenna type, it will also chose the best electrical tilt from the antenna group even if it is not optimising the electrical tilt. However, because no range is defined, ACP will select the best electrical tilt from all available.

Azimuth: Select the Azimuth check box for ACP to set the antenna azimuth using a defined range on either side of the currently defined azimuth. Note: By default, ACP optimises the antenna azimuth of each sector of a site individually. However, you might want to retain the same inter-sector angle separation. If this is the case, you can select the Azimuth check box corresponding to that site under Lock Site on the Sites tab of the Reconfiguration tab.

Mechanical tilt: Select the Mechanical tilt check box for ACP to set the mechanical tilt within the defined range and in the defined number of steps. Height: Select the Height check box for ACP to set the antenna height within the defined range and in the defined number of steps. Note: By default, ACP optimises the height of all antennas of a site identically. In other words, if ACP optimises the antenna of one sector by raising it 1 m., it will also raise the antennas of all other sectors by the same amount, in order to respect the distance between all antennas on the transmitter mast. However, in might not be necessary to maintain this distance, in which case you might want to optimise the height of each antenna of a site individually. f this is the case, you can clear the Height check box corresponding to that site under Lock Site on the Sites tab of the Reconfiguration tab.

The table displays, for each parameter selected, both the current settings for each cell in the selected zone and the currently defined optimisation parameters.

596

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Note:

If you want ACP to display more information on each transmitter, you can select the Show Advanced Grid check box. ACP will then display, for each transmitter, the antenna masking method, the propagation model used, the transmitter height, and the name and status of the site the transmitter is located on. The propagation model displayed is extracted from the Atoll document but can be changed if the propagation model is not recognised by ACP (for more information, see "ACP and Antenna Masking" on page 581).

4. Define the settings to be optimised for each cell. If are optimising the antenna azimuth, you can enter a single value in the Variation column, to define a range on either side of the current azimuth, or you can enter a minimum and maximum value separated by a semi-colon in the format "-min;max", (for example, "-20;40") in the Variation column for an asymmetric antenna. You can make the same changes to several cells by making the change for one item, selecting the others starting from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 59.

Linking Transmitters in Multi-layer Networks

When you are optimising transmitters in multi-layer environments, ACP automatically links transmitters in the same location but in different layers to ensure that it applies the same reconfiguration to them. ACP links them not only by location, but also by azimuth, mechanical tilt, and antenna height. If ACP does not automatically link two transmitters which should be linked, it is normally because there is too large a difference in one of the parameters of the two transmitters, for example, a few degrees in azimuth, one degree in mechanical tilt, or one meter difference in antenna height. If two transmitters should be linked but were not, you can manually link them. Note: If the site of one of the linked transmitters has either its antenna heights or azimuths locked, i.e., if changes made to one sector of the site are made to all sectors on that site, then corresponding changes will be made to the other linked transmitter. For more information on locking antenna heights or azimuths, see "Setting Transmitter Reconfiguration Parameters" on page 595.

To link transmitters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the Transmitters tab. 3. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear. 4. Under Advanced, click the Multi-layer Management tab. On the Multi-layer Management tab, you can link transmitters (see Figure 7.326).

Figure 7.326: Multi-layer management

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

597

Atoll User Manual To link transmitters in the same location but on different layers: a. Hold CTRL and click the first transmitter in the table above and then the second transmitter. The Link button on the Multi-layer Management tab is now available. b. Click the Link button. The two transmitters are now linked and ACP will apply the same reconfiguration to them both. To unlink linked transmitters: a. Select the transmitters in the table The Unlink button on the Multi-layer Management tab is now available. b. Click the Unlink button. The transmitters are no longer linked. To unlink all linked transmitters: Click the Unlink All button. ACP resets all linked transmitters.

To automatically all transmitters in the same location but on different layers: Click the Auto Link button. ACP links all transmitters that have the same position, azimuth and mechanical tilt.

Using Precalculated Path Loss Matrices to Calculate Path Loss Attenuation

You can define how Atoll ACP calculates path loss matrices, using either Atolls propagation models, ACPs internal propagation model, or precalculated path loss matrices. These parameters will be applied to all new and duplicated setups. To define how ACP calculates path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Reconfiguration tab (see Figure 7.325). 3. If you are using a propagation model that ACP does not natively support, select the Enable precalculated path loss matrices check box. You will then be able to select the propagation model for which ACP will pre-calculate path attentuation. 4. Under Propagation Models, select the check boxes in each column to define how ACP will interact with that propagation model. Not all parameters are available for all propagation models:

Tip:

By default, all available propagation models are displayed. By selecting the Show only used propagation models check box, ACP will only display the propagation models that are actually used.

Antenna masking method: The Antenna masking method indicates whether ACP can use this propagation model natively, or whether ACP uses its own default method. The information in this column can not be edited. Use precalculated path loss: Select the check box in the Use precalculated path loss column corresponding to every propagation model that is not supported natively by ACP or that can not be replaced using ACPs internal default method. Use clutter height: Select the check box in the Use clutter height column if you want ACP to take clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on top of clutter: Select the check box in the Receiver on top of clutter column if you want the receiver height to be sum of the clutter height and the receiver height. This option can be used, for example, to model receivers on top of buildings. Use radial method: Select the check box in the Use radial method column if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

5. Click OK. Important: When you use precalculated path loss matrices, they must be stored externally. For information on storing path loss matrices externally, see "Setting the Storage Location of Path Loss Matrices" on page 171. 6. In the table on the Reconfiguration tab, select the check box in the Precalculated Path Loss Matrices column for each entry in the Tx Name column that uses a propagation model that is not natively supported by ACP (see Figure 7.327).

598

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.327: Using precalculated path loss matrices

Importing Network Reconfiguration Parameters

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. To import reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the desired tab. 3. Right-click the table and select Export as Text from the context menu. The Save As dialogue appears. 4. Enter a name in the File name box and click Save. The file will be saved as a tab-delimited text file. 5. Open the text file in another application, for example, in a spreadsheet application, and make the modifications desired. 6. Save the file as a text file and return to Atoll. 7. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear. 8. Under Advanced, click the Import Facility tab. 9. Click the Import from File button. The Open dialogue appears. 10. Browse to the file and click Open. The Import Data dialogue appears (see Figure 7.328).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

599

Atoll User Manual

Figure 7.328: Importing site data into the Reconfiguration tab 11. Under Format Parameters, enter the number of the first row with data in the First Imported Row box, select the data Separator, and select the Decimal Symbol used in the file. 12. If you want only the cells in the imported list to be used on the Reconfiguration tab, select the Use Only Cells in List check box. The Use check box will be cleared for all cells that are not in the imported file and they will not be affected by reconfiguration options. 13. In the table, ensure that the column names from the imported file (the Source file) match the column names on the Reconfiguration tab (Destination). You can change the Destination column by clicking the column name and selecting the name from the list. Note: Any values in the imported file for current values can not be imported.

14. Click the Import button to import the file and replace the settings in the Reconfiguration tab.

7.4.3.3

Defining Site Selection Parameters

The Reconfiguration tab allows you to select which sites can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly select sites for reconfiguration. In this section, the following are explained: "Selecting Sites for Addition or Removal" on page 600 "Creating Candidate Sites" on page 602 "Selecting Sites for Reconfiguration" on page 603.

Selecting Sites for Addition or Removal

You can use the Reconfiguration tab to select the sites that will be added or removed to improve existing or new networks. To set site selection parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab (see Figure 7.329).

600

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.329: Site selection 3. Select the Current Site Selection check box to enable site selection. You can then define how sites will be added or removed. 4. In the table, define how each site will be treated during site selection: a. Select the Locked check box for each site that is not to be affected by site selection.

Tip:

If you have many sites that you do not want to be affected by site selection, you can select and lock them with the Advanced section. For more information on the options in the Advanced section, see "Selecting Sites for Reconfiguration" on page 603.

b. Select the Status for each site that is not locked: Important: Only active sites are loaded by ACP. If you want inactive sites to be taken into account during site selection, you must set them as active first in Atoll. When you commit the results of the ACP run, all sites and sectors disabled by the ACP will be set to inactive in Atoll. Existing: An "Existing" site is considered as being active in the initial network. ACP will remove an existing site if the Site Removable check box has been checked and if removing the site will improve network quality. If the Sectors Removable check box has been checked, one or more sectors might be removed if removing them will improve network quality. Candidate: A "Candidate" site is considered as being inactive in the initial network. ACP will add the site during the optimisation process if adding the site will improve network quality. If the Sectors Removable check box has been checked, only one or more sectors might be added if adding them will improve network quality. You can define candidate sites by clicking the New Candidate Setup button. For more information on defining candidate sites, see "Creating Candidate Sites" on page 602. c. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality. d. Select the Site Removable check box for each site that can be removed to improve network quality. e. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group. Note: i. If a site group has no sites belonging to it, it is automatically deleted. Under Group, click the field and select New from the list. The New Site Group dialogue appears (see Figure 7.330).

ii. Enter a Group Name and define the minimum and maximum number of sites from this group (from 0 to 1000) that must be respected by ACP during optimisation (Minimum Site Occurrence and Maximum

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

601

Atoll User Manual Site Occurrence, respectively). If there is no minimum or maximum that ACP must respect, leave the field blank. iii. Click OK to create the group and return to the Site Selection tab.

Figure 7.330: Creating a new site group f. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality.

g. Select the Site Removable check box for each site that can be removed to improve network quality. h. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group. Note: If a site group has no sites belonging to it, it is automatically deleted.

Creating Candidate Sites

The ACP enables you to create a list of candidate sites that can be added to the network to improve quality. For each candidate, you can specify both the location and the station template the candidate site would be based on if the ACP adds it to the network. As well, the ACP can optimise candidate sites when they are added to the network. During optimisation, the ACP will choose first from the sites defined as candidates on the Sites tab and then from the list of candidate sites. To create or edit candidate sites: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab. 3. On the Sites tab, click the New Candidate Sites button. The New Candidate Sites dialogue appears (see Figure 7.331).

Figure 7.331: New Candidate Setup dialogue 4. Under Zone Configuration, define, if desired, how candidate sites will be treated for each zone: Zone: Select the zone (computation, focus, or hot spot zone defined on the Optimisation tab) from the list. The ACP will add the candidate site according to the quality objectives defined on the Optimisation tab. Default Station Template: Select the station template that any candidate site the ACP adds in the selected zone will be based on.

602

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Note:

The ACP can optimise each candidate site based on a template. You can set the optimisation parameters for each template by clicking the Template Reconfiguration button. For information on the options, see "Setting Transmitter Reconfiguration Parameters" on page 595.

Default Group: Select the group that the candidate site will belong to by default. Radio Layer: If there is more than one radio layer, select the radio layer the candidate site will be added to.

5. Under New Candidate List, define the individual candidate sites. For each candidate site set the following: Name: Enter a name for the candidate site. Location: Click the Browse button ( ) to define the location of the candidate site. You can define the location either as a set of co-ordinates or you can select an existing site from a list. Station Template: Select the station template the candidate site will be based on. This selection overrides the selection made under Zone Configuration. Group: Select the group the candidate site will belong to. This selection overrides the selection made under Zone Configuration. Height: The 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 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. Radio Layer: Select the radio layer the candidate site will be added to. This selection overrides the selection made under Zone Configuration.

6. If desired, select the Try to use multi-band antenna when possible check box. The ACP will attempt to use linked transmitters on candidate sites if possible. 7. Click the Action button to update the list of new candidates by selecting one of the following options: Clear List: Select Clear List to delete all current entries in the New Candidate List. Import from File: Select Import from File to import a list of candidate sites, defined as XY coordinates. Import from Current Sites Defined as Location Only: Select Import from Current Sites Defined as Location Only to import as candidate sites sites in the current document that have no transmitters. The sites imported are those in the reconfiguration zone(s) selected on the Optimisation tab. The defined reconfiguration zone(s) is displayed at the top of the Reconfiguration tab as well. Update Candidate Height from Clutter Height: Select Update Candidate Height from Clutter Height to define the height of all candidate sites for each clutter class.

Selecting Sites for Reconfiguration

You can use the Advanced area of the Reconfiguration tab to select sites. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on page 594. To select sites: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab. 3. Select the Site Selection check box. 4. Click Advanced to display the Advanced area (see Figure 7.332).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

603

Atoll User Manual

Figure 7.332: The Advanced section 5. Select the Global Change tab. 6. Select the sites: For entire table: Select For entire table if you want to select all sites in the table. 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 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. Note: This option is only available in co-planning projects with more than one technology.

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. Note: If you want to lock the selected sites, you can select the Set "Locked" check box and click Apply. The locked sites will not be affected by the site addition or removal options.

7.4.3.3.1

Defining Antenna Groups

You can use the Antenna tab to define antenna groups according to their physical characteristics, as well as grouping patterns according to their antenna pattern and defining multi-band antennas. The antenna groups are necessary to apply the antenna type or electrical tilt reconfiguration options defined on the Reconfiguration tab. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on page 594. 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. In this section, the following are explained: "Creating and Grouping Antennas by Pattern" on page 605 "Grouping Antennas Automatically" on page 606 "Defining Multi-band Antennas" on page 606 "Creating Antenna Groups" on page 607.

604

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Creating and Grouping Antennas by Pattern

Atoll enables you to create physical antennas by grouping several instances of antennas by their pattern. By setting an option in the ACP.ini file, you can also optimise the additional electrical downtilt (AEDT) of antennas. When you have set this option, you can select which antennas for which you will optimise the AEDT and the range of values that Atoll can chose from during the optimisation process. For information on setting options in the ACP.ini file, see the Administrator Manual. To group antennas by their pattern: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 7.333). The Antenna tab displays all antennas in the Antenna Pattern Table and the groups under Physical Antenna.

Figure 7.333: Antenna tab 3. Click the New button to create a new group under Physical Antenna. You can change the name of the new group or of any group by right-clicking the group name twice under Physical Antenna, selecting Rename from the context menu, and entering the new name. You can delete one group by selecting it under Physical Antenna and clicking the Delete button. You can delete all groups by clicking the Delete All button. 4. Assign antennas to a group to create physical antennas or to associate antenna patterns to define a radiation diagramme of a group of antennas with several variations of electrical tilt: a. Select the group under Physical Antenna. b. Select the antenna under Antenna Pattern Table and click the right arrow between the columns ( ) to assign it to the selected group. Antennas under Antenna Pattern Table that have been assigned to a group are indicated with an icon ( ). You can assign the same antenna to more than one group. You can remove an antenna from a group by selecting it in the group under Physical Antenna and clicking the left arrow between the columns ( Note: ).

When you have grouped the antennas, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antennas will then be grouped automatically according to this definition.

5. If you are also optimising additional electrical downtilt, select the check box in the Use AEDT column corresponding to each antenna for which you want to optimise the additional electrical downtilt and define the limits Atoll must respect by entering values in the Min. AEDT and Max. AEDT for each antenna to be optimised.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

605

Atoll User Manual

Figure 7.334: The Antenna Pattern Table with AEDT enabled

Grouping Antennas Automatically

You can group antennas automatically using a regular expression, or "regex." The regular expression is retained from one Atoll session to the next. Therefore, once you have set the regular expression for the given antenna naming convention, you will not have to set again for the next Atoll session. The default regex pattern is overwritten when you change it. You can return to the default regular expression by clearing the text box and clicking OK. You can change the default regular expression by editing the appropriate entry in the ACP.ini file. For more information on the options available in the ACP.ini file, see the Administrator Manual. Important: It is recommended to identify both the antenna type and the electrical tilt in the antenna name in Atoll and to separate the antenna type and electrical tilt with a special character, for example, "_". This will make it easier to group antenna groups automatically using a regular expression. To group antenna automatically: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 7.333 on page 605). 3. Under Automatic Creation, enter a regular expression, or "regex," in the text box.

Tip:

Clicking the tooltip button ( expressions.

) displays a tooltip with an explanation of common regular

4. Click the Build from expression button to create antenna groups according to the defined regular expression. Note: When you have created the antenna groups, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antenna groups are then automatically created according to this definition.

Defining Multi-band Antennas

When you have grouped antennas according to their physical characteristics as explained in "Creating and Grouping Antennas by Pattern" on page 605 and "Grouping Antennas Automatically" on page 606, they are displayed on the Radome tab of the Antenna tab, grouped according to their frequency band. You can merge these groups to create groups of antennas that are multi-band antennas. To define multi-band antennas: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Radome tab (see Figure 7.333 on page 605).

606

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.335: Creating multi-band antennas 3. Create multi-band antennas by merging two or more antenna groups: a. Select two or more antenna groups by holding CTRL and clicking the antenna groups in the Radome Table. b. Click the Merge button. The antenna groups are now merged and will appear on the Antenna Groups tab. You can break the merged antenna groups up by selecting them in the Radome Table and clicking the Unmerge button, or by clicking Unmerge All. If you click Unmerge All, all merged antenna groups will be broken up. 4. Under Automatic Creation, enter a regular expression, or "regex," in the text box.

Creating Antenna Groups

ACP creates antenna groups based on common their frequency band, but you can create antenna groups based on other common characteristics. The antenna groups are used especially to chose between a directive antenna (of 35 degrees) and a less directive one (of 65 degrees). However, in most circumstances, one antenna group corresponds to one antenna radome. To group antennas: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Antenna Groups tab (see Figure 7.336 on page 608). On the Antenna Groups tab, there is already one group called "Default" in the Antenna Groups pane of the tab. The "Default" group is created automatically by ACP and contains all the antenna patterns available for a given frequency.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

607

Atoll User Manual

Figure 7.336: Creating antenna groups 3. Click the New button to create a new group under Antenna Groups. You can change the name of the new group or of any group by right-clicking the group name twice under Antenna Groups, selecting Rename from the context menu, and entering the new name. You can delete one group by selecting it under Antenna Groups and clicking the Delete button. You can delete all groups by clicking the Delete All button. 4. Assign antennas to groups according to their physical characteristics: a. Select the group under Antenna Groups. b. Select the antenna under Radome Table and click the right arrow between the columns ( ) to assign it to the selected group. Antennas under Radome Table that have been assigned to a group are indicated with an icon ( ). You can assign the same antenna to more than one group. You can remove an antenna from a group by selecting it in the group under Antenna Groups and clicking the left arrow between the columns ( Note: ).

When you have created the antenna groups, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antenna groups are then automatically created according to this definition.

7.4.3.3.2

Adding Comments to the Optimisation Setup

You can enter comments about the current optimisation setup on the Comments tab. To add comments: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Comments tab and add your comments.

7.4.3.3.3

Setting Advanced Parameters

The Advanced tab displays the traffic parameters that ACP uses to optimise the Atoll project. You can use the Advanced tab to modify this Atoll data. The Advanced tab is not displayed by default. For information on displaying the advanced parameters, see "Configuring the Default Settings" on page 583. To set advanced parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 586. 2. Click the Advanced tab. 3. In the left column, click the Expand button ( ) to expand the Parameters folder. 4. In the Parameters folder, select Services. In the Services section, the service-related parameters of the Atoll document are displayed.

608

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 5. Under Services, define the body loss for each of the services defined in the Atoll document. 6. In the Parameters folder, select Terminals. In the Terminals section, the terminal-related parameters of the Atoll document are displayed. In a co-planning document, there will be a Terminals folder for each technology. 7. Under Terminals, define the Antenna Gain, the Loss, and the Noise Factor for each terminal. 8. In the Parameters folder, select Clutter Classes. In the Clutter Classes section, the clutter-related parameters of the Atoll document that affect optimisation are displayed. 9. Under Clutter Classes, you can set the following parameters for each clutter class: Height: You can set the Height for each clutter class. Indoor Loss (dB): You can set the Indoor Loss (dB) for each clutter class. The indoor loss is used to calculate shadowing losses on the path loss, as related to the cell edge coverage probability. % Pilot Finger: You can set the % Pilot Finger for each clutter class. The percentage of the pilot finger is used in the Ec/Io calculations. Model Standard Deviation (dB): You can set the Model Standard Deviation (dB) for each clutter class. The model standard deviation is used to calculate shadowing losses on the path loss, as related to the cell edge coverage probability. Ec/Io Standard Deviation (dB): You can set the Ec/Io Standard Deviation (dB) for each clutter class. The EcIo standard deviation is used to calculate shadowing losses on the EcIo values, as related to the cell edge coverage probability. Is Indoor: You can define the clutter class as being inside by selecting the Is Indoor check box. You can set default values for all clutter classes for each of these parameters except for height.

Note:

7.4.4

Running an Optimisation Setup

When you have finished defining the optimisation parameters as described in "Defining Optimisation Parameters" on page 587, you can run the optimisation setup, either immediately by clicking the Run button. You can also save the defined optimisation setup by clicking the Create Setup button and then running the optimisation at a later point. To run a saved optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 3. Right-click the setup folder that you want to run in the ACP - Automatic Cell Planning folder. The context menu appears. 4. Select Run from the context menu. The optimisation setup runs. As the optimisation setup runs, ACP displays the current status of the process (see Figure 7.337) allowing you to observe the progress. You can pause the optimisation if you desire or stop the optimisation early, The Optimisation dialogue has two tabs: Graphs: The Graphs tab displays a graph with the iterations on the X axis and the optimisation objectives (RSCP, EcIo, network quality, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 7.337). The values displayed are indicated with a legend. Quality Maps: The Quality Maps tab displays coverage quality maps for RSCP (Ec) and EcIo improvement. The maps display the computation zone with the network improvement performed to that point. If you based this optimisation on a coverage prediction (see "Setting Objective Parameters" on page 590), the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default (see "Changing the Display Properties of ACP Maps" on page 623) or by using a configuration file (see "Configuring the Default Settings" on page 583).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

609

Atoll User Manual

Figure 7.337: The network coverage improvement graphs and maps When the optimisation has finished, the results are stored in the optimisation folder on the Data tab of the Explorer window. By default, Atoll calls the optimisation folder a "Setup" folder. Each setup folder contains one or more optimisation processes. Each optimisation process folder contains the results of that optimisation. For information on viewing optimisation results, see "Viewing Optimisation Results" on page 611.

Figure 7.338: An optimisation run in the Explorer window Note: You can perform an optimisation on a network that has already been optimised. After running the first optimisation and committing the results, you can create and run a second optimisation, with different parameters on the optimised network.

7.4.5

Working with Optimisations in the Explorer Window

Atoll offers you several options for working with the optimisation that you can access using the context menu on the Data tab of the Explorer window. To work with the optimisation: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 7.339).

610

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.339: Options available in the context menu 5. Select one of the following from the context menu: Properties: Selecting Properties from the context menu opens the optimisations Properties dialogue. You can modify all of the optimisation parameters except for the selection of traffic maps (for information on the optimisation parameters, see "Defining Optimisation Parameters" on page 587). If you want to base an optimisation on different traffic maps, you must create a new optimisation (for information on creating a new optimisation, see "Creating an Optimisation Setup" on page 586). Run: Selecting Run runs the optimisation setup. The results will be contained in a new optimisation folder in the setup folder. Caution: If you have changed some data in Atoll, for example, if you added transmitters or change some of the transmitter settings, the data that optimisation results are based on may differ from the current Atoll data. If you run a optimisation based on settings made before the changes, it will not take the changed data into consideration. ACP normally detects changes in the Atoll document data and can lock a group if it is impossible to run an optimisation that is coherent with existing data. ACP can lock a group if, for example, when you commit optimisation results after the path losses have been recalculated and are no longer consistent with the data used to run the optimisation. When this happens you will either have to: Create a new optimisation as explained in "Creating a New Optimisation Setup" on page 586. Duplicate an existing optimisation which will create a new optimisation with the same configuration but with updated parameters. Roll back the previously committed parameters as explained in "The Commit Tab" on page 618.

Delete: Selecting Delete deletes the defined optimisation setup and any results. Storing optimisation results and the group configuration increase the size of the Atoll file. Deleting unused setups in the ACP - Automatic Cell Planning folder will decrease the size of the Atoll file.

Load Configuration: Selecting Load Configuration displays the Open dialogue. You can then select a PRJ file based on the settings of a different optimisation. When you load a configuration based on a different Atoll document, only the settings that are not specific to that document are loaded. Save Configuration: Selecting Save Configuration displays the Save As dialogue. You can then save the optimisation settings in a PRJ file. You can then use this PRJ file to quickly configure an optimisation.

Tip:

Saving a configuration is a quick way to save the settings you have made in an external file. you can then easily create new configurations using these same settings as a basis without having to recreate them.

Duplicate: Selecting Duplicate displays the ACP Duplicate Options dialogue. You can then duplicate the either the ACP-generated data of selected optimisation setup or all of the data of the setup. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid.

7.4.6

Viewing Optimisation Results

Once you have run the calibrated optimisation as explained in "Running an Optimisation Setup" on page 609, the results are stored in the optimisation folder on the Data tab of the Explorer window. You can view the results in the optimisations Properties dialogue or in the map window. In this section, the following are explained: "Viewing Optimisation Results in the Properties Dialogue" on page 612 "Viewing Optimisation Results in the Map Window" on page 618 "Viewing Optimisation Results Using the Histogram" on page 624.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

611

Atoll User Manual

7.4.6.1

Viewing Optimisation Results in the Properties Dialogue

You can view the results of the optimisation run in its Properties dialogue in the ACP - Automatic Cell Planning folder. To view the results of the optimisation in its Properties dialogue: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view.

4. Right-click the optimisation. The context menu appears. 5. Select Properties from the context menu. The optimisations Properties dialogue appears. The optimisation results are on individual tabs of the Properties dialogue (with an extra tab, the General tab, that allows you to change the name of the optimisation results): Statistics: The Statistics tab displays a synthesised view of the optimisation results of the quality figures (RSCP quality, EcIo quality, and network quality). For more information on the Statistics tab, see "The Statistics Tab" on page 612. Sectors: The Sectors tab displays a table with the reconfigured cells in green, sites and sectors which have been added or removed, and the RSCP and EcIo coverage quality per cell before and after optimisation. For more information on the Statistics tab, see "The Sectors Tab" on page 613. Graph: The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (RSCP quality, EcIo quality, network quality, and global cost, if you have selected to take cost into consideration) on the Y axis. The values displayed are indicated with a legend. For more information on the Graph tab, see "The Graph Tab" on page 615. Quality: The Quality tab displays the computation zone with coverage quality maps for RSCP (Ec) and EcIo before and after optimisation. For more information on the Quality tab, see "The Quality Tab" on page 616. Change Details: The Change Details tab enables you to analyse the improvement caused by each reconfiguration option. For more information on the Change Details tab, see "The Change Details Tab" on page 617. Commit: The Commit tab enables you to commit the set of selected changes. For more information on the Commit tab, see "The Commit Tab" on page 618.

7.4.6.1.1

The Statistics Tab

The Statistics tab displays a synthesized view of the optimisation results of the quality figures (RSCP quality, EcIo quality, and network quality).

Figure 7.340: The Statistics tab For the RSCP and EcIo coverage quality, both the initial and final figures are given, as well as the absolute improvement. These figures are given both for the computation zone and the focus zone. If you defined weights for each zone on the Objectives tab of the dialogue used to define the optimisation (see "Setting Objective Parameters" on page 590), ACP indicates that the results are weighted.

612

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks For the network quality, the relative improvement is given. This improvement measures the overall decrease of interference in the network, which can be loosely equated to the overall capacity increase in the network. You can see more detailed information by clicking the links (see Figure 7.341): Show Change Statistics: The change statistics showing the reconfiguration and site selection statistics. Show Detailed Hot Spot/Clutter Results: The detailed quality figures on each hot spot and by each clutter class. Show Input: The input settings of this optimisation.

Figure 7.341: The Statistics tab - detailed information You can export the results by clicking the Export button. The Save As dialogue that appears allows you to select the format in which you want to save the results: XLS, TXT, HTML, or XML.

7.4.6.1.2

The Sectors Tab

The Sectors tab displays a table with all the cells in the network with the following information: Cells which have been reconfigured are displayed in green (i.e., if they have had their antenna type, azimuth, mechanical tilt, or pilot power reconfigured). Sites and sectors which have been added or removed. The RSCP and EcIo coverage quality per cell before and after optimisation. The quality figures are measured on the best server area of each cell. Antenna type, height, azimuth, mechanical tilt, and pilot power initial and final values for each cell.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

613

Atoll User Manual

Figure 7.342: The Sectors tab The cell results are displayed in a table. You can access options such as sorting, exporting data using the context menu (see Figure 7.343) sort, column hiding, export, etc.

Figure 7.343: Options available for data in the Sectors tab

614

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

7.4.6.1.3

The Graph Tab

The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (RSCP quality, EcIo quality, network quality, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 7.344). The values displayed are indicated with a legend.

Figure 7.344: The Graph tab The tool bar allows you to: Zoom and span the graph Export to a BMP image file or simple text file Print the graph Show the values along the curves.

Figure 7.345: The Graph tab with the values displayed on the selected point

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

615

Atoll User Manual

7.4.6.1.4

The Quality Tab

The Quality tab displays the computation zone with coverage quality maps for RSCP (Ec) and EcIo before and after optimisation. You can define the area displayed in the coverage quality maps by selecting the zone (computation, focus, or hot spot) from the list above the maps.

Figure 7.346: Coverage maps on the Quality tab The maps are displayed with a range of values displayed on the right. If you based this optimisation on a coverage prediction (see "Setting Objective Parameters" on page 590), the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default (see "Changing the Display Properties of ACP Maps" on page 623) or by using a configuration file (see "Configuring the Default Settings" on page 583). This range can be modified using the Map Properties dialogue accessed through the tool bar (see Figure 7.347).

Figure 7.347: Defining the display properties of the coverage maps In addition to the map, a histogram is provided for quick evaluation of the improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the Generate Report tool in Atoll which only uses uniform weighting. Note: The default colour range used for display can be changed using the acp.ini preference configuration file. For information on the acp.ini file options, see the Administrator Manual.

616

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

7.4.6.1.5

The Change Details Tab

In addition of the map, a histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the Generate Report tool in Atoll which only uses uniform weighting. Note: The default colour range used for display can be changed using the acp.ini preference configuration file. For information on the acp.ini file options, see the Administrator Manual.

Figure 7.348: The Change Details tab You can select a subset of all changes using a slider and view the corresponding performance improvement on the graph. This can enable you to achieve two goals: To select a subset of changes to be implemented. For example, you might find that implementing only one-third of the recommended changes will provide 80% of the benefit. You could then chose to commit only those changes to the Atoll document. To find the optimal order in which to apply these changes in the field, while at the same time avoiding less than optimal performance, or even degrading the performance, during the implementation phase.

Before selecting a subset of recommended changes, it is important to understand that ACP calculates the set of recommendations globally and that these changes are interdependent. During the finalisation step, ACP calculates the ordered list of changes displayed on the Change Details tab by starting from the initial network configuration and iteratively selecting the change that will have the most effect on the network. If you 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 proposed configuration. Important: The data displayed on the other tabs takes all the proposed changes into consideration. If you select only a subset of the proposed changes on the Change Details tab, the statistics displayed on other tabs do not change. When you commit the optimisation changes, ACP will only commit the proposed changes selected on the Change Details tab. For information on committing the optimisation changes, see "The Commit Tab" on page 618.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

617

Atoll User Manual

7.4.6.1.6

The Commit Tab

This dialogue enables you to commit the set of selected changes (antenna, azimuth, tilt, sector selection, or pilot power) to the Atoll document or to roll the network back to its initial state. The Commit tab automatically takes into account the changes selected on the Change Details tab; the Use check box is cleared for any change that was deselected on the Change Details tab.

Figure 7.349: The Commit tab You can select one of the following: Commit: Clicking the Commit button will update the Atoll document with the changes displayed on the Commit tab. Once you have committed the changes, you can recalculate the path losses and use any of the functions available in Atoll, including coverage predictions and simulations. After you perform any such calculations, remember to click the Roll Back to Initial State button to return to the original network settings. Roll Back to Initial State: Clicking the Roll Back to Initial State button will revert the Atoll network to its state before the optimisation was run.

When you click either the Commit button or the Roll Back to Initial State button, information about the commit or rollback process is displayed in the Atoll Event Viewer.

The Effects of Committing or Rolling Back Changes on Existing Setups

When you commit the optimisation results, all existing configuration setups are locked because the network state on which the configuration setup was based is not coherent with the current path losses. ACP automatically detects any incoherence and prevents you from running an optimisation on incoherent data. ACP will unlock the optimisation setups when it becomes possible, for example, when you roll back the data to restore the Atoll state to be coherent with the network state on which the configuration setup was based. It is important to remember that you can commit or roll back other optimisation results even when the setup is locked.

7.4.6.2

Viewing Optimisation Results in the Map Window

ACP can display optimisation results in the form of maps in the map window. This allows you to view the results and facilitates analysis. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default or by using a configuration file. To view the results of the optimisation in the map window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view.

4. Right-click the optimisation. The context menu appears. 5. Select New Map from the context menu. The ACP Map Types dialogue appears (see Figure 7.351).

618

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.350: Displaying a new map based on ACP results The maps available in the ACP Map Types dialogue are organised by category. 6. Select the category of maps or click the Expand button ( egory or map. ) to expand the category and then select the sub-cat-

7. Click OK to create the maps. The maps are created and inserted into the folder of the setup containing the optimisation results (see Figure 7.351).

Figure 7.351: The map types correspond to the available results You can display a map by selecting its check box in the folder of the setup containing the optimisation results. The display properties can be changed for a single map or for all maps. For information on the display properties for ACP maps, see "Changing the Display Properties of ACP Maps" on page 623. The following sections provide more information on the maps: "The Quality Analysis Maps" on page 619 "The Coverage Analysis Maps" on page 620 "The Change Analysis Maps" on page 621 "Best Server Analysis" on page 622 "Comparing Maps" on page 622 "Changing the Display Properties of ACP Maps" on page 623 "Exporting ACP Coverage Maps" on page 624.

7.4.6.2.1

The Quality Analysis Maps

The quality analysis maps enable you to display the RSCP and EcIo quality maps in the Atoll map window. These maps are the same as those displayed on the Quality tab of the optimisations Properties dialogue. The quality analysis maps are the equivalent of maps created by different Atoll coverage predictions: The RSCP maps correspond to the Atoll coverage by signal level in UMTS. For information on the coverage by signal level, see "Studying Signal Level Coverage" on page 490. The overlapping zones maps correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 500.

Making these maps available within ACP enables you to quickly validate the optimisation results without having to commit the results and then calculate a coverage prediction in Atoll. The ACP maps display results very similar to those that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before basing

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

619

Atoll User Manual any decision to commit the optimisation results on the maps produced by ACP, you should keep the following recommendations in mind: You should verify the results with a different Atoll coverage prediction, such as the pilot pollution prediction. ACP generated maps are generated using the entire set of proposed changes. They do not take into account the change subset defined on the Change Details tab. Multiple carriers are not supported by ACP; the maps are only provided for the requested carrier. Even after committing the optimisation results, differences can remain between the ACP maps and the maps resulting from Atoll coverage predictions.

You can view the exact RSCP and EcIo values on any pixel by letting the pointer rest over the pixel. The RSCP or EcIo value is then displayed in a tooltip. For the overlapping zones map, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Configuring the Default Settings" on page 583) or by setting the CellOverlap parameter in the acp.ini file.

Figure 7.352: Examples of an overlapping zones map (left) and an EcIo variation map (right) For each network quality study, ACP offers a map showing the initial network state, the final network state, and a map showing the changes between the initial and final state.

7.4.6.2.2

The Coverage Analysis Maps

The coverage analysis maps display the coverage status according to the defined threshold used in the optimisation (for both RSCP and EcIo). You can use the coverage analysis maps to quickly see the area where the coverage requirements have been fulfilled. In addition, the thresholds used for clutter and hot spot zones are taken into account. There are two types of coverage analysis maps: Initial and Final Coverage: The initial and final cell coverage maps display the areas where there is RSCP and EcIo coverage. Cell Coverage Improvement: The cell RSCP or EcIo coverage improvement maps show how the coverage has been improved or degraded by the optimisation.

Figure 7.353: Example of final cell coverage (left) and EcIo coverage improvement (right) You can define how the coverage analysis maps will be displayed. To define the coverage analysis map display: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 618, right-click the Coverage Analysis folder. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears (see Figure 7.354).

620

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.354: Defining display and threshold properties 3. Select the Display tab. On the Display tab, you can select the colour used to display RSCP coverage, EcIo coverage, and both. As well, you can use the slider to adjust the Transparency. 4. Select the Thresholds tab. On the Thresholds tab, you can set the thresholds to be used for the map. For both RSCP and EcIo, you can use the same thresholds as you used when you calculated the optimisation, or you can set a different threshold.

7.4.6.2.3

The Change Analysis Maps

The change analysis maps allow you to analyse the changes recommended by the ACP. The change attributes are displayed on the map using a best server map, because the types of changes that ACP recommends are all related to individual cells. The best server map used is usually the initial best server map but you can use the final best server map for new sites (i.e., sites that have been added during optimisation). The following maps are available: Reconfiguration Types: In the Reconfiguration Types folder, there is a separate map for each reconfiguration option displaying the changes to the network: azimuth, mechanical tilt, antenna, and pilot power. The changes are displayed for the best server zone. The maps can be displayed individually to display each reconfiguration option separately or together to display all reconfiguration options. Sector Selection Types: In the Sector Selection Types folder, there are maps to display which sectors or sites have been added or removed. These maps are only available if the site selection was activated during optimisation. Change Order: The Change Order map displays the order of changes (as displayed on the Change Details tab of the optimisations Properties dialogue). You can define the colours used to display the order of changes by right-clicking the Change Order map in the Data tab, selecting Properties from the context menu and then changing the colours on the Display tab. By displaying the Change Order map, you can see where the most important changes to be made to the network are located. Change of Electrical Tilt, Mechanical Tilt, Azimuth, Height, Pilot Power, and Change Cost: These maps show the variation of the given parameter. They can be used to see where in the network this reconfiguration option was changed. Note: The electrical tilt values are calculated using the vertical antenna pattern. The Change of Electrical Tilt map is made available even when the change was to the antenna type.

Figure 7.355: Example of antenna type change (left) and electrical tilt change (right)

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

621

Atoll User Manual

7.4.6.2.4

Best Server Analysis

The best server analysis maps contain maps enabling you to analyse cell-related parameters as related to the best server. The following maps are available: Initial and Final Electrical and Mechanical Tilt Values: These maps show the tilt values on the initial and final network. They can be used, for example, to identify areas with strong tilt values. Initial and Final Antenna Height: These maps show the initial and final antenna heights. Initial and Final Cell RSCP and EcIo Coverage: These maps show the percentage of the best server area which is covered according to the defined threshold. The values displayed are the same as those on the Cells tab of the optimisations Properties dialogue. You can use these maps to quickly identify the cells which potentially have poor quality. Initial and Final Overlapping Ratio: These maps show the percentage of the best server area with overlapping coverage greater than "1," i.e., with several received signals over the defined threshold.

7.4.6.2.5

Comparing Maps
You can compare the results displayed on one map with the results of another map from the same optimisation or from a different optimisation. To compare a map with a map from the same optimisation: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 618, right-click the map you want to compare. The context menu appears. 2. From the context menu, select Compare With and then select one of the maps in the submenu. A new map is created in the Data tab and the results of the comparison are displayed in the map window. 3. ACP creates a new map in the Data tab and displays it in the map window with the pixels that are displayed on both maps or only on a single map.

Figure 7.356: Comparing two optimisation maps To compare a map with a map from a different map type or with a map from a different optimisation: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 618, right-click the map you want to compare. The context menu appears. 2. From the context menu, select Compare With > Others. The ACP Compare Map dialogue appears (see Figure 7.357). By default, the ACP Compare Map dialogue displays only maps from the same optimisation as the map you want to compare.

Figure 7.357: The ACP Compare Map dialogue

622

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 3. Define the maps you choose from: Show studies from Predictions folder: Select the Show studies from Predictions folder check box if you want to be able to compare with a map from a coverage prediction you have already created and calculated. Show maps from all ACP setups: Select the Show maps from all ACP setups check box if you want to be able to compare with a map from a different optimisation. Show only maps of same type: Select the Show only maps of same type check box if you want to restrict the maps displayed to maps displaying comparable information.

4. Select the map with which you want to compare the first one and click OK. ACP creates a new map in the Data tab and displays it in the map window with the pixels that are displayed on both maps or only on a single map.

Tip:

By first defining a display interval of "1" in both maps and then comparing them, the resulting comparison map will have more meaningful results. For information on defining "Changing the Display Properties of ACP Maps" on page 623.

7.4.6.2.6

Changing the Display Properties of ACP Maps

You can define how ACP maps are displayed in the Atoll map window. You can define the colours used as well as the ranges of values on the Display tab of each maps Properties dialogue. As well, ACP allows you to display the value on each pixel in the form of a tooltip. To define the display of an ACP map: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 618, right-click the map whose display you want to define. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears (see Figure 7.358).

Figure 7.358: Setting the display properties for a map 3. Select the Display tab. 4. On the Display tab, you can define the following settings: Colours: For each range of values, you can click the colour button and select the colour that will be used to represent that range. Min. and Max.: You can define the minimum and maximum values that will define that range. Transparency: You can define the transparency of the map using the slider. Add to legend: You can display the range of values of the optimisation map by selecting the Add to legend. check box. Actions: You can modify the ranges of values by clicking the Actions button and selecting one of the following: Select All: Select Select All to select all the ranges on the display tab. Anything you select after that from the Actions menu (for example, Delete) will be applied to the selected ranges. Delete: Select Delete to delete the selected range or ranges. Insert Before: Select Insert Before to insert a new range before the selected range. Insert After: Select Insert After to insert a new range after the selected range Shading: Select Shading to open the Shading dialogue where you can define all the ranges by setting the first value, the last value, and the step between values, as well as the colour used for the first value and the colour used for the last value. ACP will shade the ranges in between the first and last value with a range of colours going from the first colour to the last. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

623

Atoll User Manual Save as Default: Select Save as Default to set the current settings on the display tab to the default settings. These settings can then be used for all maps of the same kind. Load from Default: Select Load from Default to change the current settings to those set as the default using Save as Default. Reset to Default: Select Reset to Default to change the current settings back to the ACP defaults. You can also use Reset to Default to return to the ACP defaults when you have created user-defined defaults using Save as Default.

You can display the value on a pixel by resting the pointer on the pixel in the map window. The value on that pixel will be displayed in a tooltip (see Figure 7.359).

Figure 7.359: Tool tip displaying ACP results on selected point

7.4.6.2.7

Exporting ACP Coverage Maps

ACP enables you to export the optimisation coverage maps as BMP files. Before you can export an optimisation coverage map, you must first select the map and define its appearance as explained in "Viewing Optimisation Results in the Map Window" on page 618. To export an optimisation coverage map: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( 4. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation map you want to export. ) to expand the optimisation.

5. Right-click the map. The context menu appears. 6. Select Export the Coverage from the context menu. The Save As dialogue appears. 7. Enter a File name for the exported coverage map and select the format from the Save as type list. 8. Click Save. The exported coverage map is saved in the selected format. Depending on the file format selected from the Save as type list, Atoll creates an additional file in the same location containing geo-referencing information: BMP file: Atoll creates a BPW file. ArcView grid (TXT) file: Atoll creates a BPW file. BIL file: Atoll creates a HDR file. GRD or GRC file: Atoll creates a TAB file. PNG file: Atoll creates a PGW file. TIF file: Atoll creates a TFW file.

9. Atoll also creates a BPW file in the same location containing geo-referencing information.

7.4.6.3

Viewing Optimisation Results Using the Histogram

ACP can display optimisation results in the form of a histogram. The histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be used for the histogram, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default or by using a configuration file. To view the results of the optimisation using a histogram: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( 4. Click the Expand button ( Note: ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view. ) to expand the folder of the optimisation.

Depending on the type of optimisation results you want to view, you might need to expand additional folders.

5. Right-click the optimisation results. The context menu appears.

624

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 6. Select Histogram from the context menu. The histogram appears in a separate window with a legend on the right side.

7.5

Verifying Network Capacity

An important step in the process of creating a UMTS HSPA network is verifying the capacity of the network. This is done using measurements of the strength of the pilot signal in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: "Importing a Drive Test Data Path" on page 625 "Displaying Drive Test Data" on page 627 "Defining the Display of a Drive Test Data Path" on page 628 "Network Verification" on page 628 "Exporting a Drive Test Data Path" on page 633 "Extracting CW Measurements from Drive Test Data" on page 633 "Printing and Exporting the Drive Test Data Window" on page 634.

7.5.1

Importing a Drive Test Data Path

In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In UMTS networks, a cell is identified by its scrambling code. Therefore, you must indicate during the import process which columns contain the scrambling code of cells and the scrambling code format (decimal or hexadecimal) used in the file. Because a scrambling code can belong to several groups, you can also indicate from which group the scrambling code has been selected.

You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test data files of the same format, you can create an import configuration. The import configuration contains information that defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the data structure each time you import a new drive test data file. To import one or several drive test data files: 1. Click the Data tab in the Explorer window. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. You can import one or several files. Select the file or files you want to open. Note: If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import.

5. Click Open. The Import of Measurement Files dialogue appears. Note: Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue.

6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Configuration, select an import configuration from the Configuration list. b. Continue with step 10.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

625

Atoll User Manual

Notes: When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. In case several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual. 7. Click the General tab. On the General tab, you can set the following parameters: Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document. 8. Click the Setup tab (see Figure 7.360).

Figure 7.360: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click Setup to link file columns and internal Atoll fields. The Drive Test Data Configuration dialogue appears. c. 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. Note: 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. In the SC 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 iden-

626

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks tifying 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 SC Group Identifier box empty. e. In the SC Identifier box, enter a string that must be 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. f. From the SC Format list, select the scrambling code format, either "Decimal" or "Hexadecimal."

g. Click OK to close the Drive Test Data Configuration dialogue. Important: If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Configuration dialogue, Atoll should recognize all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>". If a column is marked with "<Ignore>", it will not be imported. The data in the file must be structured so that the columns identifying the scrambling code group and the scrambling code are placed before the data columns for each cell. Otherwise Atoll will not be able to properly import the file.

9. If you wish 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 Configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a special 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, "*.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. Notes: 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 button ( ) in front of the file in the Setup part to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Setup 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.

7.5.2

Displaying Drive Test Data

When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see information about the active set at that location. To display information about a single drive test data point: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want active set information. Atoll displays an arrow pointing towards the serving cells (see Figure 7.362 on page 632), with a number identifying the server as numbered in the drive test data. If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display Type" on page 33.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

627

Atoll User Manual

7.5.3

Defining the Display of a Drive Test Data Path

You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to manage permanent labels on the map, tooltips and the legend. In other words, the display of measurement path are managed in the same way as sites, transmitters, etc. To display the Display tab of a drive test data paths Properties dialogue: 1. Click the Data tab in the Explorer window. 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: a text or integer attribute (discrete value) a numerical value (value interval).

In addition, you can display points by more than one criterion at a time using the Advanced option in the Display Type list. When you select Advanced from the Display Type list, a dialogue opens in which you can define the following display for each single point of the measurement path: a symbol according to any attribute a symbol colour according to any attribute a symbol size according to any attribute

You can, for example, display a signal level in a certain colour, choose a symbol type for Transmitter 1 (a circle, triangle, cross, etc.) and a symbol size according to the altitude. Notes: Fast Display forces Atoll to use the lightest symbol to display the points. This is particularly useful when you have a very large number of points. You can not use Advanced Display if the Fast Display check box has been selected. You can sort drive test data paths in alphabetical order on the Data tab of the Explorer window by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can export the display settings of a drive test data path in a configuration file to make them available for future use. You can export the display settings or import display settings by clicking the Actions button on the Display tab of the drive test data paths Properties dialogue and selecting Export or Import from the menu.

7.5.4

Network Verification
The imported drive test data is used to verify the UMTS HSPA network. To improve the relevance of the data, Atoll allows you to filter out incompatible or inaccurate points. You can then use the data for coverage predictions, either by comparing the imported measurements with previously calculated coverage predictions, or by creating new coverage predictions using the imported drive test data. In this section, the following are explained: "Filtering Incompatible Points Along Drive Test Data Paths" on page 628 "Creating Coverage Predictions from Drive Test Data Paths" on page 630 "Displaying Statistics Over a Drive Test Data Path" on page 631 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 631 "Analysing Data Variations Along the Path" on page 632.

7.5.4.1

Filtering Incompatible Points Along Drive Test Data Paths

When using a drive test data path, some measured points may present values that are too far outside of the median values to be useful in calibration. As well, test paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

628

Chapter 7: UMTS HSPA Networks The context menu appears. 3. Select Filter from the context menu. The Drive Test Data Filter dialogue 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. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder.

The context menu appears. 3. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 4. Click More. The Filter dialogue appears. 5. Click the Filter tab: a. Select a Field from the list. b. Under Values to Include, you will find all the values represented in the selected field. Select the check boxes next to the values you want to include in the filter. Click Clear All to clear all check boxes. 6. Click the Advanced tab: a. In the Column row, select the name of the column to be filtered on from the list. Select as many columns as you want (see Figure 7.361).

Figure 7.361: The Filter dialogue - Advanced tab b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table:

Formula
=X <> X <X >X <=X >=X *X* *X

Data are kept in the table only if

value equal to X (X may be a number or characters) value not equal to X (X may be a number or characters) numerical value is less than X numerical value is greater than X numerical value is less than or equal to X numerical value is greater than or equal to X text objects which contain X text objects which end with X

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

629

Atoll User Manual

Formula
X*

Data are kept in the table only if

text objects which start with X

7. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering" on page 75. 8. Click OK to apply the filter and close the dialogue. Note: The Refresh Geo Data option available in the context menu of Drive Test Data paths enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones.

7.5.4.2

Creating Coverage Predictions from Drive Test Data Paths

You can create the following coverage predictions for all transmitters on each point of a drive test data path: Pilot signal level and coverage by signal level Pilot reception analysis (EcI0), service area (EbNt) downlink, and service area (EbNt) uplink.

To create a coverage prediction along a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. 5. Under Standard Studies, select one of the following coverage predictions and click OK: Coverage by Signal Level: Click the Condition tab. At the top of the Condition tab, you can set the range of signal level to be calculated. Under Server, you can select whether to calculate the signal level from all transmitters, or only the best or second-best signal. If you choose to calculate the best or second-best signal, you can enter a Margin. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. Finally, you can select the Carrier to be studied. On the Condition 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 510. 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. On the Condition 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 510. 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. On the Condition 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.

Pilot Reception Analysis (EcI0): Click the Condition tab. -

Service Area (EbNt) Downlink: Click the Condition tab.

Service Area (EbNt) Uplink: Click the Condition tab.

630

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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 510. 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.

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 Studies from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calculations in Atoll). You can display the information in these new columns in the Drive Test Data window. For more information on the Drive Test Data window, see "Analysing Data Variations Along the Path" on page 632.

7.5.4.3

Displaying Statistics Over a Drive Test Data Path

Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific Drive Test Data path: 1. Click the Data tab in the Explorer window. 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 dialogue 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.

7.5.4.4

Extracting a Field From a Drive Test Data Path for a Transmitter

You can extract a specific field for a specific transmitter on each point of an existing drive test data path. The extracted information will be added to a new column in the table for the drive test data. To extract a field from a drive test data path: 1. Click the Data tab in the Explorer window. 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 Select for a Given Transmitter dialogue appears. 5. Select a transmitter from the On the Transmitter list. 6. Click the For the Fields list. The list opens. 7. Select the check box beside the field you want to extract for the selected transmitter.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

631

Atoll User Manual

Note:

Atoll can display the best server and up to six other servers in the active set. If you want to display for example, the point signal level, remember to select the check box for the point signal level for all servers in the For the Fields list. The new column will then display the point signal level for the selected transmitter for all servers if a value exists.

8. Click OK. Atoll creates a new column in the drive test data path data table for the selected transmitters and with the selected values.

7.5.4.5

Analysing Data Variations Along the Path

In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point. To analyse data variations using the Drive Test Data window. 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 7.362).

Figure 7.362: The Drive Test Data window 5. Click Display at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 7.363).

Figure 7.363: The Drive Test Data window 6. In the Display Parameters dialogue: Select the check box next to any field you want to display in the Drive Test Data window.

632

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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 dialogue. Note: You can change the display status or the colour of more than one field at a time. You can select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field you want to import. You can select non-contiguous fields by pressing CTRL and clicking each field. You can then change the display status or the colour by right-clicking on the selected fields and selecting the choice from the context menu.

The selected fields are displayed in the Drive Test Data window. 7. You can display the data in the drive test data path in two ways: Click the values in the Drive Test Data window. Click the points on the drive test data path in the map window.

The drive test data path appears in the map window as an arrow pointing towards the serving cell, with a number identifying the best server (see Figure 7.362 on page 632). If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display Type" on page 33. 8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the secondary Y-axis from the right-hand list on the top of the Drive Test Data window. The selected values are displayed in the colours defined for this variable in the Display Parameters dialogue. 9. You can change the zoom level of the Drive Test Data window display in the Drive Test Data window in the following ways: Zoom in or out: i. Right-click the Drive Test Data window.

ii. Select Zoom In or Zoom Out from the context menu. Select the data to zoom in on: i. Right-click the Drive Test Data window on one end of the range of data you want to zoom in on.

ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data window on the other end of the range of data you want to zoom in on. iv. Select Last Zoom Point from the context menu. The Drive Test Data window zooms in on the data between the first zoom point and the last zoom point. 10. Click the data in the Drive Test Data window to display the selected point in the map window. Atoll will recentre the map window on the selected point if it is not presently visible.

Tip:

If you open the table for the drive test data you are displaying in the Drive Test Data window, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data window (see Figure 7.362 on page 632).

7.5.5

Exporting a Drive Test Data Path

You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.

7.5.6

Extracting CW Measurements from Drive Test Data

You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

633

Atoll User Manual 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears. 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the Transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the For the Fields list. 6. Under CW Measurement Creation Parameters: a. Enter the Min. Number of Points to Extract per Measurement Path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured Signal Levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.

7.5.7

Printing and Exporting the Drive Test Data Window

You can print or export the contents of the Drive Test Data window, using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 7.362 on page 632). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 632. 6. Right-click the Drive Test Data window. The context menu appears. To export the Drive Test Data window: a. Select Copy from the context menu. b. Open the document into which you want to paste the contents of the Drive Test Data window. c. Paste the contents of the Drive Test Data window into the new document. To print the Drive Test Data window: a. Select Print from the context menu. The Print dialogue appears. b. Click OK to print the contents of the Drive Test Data window.

7.6

Co-planning UMTS Networks with Other Networks

Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a UMTS and a GSM network for the same area in Atoll, and then work with Atolls co-planning features to study the mutual impacts of the two networks. Important: Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other networks Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In addition, you can optimise the settings of the two networks using Atolls Automatic Cell Planning (ACP) module. In this section, the following are explained: "Switching to Co-planning Mode" on page 635 "Working with Coverage Predictions in a Co-Planning Project" on page 636 "Performing Inter-Technology Neighbour Allocation" on page 640 "Creating a UMTS Sector From a Sector in the Other Network" on page 650 "Using ACP in a Co-planning Project" on page 650 "Ending Co-planning Mode" on page 652.

634

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

7.6.1

Switching to Co-planning Mode

Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a UMTS Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, the UMTS document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Important: Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems. To switch to co-planning mode: 1. Open the main document. Select File > Open or File > New > From an Existing Database.

2. Link the other document with the open main document. a. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document. b. Select File > Link With. The Link With dialogue appears. c. Select the document to be linked. d. Click Open. The selected document is opened in the same Atoll session as the main document and the two documents are linked. The Explorer window of the main document now contains a folder named Transmitters in [linked document], where [linked document] is the name of the linked document and another folder named Predictions in [linked document]. Note: By default, only the Transmitters and Predictions folders of the linked document appear in the main document. If you want the Sites folder of the linked document to appear in the main document as well, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.

As soon as a link is created between the two documents, Atoll switches to co-planning mode and Atolls co-planning features are now available. When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll syncronises the display for the following: Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.

Displaying Both Networks in the Same Atoll Document

After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 635, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the Explorer window of the linked document to the Explorer window of the main document (e.g., you can display GSM sites and measurement paths in a UMTS document). To display sites from the linked document in the main document: 1. Click the linked documents map window. The linked documents map window becomes active and the Explorer window shows the contents of the linked document. 2. Click the Data tab of the Explorer window. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In > [main document] from the context menu, where [main document] is the name of the main document. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

635

Atoll User Manual Once the folders are linked, you can access their properties and the properties of the items in the folders from either of the two documents. Any changes you make in the linked document are taken into account in the both the linked and main documents. However, the only changes in the working document that are taken into account in the linked document are changes made to the linked folders (e.g., the Transmitters and Predictions folders). If you close the linked document, Atoll displays a warning icon ( ) in the main documents Explorer window, and the linked items are no longer accessible from the main document. You can load the linked document in Atoll again by rightclicking 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 82. You can also set the tool tips to enable you to distinguish the objects and data displayed on the map. For more information on tool tips, see "Defining the Object Type Tip Text" on page 36. In order to more easily view differences between the networks, you can also change the order of the folders or items in the Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers Using the Explorer" on page 28. Figure 7.364 shows an example of UMTS transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in a tool tip.

Figure 7.364: GSM and UMTS Transmitters displayed on the map

7.6.2

Working with Coverage Predictions in a Co-Planning Project

Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: "Updating Coverage Predictions" on page 636 "Analysing Coverage Predictions" on page 637.

7.6.2.1

Updating Coverage Predictions

You can access the properties of the coverage predictions in the linked Predictions folder in the main documents Explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button ( ) in the toolbar.

636

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks When you click the Calculate button, Atollfirst calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 185. If you want, you can make Atoll recalculate all path loss matrices, including valid ones, before calculating unlocked coverage predictions in the main and linked Predictions folders. To force Atoll to recalculate all path loss matrices before calculating coverage predictions: Click the Force Calculate button ( ) in the toolbar.

When you click the Force Calculate button, Atoll first removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions defined in the main and linked Predictions folders. Note: 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.

7.6.2.2

Analysing Coverage Predictions

In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tooltips to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which studies to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following are explained: "Co-Planning Coverage Analysis Process" on page 637 "Displaying the Legend Window" on page 638 "Comparing Coverage Prediction Results Using Tooltips" on page 638 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 638 "Studying Differences Between Coverage Areas" on page 639.

7.6.2.2.1

Co-Planning Coverage Analysis Process

The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. Note: In a co-planning environment, many sites share the same antennas, using one mast for both technologies. When transmitter, remote antenna, or repeater antennas have the same co-ordinates and the same value set for the SHAREDMAST field in both coplanning documents, Atoll assumes that the antennas are shared. Atoll then automatically synchronises changes made to shared antenna parameters in one coplanning document in the other document. The shared antenna parameters include the site location (X and Y coordinates), the antenna's position relative to the site (Dx, Dy), antenna height, azimuth and mechanical tilt. The SHAREDMAST field is not available by default and must be added in order for the synchronization mechanism to operate. For information on setting up shared antenna parameter synchronisation, see the Administrator Manual.

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 (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the main document. For more information, see "Making a Coverage Prediction by Transmitter" on page 499 and "Studying Signal Level Coverage" on page 490. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tool tip contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage predictions Properties dialogue. 4. Make the two new coverage predictions in the linked document accessible in the main document as described in "Displaying Both Networks in the Same Atoll Document" on page 635.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

637

Atoll User Manual 5. Optimise the main network by changing parameters such as antenna azimuth and tilt or the pilot power. You can use a tool such as the Atoll ACP to optimise the network. 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 638 and "Studying Differences Between Coverage Areas" on page 639. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.

7.6.2.2.2

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

7.6.2.2.3

Comparing Coverage Prediction Results Using Tooltips

You can compare coverage predictions by by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltip. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Analysing Coverage Predictions" on page 637). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 7.290). The tooltip for the working document is on top and the tooltip for the linked document, with the linked document identified by name is on the bottom.

Figure 7.365: Comparing coverage prediction results using tooltips

7.6.2.2.4

Comparing Coverage Areas by Overlaying Coverage Predictions

You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is dislayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 32. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is dislayed on the map.

638

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 11. Right-click the coverage prediction. The context menu appears. 12. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 13. Modify the display parameters of the coverage prediction. 14. Calculate the two coverage predictions again, if needed. Figure 7.366 and Figure 7.367 show an example of overlayed UMTS and GSM coverage predictions. To more easily view differences between the coverage areas, you can also change the order of the Predictions folders in the Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers Using the Explorer" on page 28.

Figure 7.366: UMTS Coverage Prediction (Pilot Best Server) Pink contours with no interior

Figure 7.367: GSM Coverage Prediction (Best Server) High transparency with full interior coloured by BCCH, with BCCH/BSIC information available in tooltips

7.6.2.2.5

Studying Differences Between Coverage Areas

You can compare coverage predictions to find differences in coverage areas. To compare coverage predictions: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Right-click the coverage prediction of the main document you want to compare. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

639

Atoll User Manual 5. Select Compare With > [linked coverage prediction] from the context menu, where [linked coverage prediction] is the linked coverage prediction you want to compare with the coverage prediction of the main document. The Comparison Properties dialogue opens. 6. Select the display parameters of the comparison and add a comment if you want. 7. Click OK. The two coverage predictions are compared and a comparison coverage prediction is added to the main documents Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 506.

7.6.3

Performing Inter-Technology Neighbour Allocation

The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between a UMTS and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to UMTS cells. In this section, the following are explained: "Setting Inter-Technology Exceptional Pairs" on page 640 "Configuring Importance Factors for Inter-Technology Neighbours" on page 642 "Allocating Inter-Technology Neighbours Automatically" on page 642 "Displaying Inter-Technology Neighbours on the Map" on page 644 "Allocating and Deleting Inter-Technology Neighbours per Cell" on page 645 "Calculating the Importance of Existing Inter-technology Neighbours" on page 647 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 649.

In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Co-planning Mode" on page 635.

7.6.3.1

Setting Inter-Technology Exceptional Pairs

You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Exceptional Pairs from the context menu. The Exceptional Pairs of Inter-technology Neighbours table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. d. Atoll fills the Number and Distance (m) fields automatically. In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector). You can access a cells inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cells Properties dialogue: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Double-click the row corresponding to the cell whose properties you want to access. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitters Properties dialogue.

Displaying Inter-Technology Exceptional Pairs on the Map

You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table.

640

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks To display exceptional pairs defined between the main and the linked documents: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select which exceptional pair links to display: Outwards Non-Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Selecting this option displays an exceptional pair link for each transmitter/cell in the linked document that has an exceptional pair defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Forced Neighbours or Forbidden Neighbours from the menu. The exceptional pair of a cell will be displayed when you select a transmitter. 8. Click the Visual Management button ( ) in the Radio toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Visual Management button again. 9. Click a transmitter on the map to show its exceptional pair links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map.

Adding and Removing Inter-Technology Exceptional Pairs on the Map

You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-Technology Exceptional Pairs on the Map" on page 640. To add a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set an exceptional pair. Atoll adds both transmitters to the list of inter-technology exceptional pairs of the other transmitter. To remove a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes both transmitters from the list of inter-technology exceptional pairs of the other transmitter. To add an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set an exceptional pair. Atoll adds the reference transmitter to the list of inter-technology exceptional pairs of the other transmitter. To remove an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the reference transmitter from the list of inter-technology exceptional pairs of the other transmitter. To add an inwards forced or forbidden exceptional pair: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric exceptional pair relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

641

Atoll User Manual If there is no existing exceptional pair relation between the two transmitters, first create a symmetric exceptional pair relation between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation.

To remove an inwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the transmitter from the inter-technology exceptional pairs list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

7.6.3.2

Configuring Importance Factors for Inter-Technology Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. Note: In a GSM project, you must select Neighbours > Configure Importance from the Transmitters folders context menu.

4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when performing automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Inter-Technology Neighbours Automatically" on page 642.

5. Click OK.

7.6.3.3

Allocating Inter-Technology Neighbours Automatically

Atoll can automatically determine handover relations between networks of different technologies, for example, UMTS and GSM. In this case, inter-technology handovers from UMTS to GSM may occur when the UMTS coverage is not continuous. The networks overall coverage is extended by a UMTS-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database. Note: By setting an option in the atoll.ini file, you can prevent Atoll from allocating intertechnology neighbours to cells located on sites whose equipment does not support the compressed mode. For more information, see the Administrator Manual.

To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 5. Click the Inter-technology Neighbours tab. 6. Define the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. 7. Define the maximum number of inter-technology neighbours that can be allocated to a cell in the Max Number of Neighbours box. This value can be either set here for all the cells, or specified for each cell in the Cells table.

642

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 8. Clear the Use Overlapping Coverage check box in order to base the neighbour allocation on distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour allocation on coverage conditions. a. Click the Define button to change the coverage conditions for the cells in the main document. The UMTS Coverage Conditions dialogue appears. In the UMTS Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell. Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the best server in terms of pilot quality or a cell of the active set. Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the reference cell. DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink load for all the cells, or the downlink loads Defined per Cell. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is an LTE document, the LTE Coverage Conditions dialogue appears. In the LTE Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. e. In the % Min. Covered Area box, enter the minimum percentage of the cells coverage area that the neighbours coverage area should also cover to be considered as a neighbour. 9. Under Calculation Options, define the following: CDMA Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers; Atoll will allocate neighbours to cells using the selected carriers. Force co-site as neighbours: Selecting the Force co-site as neighbours check box will include the co-site transmitters/cells in the neighbour list of the UMTS cell. The check box is automatically selected when the neighbour allocation is based on distance. Force exceptional pairs: Selecting the Force exceptional pairs check box will apply the inter-technology exceptional pair criteria on the neighbours list of the UMTS cell. Delete existing neighbours: Selecting the Delete existing neighbours check box will delete all existing neighbours in the neighbours list and perform a clean neighbour allocation. If the Delete existing neighbours check box is not selected, Atoll keeps the existing neighbours in the list.

10. Click the Calculate button to start calculations. 11. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the names of the neighbours, the number of neighbours of each cell, and the reason they are included in the neighbours list. The reasons include:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

643

Atoll User Manual

Reason
Exceptional Pair Co-site Distance % of covered area and overlapping area Existing

Description
Neighbour relation is defined as an exceptional pair. The neighbour is located at the same site as the reference cell. The neighbour is within the maximum distance from the reference cell. Neighbour relation that fulfils coverage conditions. The neighbour relation existed before running the automatic allocation.

When
Force exceptional pairs is selected Force co-site as neighbours is selected Use Coverage Overlapping is not selected Use Coverage Overlapping is selected Reset is not selected

12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

13. Click the Commit button. The allocated neighbours are saved in the Intra-technology Neighbours tab of each cell. 14. Click Close.

7.6.3.4

Displaying Inter-Technology Neighbours on the Map

You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select the neighbour links to display: Outwards Non-Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Neighbours as the type of neighbour links to display. 8. Click the Visual Management button ( ) in the Radio toolbar. Neighbours are now displayed on the map. Neighbours and displayed until you click the Visual Management button again.

644

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.

7.6.3.5

Allocating and Deleting Inter-Technology Neighbours per Cell

Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Intertechnology Neighbours table. This section explains the following: "Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 645. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 646. "Allocating and Removing Inter-Technology Neighbours on the Map" on page 647.

Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Cells tab of the transmitters Properties dialogue: 1. On the main documents map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. 6. If desired, you can enter the Maximum Number of Neighbours. 7. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, and sets the Type to "manual." 8. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

645

Atoll User Manual 9. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 11. Click OK. In GSM, the inter-technology neighbours tab is available in each transmitters Properties dialogue.

Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table

To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Neighbours from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. To allocate an inter-technology neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Type to "manual." 7. To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 8. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. 9. To take all exceptionnal pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either forced neighbours or forbidden neighbours using the Exceptional Pairs of Inter-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu. ), select a reference cell in the Cell column.

10. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 11. To delete several symmetric neighbour relations: a. Click in the left margin of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears.

646

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks c. Select Delete Link and Symmetric Relation from the context menu. 12. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector).

Allocating and Removing Inter-Technology Neighbours on the Map

You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-Technology Neighbours on the Map" on page 644. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. T remove an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the list of inter-technology neighbours of the other transmitter. To add an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. There can be two cases: If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the inter-technology neighbours list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

7.6.3.6

Calculating the Importance of Existing Inter-technology Neighbours

After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing inter-technology neighbours: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

647

Atoll User Manual Note: In a GSM project, you must select Neighbours > Calculate Importance from the Transmitters folders context menu.

5. Select the Inter-technology Neighbours tab. 6. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance. 7. Clear the Use Overlapping Coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour importance calculation on coverage conditions. 8. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for cells in the main document. The UMTS Coverage Conditions dialogue appears. In the UMTS Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell. Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the best server in terms of pilot quality or a cell of the active set. Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the reference cell. DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink load for all the cells, or the downlink loads Defined per Cell. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is an LTE document, the LTE Coverage Conditions dialogue appears. In the LTE Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. 9. If you cleared the Use Overlapping Coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. Notes: You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

648

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 10. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 5. Cause: The reason Atoll has calculated the value in the Importance column. Co-site Symmetry Coverage

Distance: The distance in kilometres between the reference cell and the neighbour.

11. Click Close. The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

7.6.3.7

Checking the Consistency of the Inter-technology Neighbour Plan

You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab. 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Which cells having the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Lists > Max Number: Which cells having more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax: |CELL|

Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax: Note: |CELL| |NUMBER| |MAX NUMBER| If the field Maximum number of inter-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

649

Atoll User Manual Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

7.6.4

Creating a UMTS Sector From a Sector in the Other Network

You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main documents map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new UMTS transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder of the main document. The context menu appears. 4. Select Apply Current Configuration from the context menu.

Figure 7.368: New sector Before and after applying the configuration Note: 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.

7.6.5

Using ACP in a Co-planning Project

Atoll ACP enables you to automatically calculate the optimal network settings in terms of network coverage and capacity in co-planning projects where networks using different technologies, for example, UMTS and GSM, must both be taken into consideration. When you run an optimisation setup in a co-planning environment, you can display the sites and transmitters of both networks in the document in which you will run the optimisation process, as explained in "Switching to Co-planning Mode" on page 635. While this step is not necessary in order to create a co-planning optimisation setup, it will enable you to visually analyse the changes to both networks in the same document. Afterwards you can create the new optimisation setup, but when creating an optimisation setup in a co-planning environment, you can not run it immediately; you must first import the other network into the ACP setup. This section explains how to use ACP to optimise network settings in a co-planning project:

650

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks "Creating a New Co-planning Optimisation Setup" on page 651 "Importing the Other Network into the Setup" on page 651.

7.6.5.1

Creating a New Co-planning Optimisation Setup

Once you have displayed both networks in the main document as explained in "Switching to Co-planning Mode" on page 635, you can create the new co-planning optimisation setup. To create a new co-planning optimisation setup: 1. Click the main documents map window. 2. Click the Data tab in the Explorer window. 3. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 4. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation process. For information on the parameters available, see "Defining Optimisation Parameters" on page 587. 5. After defining the optimisation setup, click the Create Setup button to save the defined optimisation. The optimisation setup has now been created. The next step is to add the GSM network to the ACP optimisation setup you have just created.

7.6.5.2

Importing the Other Network into the Setup

Once you have created the co-planning optimisation setup, you must import the linked network. To import the linked network: 1. Click the main documents map window. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 651. 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.

ACP displays a dialogue enabling you to define which traffic will be used for the document you are importing. 6. Under Traffic generated from, select one of the following: Uniform traffic: Select Uniform traffic if the traffic in the document you are importing is uniform. Maps based on traffic densities: If the traffic is to be generated from traffic density maps, select Maps based on traffic densities and define the following parameters: When importing a GSM project: Under Traffic parameters, define whether traffic weighting should be applied to Cell Dominance or the BCCH or both by selecting the appropriate check boxes. When importing a UMTS project: Under Traffic parameters, define whether traffic weighting should be applied to the EcIo or the RSCP or both by selecting the appropriate check boxes. When importing either a GSM project or a UMTS project: Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Terminal, and select a Traffic Density File by clicking the Browse button ( ).

Following traffic maps: Select Following traffic maps if you have traffic maps available and then select the check boxes corresponding to the traffic maps you want to use.

7. Click OK. The setup has been modified to include the linked network. You can modify the parameters for the optimisation setup by right-clicking it on the Data tab of the Explorer window and selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation Parameters" on page 587.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

651

Atoll User Manual After defining the co-planning optimisation setup: Click the Run button to run the optimisation immediately. For information on running the optimisation, see "Running an Optimisation Setup" on page 609. For information on the optimisation results, see "Viewing Optimisation Results" on page 611. Click the Create Setup button to save the defined optimisation to be run later.

7.6.6

Ending Co-planning Mode

once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents. To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select File > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.

7.7

Advanced Configuration
In this section, the following advanced configuration options are explained: "Modelling Inter-Carrier Interference" on page 652 "Defining Frequency Bands" on page 652 "The Global Transmitter Parameters" on page 653 "Radio Bearers" on page 654 "Site Equipment" on page 656 "Receiver Equipment" on page 657 "Multiple Input Multiple Output Systems" on page 660 "Conditions for Entering the Active Set" on page 661 "Modelling Shadowing" on page 661 "Modelling Inter-Technology Interference" on page 662.

7.7.1

Modelling Inter-Carrier Interference

If you want Atoll to take into account the interference between two carriers, you must create a carrier pair with an interference reduction factor. Atoll will take the interference reduction factor into account on both the uplink and the downlink. To create a pair of carriers with an interference reduction factor: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Intra-technology IRF from the context menu. The Inter-Carrier Interference Reduction Factor table appears. 4. For each carrier pair for which you want define inter-carrier interference: a. Enter the first carrier of the pair in the 1st Carrier column. b. Enter the second carrier of the pair in the 2nd Carrier column. c. Enter an interference reduction factor in the Reduction Factor (dB) column. When Atoll is calculating interference, it subtracts the interference reduction factor from the calculated interference. If the interference reduction factor is set to "0," Atoll assumes that the carriers in the defined pair generate as much interference as cells with the same carrier interference. Important: The interference reduction factor must be a positive value. For every pair of carriers that is not defined, Atoll assumes that there is no inter-carrier interference. d. Press ENTER to create the carrier pair and to create a new row in the table.

7.7.2

Defining Frequency Bands

To define frequency bands: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears.

652

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 3. Select Network Settings > Frequencies > Bands from the context menu. 4. In the table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each frequency band, enter: Name: Enter a name for the frequency, for example, "Band 2100." This name will appear in other dialogues when you select a frequency band. Average Frequency (MHz): Enter the average frequency. First Carrier: Enter the number of the first carrier in this frequency band. Last Carrier: Enter the number of the last carrier in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First Carrier field. Important: 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 5. When you have finished adding frequency bands, click Close.

7.7.3

The Global Transmitter Parameters

On the Global Parameters tab of the Transmitters Properties dialogue, you can define many network parameters that are used in UMTS power control simulations. Many parameters are used as default values for all transmitters. This section explains the options available on the Global Parameters tab of the Transmitters Properties dialogue, and explains how to access the tab: "The Options on the Global Parameters Tab" on page 653 "Modifying Global Transmitter Parameters" on page 654.

7.7.3.1

The Options on the Global Parameters Tab

The Global Parameters tab has the following options: DL Powers: Under DL Powers, you can define whether the power values on the downlink are Absolute or Relative to Pilot. The power values affected are the synchronisation channel, other common channel, HS-SCCH, and HSUPA powers defined in the cell properties, as well as the minimum and maximum traffic channel powers per R99 radio bearer. Atollautomatically converts the power values defined in the cell properties (i.e., synchronisation channel, other common channel, HS-SCCH, and HSUPA powers) when you change the option. On the other hand, the values for the minimum and maximum traffic channel powers have to be modified manually. DL Load: Under DL Load, you can define whether the total power values on the downlink are Absolute or a percentage of the maximum power (% Pmax). Atollautomatically converts the total power values when you change the option. Interferences: Under Interferences, you can define the method used to calculate interference on the downlink (I0 and Nt): - I0: You can select "Total noise" and Atoll will calculate I0 using the noise generated by all transmitters plus thermal noise or you can select "Without pilot" and Atoll will calculate I0 using the total noise less the pilot signal and orthogonal part of traffic channels and other common channels. - Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus thermal noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the signal of the studied cell. Handoff: Under Handoff, you can define the parameters used to model soft handoff on the uplink. 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 Condition 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 Condition tab, Atoll calculates the UL macro-diversity gain, based on the standard deviation value of EbNt on the uplink 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 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. RSCP Activation Threshold: You can select the RSCP Active check box and enter a RSCP Activation Threshold. EcI0 Activation Threshold: You can select the EcI0 Active check box and enter a EcI0 Activation Threshold.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

653

Atoll User Manual

Note: -

You must select either the RSCP Active check box or the EcI0 Active check box or both.

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(HSPDSCH Ec/Nt) graph in the Properties dialogue of the terminal equipment. The calculated CQI will be used to determine the best bearer.

7.7.3.2

Modifying Global Transmitter Parameters

You can change global transmitter parameters on the Global Parameters tab of the Transmitters Properties dialogue. To change global transmitter parameters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Transmitters Properties dialogue appears. 4. Click the Global Parameters tab. 5. Modify the parameters described in "The Options on the Global Parameters Tab" on page 653. 6. Click OK.

7.7.4

Radio Bearers
Bearer services are used by the network for carrying information. In this section, the following are explained: "Defining R99 Radio Bearers" on page 654 "Defining HSDPA Radio Bearers" on page 655 "Defining HSUPA Radio Bearers" on page 655.

7.7.4.1

Defining R99 Radio Bearers

Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists all the available radio bearers. You can create new R99 radio bearers and modify existing ones by using the R99 Radio Bearer table. Only the following R99 radio bearer parameters are used in predictions: Max TCH Power (dBm) The type of bearer.

To create or modify an R99 radio bearer: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select R99 Radio Bearer from the context menu. The R99 Radio Bearer table appears. 5. In the R99 Radio Bearer table, you can enter or modify the following fields: Name: You can modify the name of the bearer. If you are creating a new R99 radio bearer, enter a name in the row marked with the New Row icon ( ). Nominal Uplink Rate (Kbps): Enter or modify the nominal uplink rate in kilobytes per second. Nominal Downlink Rate (Kbps): Enter or modify the nominal downlink rate in kilobytes per second. Type: Select or modify the service type. There are four classes: Conversational, Streaming, Interactive, and Background. This field corresponds to the QoS (quality of service) class or traffic class that the bearer will belong to. UL DPCCH/DPCH Power Ratio: Enter or modify the uplink DPCCH (Dedicated Physical Control Channel)/ DPCH (Dedicated Physical Channel) power ratio. The DPCH power is the combination of the DPCCH and the DPDCH (Dedicated Physical Data Channel) power. DL DPCCH/DPCH Power Ratio: Enter or modify the downlink DPCCH (Dedicated Physical Control Channel)/ DPCH (Dedicated Physical Channel) power ratio. 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.

654

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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. 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. Note: 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 Transmitters Properties dialogue. These values have to be manually modified when the option is changed.

7.7.4.2

Defining HSDPA Radio Bearers

In each cell, the scheduler selects the HSDPA resource per UE and per TTI. This HSDPA resource is called a TFRC (Transport Format Resource Combination) and is the set of parameters such as the transport format, the modulation scheme, and the number of used HS-PDSCH channels. In Atoll, the TFRC are referred to as HSDPA radio bearers. During a simulation, and for the HSDPA coverage prediction, Atoll selects a suitable HSDPA radio bearer and uses its RLC peak rate. The HSDPA radio bearer selection is based on UE capabilities (maximum number of HS-PDSCH channels, transport block size, modulation supported), cell capabilities (HSPA or HSPA+, MIMO system used, maximum number of HS-PDSCH channels), and reported CQI. The HSDPA Radio Bearer table lists the available HSDPA radio bearers. They can be classified into two categories: HSDPA bearers using QPSK and 16QAM modulations. They can be selected for users connected to HSPA and HSPA+ capable cells. HSDPA bearers using 64QAM modulation (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+). These HSDPA bearers can be allocated to users connected to cells with HSPA+ capabilities only.

You can create new HSDPA radio bearers and modify existing ones by using the HSDPA Radio Bearer table. To open the HSDPA Radio Bearer table: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select HSDPA Radio Bearer from the context menu. The HSDPA Radio Bearer table appears with the following information: Radio Bearer Index: The bearer index number. Transport Block Size (Bits): The transport block size in bits. Number of HS-PDSCH Channels Used: The number of HS-PDSCH channels used. Modulation: The modulation used. You can choose between QPSK, 16QAM or 64QAM. RLC Peak Rate (bps): The RLC peak rate represents the peak rate without coding (redundancy, overhead, addressing, etc.).

7.7.4.3

Defining HSUPA Radio Bearers

In each cell, the scheduler selects the HSUPA resource per UE, per Node B, and per user service. This HSUPA resource is called a TFC (Transport Format Combination) and requires a defined ratio of E-DPDCH power over DPCCH power. This ratio is modelled as the required E-DPDCH EcNt. The combination of the TFC and the power offset is modelled in Atoll as HSUPA radio bearers. During a simulation, and for the HSUPA coverage prediction, Atoll selects a suitable HSUPA radio bearer. The HSUPA radio bearer selection is based on UE capabilities (maximum number of E-DPDCH codes, smallest spreading factor, TTI length, and modulation supported), cell capabilities (HSPA or HSPA+), and the required E-DPDCH EcNt. The HSUPA Radio Bearer table lists the available HSUPA radio bearers. They can be classified into two categories: HSUPA bearers using QPSK modulation. They can be selected for users connected to HSPA and HSPA+ capable cells. HSUPA bearers using 16QAM modulation (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+). These HSUPA bearers can be allocated to users connected to cells with HSPA+ capabilities only.

To open the HSUPA Radio Bearer table: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select HSUPA Radio Bearer from the context menu. The HSUPA Radio Bearer table appears: Radio Bearer Index: The bearer index number. TTI Duration (ms): The TTI duration in ms. The TTI can be 2 or 10 ms.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

655

Atoll User Manual Transport Block Size (Bits): The transport block size in bits. Number of E-DPDCH Codes: The number of E-DPDCH channels used. Minimum Spreading Factor: The minimum spreading factor used. Modulation: The modulation used. You can choose between QPSK or 16QAM. RLC Peak Rate (bps): The RLC peak rate represents the peak rate without coding (redundancy, overhead, addressing, etc.).

7.7.5

Site Equipment
In this section, the following are described: "Creating Site Equipment" on page 656 "Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer" on page 657.

7.7.5.1

Creating Site Equipment

To create a new piece of UMTS site equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Sites folder. The context menu appears. 3. Select Equipment > Open Table from the context menu. The Equipment table appears. 4. In the Equipment table, each row describes a piece of equipment. For information on working with data tables, see "Working with Data Tables" on page 53. For the new piece of UMTS equipment you are creating, enter the following: Name: The name you enter will be the one used to identify this piece of equipment. Manufacturer: The name of the manufacturer of this piece of equipment. MUD factor: Multi-User Detection (MUD) is a technology used to decrease intra-cell interference in the uplink. MUD is modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation. In case MUD is not supported by equipment, enter 0 as value. Rake receiver efficiency factor: This 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 studies. 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. Note: The rake efficiency factor used to model the recombination in downlink can be set in terminal properties.

Carrier selection: Carrier selection refers to the carrier selection method used during the transmitter admission control in the mobile active set. The selected strategy is used in simulations when no carrier is specified in the properties of the service (all the carriers can be used for the service) or when the carrier specified for the service is not used by the transmitter. On the other hand, the specified carrier selection mode is always taken into account in predictions (AS analysis and coverage studies). 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. Note: By setting an option in the atoll.ini file, you can prevent Atoll from allocating inter-carrier and inter-technology neighbours to cells located on sites whose equipment does not support the compressed mode. For more information, see the Administrator Manual.

Overhead Iub Throughput/Cell (kbps): The overhead Iub throughput per cell corresponds to the Iub throughput required by the cell for common channels in the downlink. HSDPA Iub Backhaul Overhead (%): The HSDPA Iub backhaul overhead corresponds to the percentage of the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corresponds to the Iub backhaul throughput required by the HSDPA user for HS Channels in the downlink.

656

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 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. ) to close the table.

5. Click the Close button (

7.7.5.2

Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer
The number of channel elements and the Iub backhaul throughput consumed by an R99 bearer user depend on the site equipment, on the R99 radio bearer, and the link direction (up or down). The number of channel elements and the Iub backhaul throughput consumed can be defined for UMTS simulations. To define channel element and Iub backhaul throughput consumption during UMTS simulations: 1. Click the Data tab in the Explorer window. 2. Right-click the Sites folder. The context menu appears. 3. Select Equipment > R99 Resource Consumption from the context menu. The R99 Resource Consumption table appears. 4. 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. 5. Click the Close button ( ) to close the table.

7.7.5.3

Defining Resource Consumption per UMTS Site Equipment and HSUPA Radio Bearer
The number of channel elements and the Iub backhaul throughput consumed by a HSUPA bearer user in the uplink depend on the site equipment and on the HSUPA radio bearer. The number of channel elements and the Iub backhaul throughput consumed can be defined for UMTS simulations. To define channel element and Iub backhaul throughput consumption during UMTS simulations: 1. Click the Data tab in the Explorer window. 2. Right-click the Sites folder. The context menu appears. 3. Select Equipment > HSUPA Resource Consumption from the context menu. The HSUPA Resource Consumption table appears. 4. 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. 5. Click the Close button ( ) to close the table.

7.7.6

Receiver Equipment
In this section, the following are described: "Setting Receiver Height" on page 657 "Creating or Modifying Reception Equipment" on page 657 "HSDPA UE Categories" on page 659 "HSUPA UE Categories" on page 659.

7.7.6.1

Setting Receiver Height

When you make UMTS coverage predictions, you can define the height of the receiver. To define the height of the receiver: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Receiver tab. 5. Enter a receiver Height. This value will be used when calculating a UMTS coverage predictions and a point analysis. 6. Click OK.

7.7.6.2

Creating or Modifying Reception Equipment

In Atoll, reception equipment models the reception characteristics of user terminals and is used when you create a terminal. The graphs defined for each reception equipment entry are used for quality studies and for selecting HSDPA and HSUPA bearers.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

657

Atoll User Manual To create or modify reception equipment: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select Reception Equipment from the context menu. The Reception Equipment table appears. "Standard" is the default reception equipment type for all terminals. 5. Double-click the reception equipment type you want to modify. The reception equipment types Properties dialogue appears. Note: You can create a new reception equipment type by entering a name in the row marked with the New Row icon ( ) and pressing ENTER.

6. 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. R99 Bearer: Select an R99 bearer from the list. Mobility: Select a mobility type from the list. UL Target (dB): Enter or modify the uplink (EbNt) threshold. Uplink 2RX Diversity Gain (dB): Enter or modify the two-receiver uplink diversity gain in dB. Uplink 4RX Diversity Gain (dB): Enter or modify the four-receiver uplink diversity gain in dB. DL Target (dB): Enter or modify the downlink (EbNt) threshold. Downlink Open Loop Diversity Gain (dB): Enter or modify the downlink open loop diversity gain in dB. Downlink Closed Loop Diversity Gain (dB): Enter or modify the downlink closed loop diversity gain in dB.

7. Click the Quality Graphs tab. 8. Ensure that a Quality Indicator has been chosen for each R99 Bearer. You can edit the values in the DL and UL Quality Indicator Tables by clicking directly on the table entry, or by selecting the Quality Indicator and clicking the Downlink Quality Graphs or the Uplink Quality Graphs buttons. The DL and UL Quality Indicator tables describe the variation of the quality indicator as a function of the measured parameter (as defined in the Quality Indicators table). The Uplink and Downlink Quality Graphs are used for quality studies. 9. Click the HSDPA Bearer Selection tab. 10. Ensure that the values for each Mobility in the CQI Table and the Best HSDPA Bearer Table have been entered. You can edit the values in the CQI Table and the Best HSDPA Bearer Table by clicking directly on the table entry, or by selecting the Mobility and clicking the CQI Graph or the Best Bearer Graph buttons. The CQI table describes the variation of the CPICH CQI as a function of the CPICH Ec/Nt (or the variation of HSPDSCH CQI as a function of the HS-PDSCH Ec/Nt); the values displayed depend on the calculation parameter you have selected in the Global Parameters tab of the Transmitters Properties dialogue (for more information, see "The Options on the Global Parameters Tab" on page 653). The Best HSDPA Bearer table describes the index of the best HSDPA bearer as a function of the HS-PDSCH CQI. The CQI graphs and best bearer graphs are used in the simulation and in the HSDPA prediction study to model fast link adaptation (selection of the HSDPA bearer). The supplier RRM (radio resource management) strategy can be taken into account using the Best HSDPA Bearer table, for example: You can define several pieces of reception equipment with a separate table for each. You can reserve low bearer indexes for poor-performance reception equipment and higher bearer indexes for high-performance equipment. You can specify a graph for each mobility. Here, you can reserve low bearer indexes for high speeds and higher bearer indexes for low speeds. You can also give priority to either one user by assigning him a high bearer index or to all users by assigning them low bearer indexes.

11. Click the HSDPA Quality Graphs tab. 12. Ensure that a Quality Indicator has been chosen for each Radio Bearer Index. You can edit the values in the DL Quality Indicator Table by clicking directly on the table entry, or by selecting the Quality Indicator and clicking the Downlink Quality Graph button. The Downlink Quality table describes the variation of the BLER as a function of the HS-PDSCH EcNt. It is used to calculate the application throughput for the HSDPA coverage prediction. 13. Click the HSUPA Bearer Selection tab.

658

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks 14. Ensure that, for each Radio Bearer Index and Mobility pair, you have entered a value for the Number of Retransmissions and for the Requested EcNt Threshold. You can edit the values in the Early Termination Probabilities table by clicking directly on the table entry, or by selecting the Radio Bearer Index and clicking the Early Termination Probability Graph button. The Number of Retransmissions and the Requested EcNt Threshold values are used in the simulation and in the HSUPA prediction to model noise rise scheduling and in the selection of the HSUPA radio bearer. The Early Termination Probabilities table describes the variation of the early termination probability as a function of the number of retransmissions. It is used in the HSUPA prediction to calculate the average RLC throughput and the average application throughput when HARQ (Hybrid Automatic Repeat Request) is used. 15. Click the HSUPA Quality Graphs tab. 16. Ensure that a Quality Indicator has been chosen for each Radio Bearer Index and that there is a value defined for the Number of Retransmissions. You can edit the values in the UL Quality Indicator Table by clicking directly on the table entry, or by selecting the Quality Indicator and clicking the Uplink Quality Graph button. The Uplink Quality table describes the variation of the BLER as a function of the E-DPDCH EcNt. It is used to calculate the application throughput for the HSUPA coverage prediction. 17. Click the MIMO tab. 18. Ensure that, for each HSDPA Radio Bearer Index and Mobility pair, you have entered a value for the Number of Transmission Antennas Ports, for the Number of Reception Antennas Ports and for the Transmit Diversity Gain. You can edit the values in the Max Spatial Multiplexing Gains table by clicking directly on the table entry, or by selecting the Mobility and clicking the Max Spatial Multiplexing Gain Graph button. 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 660.

Note:

No MIMO gain (diversity, spatial multiplexing) is applied if N Ant = N Ant = 1 .

TX

RX

19. Click OK to close the reception equipment types Properties dialogue.

7.7.6.3

HSDPA UE Categories
HSDPA user equipment capabilities are standardised into 22 different categories according to 3GPP specifications. To edit a UE category: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select HSDPA User Equipment Categories from the context menu. The HSDPA User Equipment Categories table appears. 5. The HSDPA User Equipment Categories table has the following columns: Category: The number identifying 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 TTI Used: 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.

7.7.6.4

HSUPA UE Categories
HSUPA user equipment capabilities are standardised into 7 different categories according to 3GPP specifications. To edit a UE category: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the UMTS Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select HSUPA User Equipment Categories from the context menu. The HSUPA User Equipment Categories table appears. 5. The HSUPA User Equipment Categories table has the following columns: Category: The number identifying the HSUPA UE category. Max Number of E-DPDCH Codes: The maximum number of E-DPDCH codes allowed for the category.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

659

Atoll User Manual 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.

7.7.7

Multiple Input Multiple Output Systems

Multiple Input Multiple Output (MIMO) systems which are supported by some HSDPA bearers (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+) use different transmission and reception diversity techniques. MIMO diversity systems can be roughly divided into the types described in the following sections, all of which are modelled in Atoll.

Transmit and Receive Diversity

Transmit or receive diversity uses more than one transmission or reception antenna to send or receive more than one copy of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining) at the receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, diversity improves the quality at the receiver. It is often used for the regions of a cell that have bad quality conditions. In Atoll, you can define whether a cell supports transmit diversity by selecting HSPA+ (Transmit Diversity) in cell properties (see "Cell Definition" on page 470). Diversity gains on downlink can be defined in the reception equipment for different numbers of transmission and reception antenna ports, mobility types and HSDPA bearers. For more information on downlink diversity gains, see "Creating or Modifying Reception Equipment" on page 657. Additional gain values can be defined per clutter class. For information on setting the additional downlink diversity gain for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 121. During calculations in Atoll, a user (mobile, pixel, or point receiver) using a MIMO-capable terminal, and connected to a cell that supports HSPA+ with transmit diversity, will benefit from the downlink diversity HS-PDSCH Ec/Nt gain.

Spatial Multiplexing
Spatial multiplexing uses more than one transmission antenna to send different signals (data streams) on each antenna. The receiver can also have more than one antenna for receiving different signals. When spatial multiplexing is used with M transmission and N reception antenna ports, the throughput over the transmitter-receiver link can be theoretically increased M or N times, depending on which is smaller, M or N. Spatial multiplexing improves the throughput (i.e., the channel capacity) for a given HS-PDSCH Ec/Nt, and is used for the regions of a cell that have sufficient HS-PDSCH EcNt conditions. In Atoll, you can define whether a cell supports spatial multiplexing by selecting HSPA+ (Spatial Multiplexing) in the cell properties (see "Cell Definition" on page 470). 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 657. 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 121. 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 Ec ----- Nt HS PDSCH ------------------------------------------ is the channel capacity at a given HS-PDSCH Ec/Nt for Log 2 1 + TX RX Min ( N Ant, N Ant )

Where CC MIMO =

TX Min ( N Ant,

RX N Ant )

TX RX Ec is a MIMO system using N Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 1 + ------ Nt HS PDSCH

the channel 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.

660

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

7.7.8

Conditions for Entering the Active Set

The mobile active set is the list of the transmitters to which the mobile is connected. The active set may consist of one or more transmitters; depending on whether the service supports soft handover and on the terminal active set size. Transmitters in the mobile active set must use a frequency band with which the terminal is compatible. It is, however, the quality of the pilot (EcI0) that finally determines whether or not a transmitter can belong to the active set. In order for a given transmitter to enter the mobile active set as best server, the pilot quality from this transmitter must exceed an upper threshold defined in the properties of the mobility type. In addition, the pilot quality must be the highest one. In order for a transmitter to enter the active set: It must use the same carrier as the best server transmitter. In Atoll, carriers are modelled using cells. For information on accessing cell properties, see "Creating or Modifying a Cell" on page 474. For a description of the properties of a cell, see "Cell Definition" on page 470. The pilot quality difference between the cell and the best server must not exceed the AS-threshold set per cell. For information on accessing the AS threshold defined for a given cell, see "Creating or Modifying a Cell" on page 474. 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 656.

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.

7.7.9

Modelling Shadowing
Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be greater and in 50% of the measured cases, the result will be worse. Atoll uses a model standard deviation with the defined cell edge coverage probability to model the effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. 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 UMTS projects, the standard deviation of the propagation model is used to calculate shadowing margins on signal levels. You can also calculate shadowing margins on EcI0 and EbNt values and the macro-diversity gain. For information on setting 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 121. Shadowing can be taken into consideration when Atoll calculates the signal level, EcI0, and EbNt for: A point analysis (see "Making a Point Analysis to Study the Profile" on page 488) A coverage prediction (see "Studying Signal Level Coverage" on page 490).

Atoll always takes shadowing into consideration when calculating a Monte-Carlo-based UMTS simulation. You can display the shadowing margins and the macro-diversity gain per clutter class. For information, see "Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class" on page 661.

7.7.9.1

Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class
To display the shadowing margins and macro-diversity gain per clutter class: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialogue appears (see Figure 7.369). 4. You can set the following parameters: Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macro-diversity gains: From Model: The model standard deviation. Atoll will display the shadowing margin of the signal level. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

661

Atoll User Manual 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.

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 DL 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 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.

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 dialogue.

Figure 7.369: The Shadowing Margins and Gains dialogue

7.7.10

Modelling Inter-Technology Interference

Analyses of UMTS networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a UMTS network. Atoll can take into account interference from coexisting networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modeled in Atoll: Interference received by mobiles on the downlink: Interference can be received by mobiles in a UMTS network on the downlink from external base stations and mobiles in the vicinity. Interference from external base stations (also called downlink-to-downlink interference) may be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (CDMA, TDMA, OFDM). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-Technology IRFs" on page 663. Interference from external mobiles (also called uplink-to-downlink interference) may be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your UMTS network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled in Atoll using the Inter-technology DL Noise Rise definable for each cell in the UMTS network. This noise rise is taken into account in all downlink interference-based calculations. However, this noise rise does not impact the calculation of the mobile reuse factor. For more information on the Inter-technology DL Noise Rise, see "Cell Definition" on page 470. 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 522.

662

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 7: UMTS HSPA Networks

Figure 7.370: Interference received by mobiles on the downlink Interference received by cells on the uplink: Interference can be received by cells of a UMTS network on the uplink from external base stations and mobiles in the vicinity. Interference from external base stations (also called downlink-to-uplink interference) may be created by insufficient separation between the downlink frequency used by the external network and the uplink frequency used by your UMTS network. Such interference may also come from co-existing TDD networks. Interference from external mobiles (also called uplink-to-uplink interference) may be created by the use of same or nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possible to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the Inter-technology UL Noise Rise definable for each cell in the UMTS network. This noise rise is taken into account in uplink interference-based calculations in the simulation. However, this noise rise is not considered in predictions (AS Analysis and coverage prdeictions) and does not impact the calculation of the cell reuse factor. For more information on the Inter-technology UL Noise Rise, see "Cell Definition" on page 470.

Figure 7.371: Interference received by cells on the uplink

7.7.10.1

Defining Inter-Technology IRFs

Interference received from external base stations on mobiles of your UMTS network can be calculated by Atoll. Atoll uses 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 An IRF depends on: The interfering technology (TDMA, CDMA, and OFDM) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).

IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your UMTS document, i.e., when Atoll is in co-planning mode. For more information on how to switch to co-planning mode, see "Switching to Co-planning Mode" on page 635. To define the inter-technology IRFs in the victim network: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Inter-technology IRFs from the context menu. The Inter-technology Interference Reduction Factors table appears. 4. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

663

Atoll User Manual Technology: Select the technology used by the interfering network. Interferer Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfering network. This channel width must be consistent with that used in the linked document. Victim Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfered network. This channel width must be consistent with that used in the main document. Reduction Factors (dB): Click the cell corresponding to the Reduction Factors (dB) column and the current row in the table. The Reduction Factors (dB) dialogue appears. Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document.

Notes: Reduction values must be positive. Undefined reduction factors are assumed to be very high values. Click OK. The interference reduction factors are stored.

You can, if you wish, link more than one Atoll document with your main document following the procedure described in "Switching to Co-planning Mode" on page 635. If the linked documents model networks using different technologies, you can define the interference reduction factors in your main document for all these technologies, and Atollwill calculate interference from all the external base stations in all the linked documents.

664

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8
CDMA2000 Networks

RF Planning & Optimisation Software

Atoll

Chapter 8: CDMA2000 Networks

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 and Rev.A 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 667. Allocating neighbours is explained in "Planning Neighbours" on page 727 and allocating PN offset codes is explained in "Planning PN Offsets" on page 739. In this section, you will also find information on how you can display information on base stations on the map and how you can use the tools in Atoll to study base stations. In "Studying Network Capacity" on page 746, using traffic maps to study network capacity is explained. Creating simulations using the traffic map information and analysing the results of simulations is also explained. Using drive test data paths to verify the network is explained in "Verifying Network Quality" on page 772. How to filter imported pilot mobile data paths, and how to use 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
handoff radio configuration reverse link forward link

Atoll handover terminal uplink (UL) downlink (DL)

8.1

Planning and Optimising CDMA Base Stations

As described in "Chapter 2: Starting an Atoll Project", you can start an Atoll document from a template, with no sites, or from a database with a set of sites. As you work on your Atoll document, you will still need to create sites and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such as the TMA, feeder cables, etc. In a CDMA project, you must also add cells to each transmitter. A cell refers to the characteristics of a carrier on a transmitter.

Antenna
- Azimuth - Mechanical tilt

TMA Antenna
- Height

Feeder Cable

BTS
- BTS noise figure - Power

Site
- X, Y coordinates

Figure 8.372: A transmitter Atoll lets you create one site, transmitter, or cell at a time, or create several at once by creating a station template. Using a station template, you can create one or more base stations at the same time. In Atoll, a base station refers to a site with its transmitters, antennas, equipment, and cells.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

667

Atoll User Manual 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 studies, such as effective service area, noise, or handoff status predictions, on the network. In this section, the following are explained: "Creating a CDMA Base Station" on page 668 "Creating a Group of Base Stations" on page 680 "Modifying Sites and Transmitters Directly on the Map" on page 681 "Display Tips for Base Stations" on page 681 "Creating a Repeater" on page 682 "Creating a Remote Antenna" on page 685 "Setting the Working Area of an Atoll Document" on page 687 "Studying a Single Base Station" on page 687 "Studying Base Stations" on page 691 "Planning Neighbours" on page 727 "Planning PN Offsets" on page 739.

8.1.1

Creating a CDMA Base Station

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

8.1.1.1

Definition of a Base Station

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

8.1.1.1.1

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

Figure 8.373: New Site dialogue

668

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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.

Tip:

While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.

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 wish. If an altitude is specified here, Atoll will use this value for calculations. Comments: You can enter comments in this field if you wish. 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.

The Equipment tab:

Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equipment" on page 801. If no equipment is assigned to the site, Atoll considers the following default values: Rake efficiency factor = 1 MUD factor = 0 Carrier selection = reverse link minimum noise Forward link and reverse link overhead resources for common channels = 0 The option AS Restricted to Neighbours is not selected, the option Pool of Shared CEs is not selected, the option Power Pooling Between Transmitters is not selected and Atoll uses one channel element on the forward link or reverse link for any service during power control simulation.

8.1.1.1.2

Transmitter Description
The parameters of a transmitter can be found in the transmitters Properties dialogue. When you create a transmitter, the Properties dialogue has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Properties dialogue has three additional tabs: the Cells tab (see "Cell Definition" on page 671), the Propagation tab (see "Assigning a Propagation Model to One Transmitter" on page 695), and the Display tab (see "Display Properties of Objects" on page 32). The General tab: Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names transmitters, see the Administrator Manual. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site on which the transmitter will be located. For information on the site Properties dialogue, see "Site Description" on page 668. You can click the New button to create a new site on which the transmitter will be located. Frequency Band: You can select a Frequency Band for the transmitter. Once you have selected the frequency band, you can click the Browse button ( ) to access the properties of the band. For information on the frequency band Properties dialogue, see "Defining Frequency Bands" on page 798. Under Antenna Position, you can modify the position of the antennas (main and secondary): Relative to Site: Select this option if you wish 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 wish to enter the coordinates of the antenna positions, and enter the x-axis and y-axis coordinates, X and Y, respectively.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

669

Atoll User Manual The Transmitter tab (see Figure 8.374):

Figure 8.374: Transmitter dialogue - Transmitter tab Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder of the Data tab. Note: 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 prediction studies 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 BTS Noise Figure for Transmitters" on page 148. You can assign equipment by using the Equipment Specifications dialogue which appears when you click the Equipment button.

On the Equipment Specifications dialogue (see Figure 8.375), the equipment you select and the gains and losses you define are used to set the transmitter noise figure and the total transmitter reverse link and forward link 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 147. 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 147. BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defining BTS Equipment" on page 148. Feeder Length: You can enter the feeder length at transmission and reception. Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value you enter must be positive. Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter must be positive.

670

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Figure 8.375: The Equipment Specifications dialogue Note: Any loss related to the noise due to a transmitters repeater is included in the calculated reception 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 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. For information on working with data tables, see "Working with Data Tables" on page 53.

8.1.1.1.3

Cell Definition
In Atoll, a cell is defined as a carrier, with all its characteristics, on a transmitter; the cell is the mechanism by which you can configure a CDMA multi-carrier network. In other words, a transmitter has one cell for every carrier. When you create a transmitter, Atoll reminds you to create at least one cell for the transmitter. The following 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. You can, if you wish, modify these values. The properties of a CDMA cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned. The Cells tab has the following options: 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. 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/I0 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. - Inter-technology 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 the simulation. It is not used in predictions (AS Analysis and coverage predictions). In predictions, Atoll calculates the uplink total interference from the UL load factor which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-Technology Interference" on page 806.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

671

Atoll User Manual Inter-technology DL Noise Rise: This noise rise represents the interference created by mobiles of an external network on the mobiles served by this cell on the downlink. This noise rise will be taken into account in all downlink interference-based calculations involving this cell. For more information on inter-technology interference, see "Modelling Inter-Technology Interference" on page 806. 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 dialogue in which you can set both intra-technology (intra-carrier and intercarrier) and inter-technology neighbours by clicking the Browse button ( neighbours, see "Planning Neighbours" on page 727. ). For information on defining

Tip:

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.

The following parameters are available for 1xRTT carriers: - Max Power (dBm): The maximum available forward link power for the cell. - Pilot Power (dBm): The pilot power. - Synchro Power (dBm): The synchronisation power. - Paging Power (dBm): The paging power. Note: 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 Transmitters folder on the Data tab of the Explorer window and selecting Properties from the context menu. On the Global Parameters tab of the Properties dialogue, 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. Note: 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 Transmitters folder on the Data tab of the Explorer window and selecting Properties from the context menu. On the Global Parameters tab of the Properties dialogue, under DL Load, you can select % Pmax. The total power value is automatically converted and set as a percentage of the maximum power.

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 BTS always transmits at maximum power (the DL maximum power) unless it has no user to support. When there is no user, the BTS 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 = f(No. Users): 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. 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

The following parameters are available for 1xEV-DO carriers: -

672

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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. 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 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. Max No. of EV-DO Users: The maximum number of EV-DO carrier users that this cell can support at any given time.

8.1.1.2

Creating or Modifying a Base Station Element

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: "Creating or Modifying a Site" on page 673 "Creating or Modifying a Transmitter" on page 673 "Creating or Modifying a Cell" on page 674.

8.1.1.2.1

Creating or Modifying a Site

You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 668, through the sites Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create or modify a site: 1. If you are creating a new site: a. Click the Data tab in the Explorer window. b. Right-click the Sites folder. The context menu appears. c. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 8.373 on page 668). 2. If you are modifying the properties of an existing site: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Sites folder.

c. Right-click the site you want to modify. The context menu appears. d. Select Properties from the context menu. The sites Properties dialogue appears. 3. Modify the parameters described in "Site Description" on page 668. 4. Click OK.

8.1.1.2.2

Creating or Modifying a Transmitter

You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 669, through the transmitters Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create or modify a transmitter: 1. If you are creating a new transmitter: a. Click the Data tab in the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 8.374).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

673

Atoll User Manual 2. If you are modifying the properties of an existing transmitter: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Transmitters folder.

c. Right-click the transmitter you want to modify. The context menu appears. d. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Modify the parameters described in "Transmitter Description" on page 669. 4. Click OK. If you are creating a new transmitter, Atoll reminds you to create a cell. For information on creating a cell, see "Creating or Modifying a Cell" on page 674.

Tips: 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 right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. 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.

8.1.1.2.3

Creating or Modifying a Cell

You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Definition" on page 671, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Definition" on page 671. 7. Click OK.

Tips: If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 59), or import data into the table (see "Importing Tables from Text Files" on page 63). If you want to add a cell to an existing transmitter on the map, you can add the cell by rightclicking the transmitter and selecting New Cell from the context menu.

8.1.1.3

Placing a New Station Using a Station Template

In Atoll, a station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio toolbar, select a template from the list.

674

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 2. Click the New Transmitter or Station button ( ) in the Radio toolbar.

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.

Tips:

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 38. If you let the pointer rest over the station you have placed, Atoll displays its tip text with its exact coordinates, allowing you to verify that the location is correct.

You can also place a series of stations using a station template. You do this by defining an area on the map where you want to place the stations. Atoll calculates the placement of each station according to the defined hexagonal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 676. To place a series of stations within a defined area: 1. In the Radio toolbar, select a template from the list. 2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of stations created from the same station template.

Note:

If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this template is not defined. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 676.

3. Draw a zone delimiting the area where you want to place the series of stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. Atoll fills the delimited zone with new stations and their hexagonal shapes. Station objects such as sites and transmitters are also created and placed into their respective folders. Once you have created one or more stations, the hexagons describing their cell radius remain visible. You can choose not to display them. To hide the hexagons after creating stations using the Hexagonal Design button ( ) or the New Station button ( ):

On the Data tab, clear the display check box beside the Hexagonal Design folder.

You can work with the sites and transmitters in these stations as you work with any station object, adding, for example, another antenna to a transmitter.

Placing a Station on an Existing Site

When you place a new station using a station template as explained in "Placing a New Station Using a Station Template" on page 674, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place a station on an existing site: 1. On the Data tab, clear the display check box beside the Hexagonal Design folder. 2. In the Radio toolbar, select a template from the list. 3. Click the New Station button ( ) in the Radio toolbar.

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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

675

Atoll User Manual

8.1.1.4

Managing Station Templates

Atoll comes with CDMA station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio toolbar (see Figure 8.376).

Figure 8.376: The Radio toolbar In this section, the following are explained: "Creating or Modifying a Station Template" on page 676 "Copying Data from One Station Template to Another" on page 679 "Modifying a Field in a Station Template" on page 679 "Deleting a Station Template" on page 680.

8.1.1.4.1

Creating or Modifying a Station Template

When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. As well, you can modify the properties of any station template. To create or modify a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. You can now create a new station template or modify an existing one: To create a new station template: Under Station Templates, select the station template that most closely resembles the station template you want to create and click Add. The Properties dialogue appears. To modify an existing station template: Under Station Templates, select the station template whose properties you want to modify and click Properties. The Properties dialogue appears.

4. Click the General tab of the Properties dialogue. In this tab (see Figure 8.377), you can modify the following: the Name of the station template, the number of Sectors, i.e., the number of transmitters on the site, and the Hexagon Radius, i.e., the theoretical radius of the hexagonal area covered by each sector.

Figure 8.377: Station Template Properties dialogue General tab Under Main Antenna, you can modify the following: the antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Height of the antenna 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 Mechanical Downtilt, and the Additional Electrical Downtilt. 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 "Assigning a Propagation Model to One Transmitter" on page 695.

5. Click the Transmitter tab. In this tab (see Figure 8.378). You can modify the following:

676

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Active: If the transmitters in this station template are to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder of the Data tab. 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 prediction studies 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 BTS Noise Figure for Transmitters" on page 148. You can assign equipment by using the Equipment Specifications dialogue which appears when you click the Equipment button. For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 669.

Figure 8.378: Station Template Properties dialogue Transmitter tab 6. Click the CDMA tab. In this tab (see Figure 8.379), you modify the specifications of the Carriers (each corresponding to a cell) that each transmitter supports. For information on carriers and cells, see "Cell Definition" on page 671. You can select the Carrier numbers for each sector of the station template. To select the carriers to be added to the sectors of a base station created using this station template: i. Click the Browse button ( ). The Carriers per Sector dialogue appears.

ii. In the Carriers per Sector dialogue, select the carriers to be created for each sector of the station. iii. Click OK. Under PN Offset, you can define the Reuse Distance and the Domain of the pseudo noise offset. Under Power, you can define the Pilot, the Paging, and the Synchro powers, and the Idle Power Gain. Under Simulation Constraints, you can modify the Max Power, the Max DL Load (defined as a percentage of the maximum power), and the Max UL Load Factor. Under Load Conditions, you can modify the Total Transmitted Power and the UL Load Factor. Under Active Set, you can modify the Min Ec/Io and the T-Drop. Under Inter-technology Interference, you can set the DL Noise Rise and the UL Noise Rise. For more information on inter-technology interference, see "Modelling Inter-Technology Interference" on page 806. You can also modify the Number of Uplink and Downlink Channel Elements and select the Equipment.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

677

Atoll User Manual

Figure 8.379: Station Template Properties dialogue CDMA tab 7. Click the CDMA2000 tab. In this tab (see Figure 8.380), you modify additional specifications of the Carriers (each corresponding to a cell) that each transmitter supports. For information on carriers and cells, see "Cell Definition" on page 671. You can set the Power Reserved for Pooling. Under 1xRTT, you can modify the Pilot Power, the Paging Power, and the Synchro Power. Under 1xEV-DO, you can modify the Idle Power Gain, the Max. Number of EV-DO Channel Elements per Carrier, and you can modify the MUG (multi-user gain) table. Under 1xEV-DO, for rev.0, you can set the Noise Rise Threshold, the Acceptable Noise Rise Margin, and the DRC Error Rate. Under 1xEV-DO, for rev.A, you can set the Timeslot BCMCS, the Timeslot Control Channels, and the BCMCS Throughput.

Figure 8.380: Station Template Properties dialogue CDMA2000 tab

678

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 8. Click the Neighbours tab. In this tab (see Figure 8.381), you can modify the Max Number of Intra- and Inter-Carrier Neighbours and the Max Number of Inter-Technology Neighbours. For information on defining neighbours, see "Planning Neighbours" on page 727.

Figure 8.381: Station Template Properties dialogue Neighbours tab 9. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Sites table, or if you have defined an additional field in the Station Template Properties dialogue. 10. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.

8.1.1.4.2

Copying Data from One Station Template to Another

You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Station Templates from the context menu. The Station Templates table appears. 4. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy from and paste them into the row corresponding to the station template you want to modify.

8.1.1.4.3

Modifying a Field in a Station Template

To modify a field in a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Select the template in the Available Templates list. 4. Click the Fields button. 5. In the dialogue that appears, you have the following options: Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Types Data Table" on page 54) for it to appear as an option in the station template properties. To add a new field: i. Click the Add button. The Field Definition dialogue appears.

ii. Enter a Name for the new field. This is the name that will be used in database. iii. If desired, you can define a Group that this custom field will belong to. When you open an Atoll document from a database, you can then select a specific group of custom fields to be loaded from the database, instead of loading all custom fields. iv. In Legend, enter the name for the field that will appear in the Atoll document. v. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/ Time, and Currency. If you choose text, you can also set the field Size (in characters), and create a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER after each one. vi. Enter, if desired, a Default value for the new field. vii. Click OK to close the Field Definition dialogue and save your changes. Delete: To delete a user-defined field: i. Select the user-defined field you want to delete.

ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you close the dialogue. Properties: To modify the properties of a user-defined field: i. Select the user-defined field you want to modify.

ii. Click the Properties button. The Field Definition dialogue appears. iii. Modify any of the properties as desired. iv. Click OK to close the Field Definition dialogue and save your changes.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

679

Atoll User Manual 6. Click OK.

8.1.1.4.4

Deleting a Station Template

To delete a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Under Station Templates, select the station template you want to delete and click Delete. The template is deleted. 4. Click OK.

8.1.1.5

Duplicating of an Existing Base Station

You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the station you create will have the same site, transmitter, and cell parameter values as the original base station. Duplicating a station allows you to: 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.

To duplicate an existing base station: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Sites folder.

3. Right-click the site you want to duplicate. The context menu appears. 4. From the context menu, select one of the following: Select Duplicate > 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. 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.

You can now place the new base station on the map using the mouse. 5. In the map window, move the pointer over the map to where you would like to place the new base station. The exact coordinates of the pointers current location are visible in the Status bar.

Figure 8.382: Placing a new station

Tips:

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 38. If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact coordinates, allowing you to verify that the location is correct.

6. Click to place the duplicate base station. A new base station is placed on the map. The site, transmitters, and cells of the new 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 base station have the same settings as those of the original base station. All the remote antennas and repeaters of any transmitter on the original site are also duplicated. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate base station. For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 668.

8.1.2

Creating a Group of Base Stations

You can create base stations individually as explained in "Creating a CDMA Base Station" on page 668, or you can create one or several base stations by using station templates as explained in "Placing a New Station Using a Station Template" on page 674. However, if you have a large data-planning project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations.

680

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Note:

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 96.

You can import base station data in the following ways: Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. Important: The table you copy 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 59. Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files" on page 61. For information on importing table data, see "Importing Tables from Text Files" on page 63. Note: You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio toolbar. For information, see "Placing a New Station Using a Station Template" on page 674.

8.1.3

Modifying Sites and Transmitters Directly on the Map

In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu on the Data tab of the Explorer window. However, in a complex radio-planning project, it can be difficult to find the data object in the Data tab, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. If there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in "Chapter 1: The Working Environment": "Selecting One of Several Transmitters" on page 31 "Moving a Site Using the Mouse" on page 31 "Moving a Site to a Higher Location" on page 31 "Changing the Azimuth of the Antenna Using the Mouse" on page 31 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32.

8.1.4

Display Tips for Base Stations

Atoll allows to you to display information about base stations in a number of different ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object types data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information will lead to a cluttered display. For information on defining the label, see "Defining the Object Type Label" on page 35. Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip 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 every field in that object types data table, including from fields that you add. For information on defining the tooltips, see "Defining the Object Type Tip Text" on page 36. 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 "Defining the Display Type" on page 33.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

681

Atoll User Manual 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 "Defining the Display Type" on page 33.

8.1.5

Creating a Dual-Band CDMA Network

In Atoll, you can model a dual-band CDMA network, i.e., a network consisting of 1900 MHz and 700 MHz transmitters, in one document. Creating a dual-band CDMA network consists of the following steps: 1. Defining the two frequency bands in the document (see "Defining Frequency Bands" on page 798). 2. Selecting and calibrating a propagation model for each frequency band (see "Chapter 5: Managing Calculations in Atoll"). 3. Assigning a frequency band, with its propagation model, to each transmitter (see "Transmitter Description" on page 669). 4. Defining the frequency bands with which terminals are compatible (see "Modelling Terminals" on page 714).

8.1.6

Creating a Repeater
A repeater receives, amplifies, and re-transmits the radiated or conducted RF carrier in both the forward and reverse link. It has a donor side and a server side. The donor side receives the signal from a donor transmitter, repeater, or remote antenna. This signal may be carried by different types of links such as radio link or microwave link. The server side retransmits the received signal. Atoll models RF repeaters and microwave repeaters. The modelling focuses on: The additional coverage these systems provide to transmitters on the forward link. The reverse link total gain value in service area studies (effective service area and reverse link EbNt service area) and the noise rise generated at the donor transmitter by the repeater.

In this section, the following are explained: "Creating and Modifying Repeater Equipment" on page 682 "Placing a Repeater on the Map Using the Mouse" on page 683 "Creating Several Repeaters" on page 683 "Defining the Properties of a Repeater" on page 683 "Tips for Updating Repeater Parameters" on page 685 Note: Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor transmitter are amplified.

8.1.6.1

Creating and Modifying Repeater Equipment

You can define repeater equipment to be assigned to each repeater in the network. To create or modify repeater equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Repeaters > Equipment from the context menu. The Repeater Equipment table appears. 4. To create repeater equipment, enter the following in the row marked with the New Row icon ( a. Enter a Name and Manufacturer for the new equipment. b. Enter a Noise Figure. The repeater causes a rise in noise at the donor transmitter, so the noise figure is used to calculate the reverse link loss to be added to the donor transmitter reverse link losses. The noise figure must be a positive value. c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain using the buttons to the right of the Amplification box ( dialogue. ) on the General tab of the repeater Properties ):

e. Enter the maximum power that the equipment can transmit on the downlink in the 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.

682

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 5. To modify repeater equipment, change the parameters in the row containing the repeater equipment you wish to modify.

8.1.6.2

Placing a Repeater on the Map Using the Mouse

In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. For information on creating a remote antenna, see "Creating a Remote Antenna" on page 685. To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder of the Explorer windows Data tab, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Repeater from the menu. 4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tooltip and label display the same information as displayed for the donor. As well, its tooltip identifies the repeater and the donor. In the Explorer window, the repeater is found in the Transmitters folder of the Data tab under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 683. Note: You can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter or repeater. ) on the Radio toolbar.

8.1.6.3

Creating Several Repeaters

In Atoll, the characteristics of each repeater are stored in the Repeaters table. You can create several repeaters at the same time by pasting the information into the Repeaters table: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document. You can open the Repeaters table by rightclicking the Transmitters folder in the Data tab of the Explorer window and selecting Repeaters > Open Table from the context menu. Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

8.1.6.4

Defining the Properties of a Repeater

To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or from the Transmitters folder of the Explorer windows Data tab. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: You can change the Name of the repeater. By default, repeaters are named "RepeaterN" where "N" is a number assigned as the repeater is created. You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another repeater, or a remote antenna. Clicking the Browse button ( ) opens the Properties dialogue of the donor.

You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Properties dialogue of the site. You can enter a Position relative to site location, if the repeater is not located on the site itself. You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties dialogue of the equipment. You can change the Amplification gain. The amplification gain is used in the link budget to evaluate the repeater total gain.

4. Click the Donor Side tab. You can modify the following parameters: Under Donor-Repeater Link, select a Link Type. If you select Microwave Link, enter the Propagation Losses and continue with step 5. If you select Air Link, 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

683

Atoll User Manual 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. Important: If you want to create a remote antenna, you must select Optical Fibre Link. If you selected Air Link under Donor-Repeater Link, enter the following information under Antenna: i. Select a Model from the list. You can click the Browse button ( antenna. ) to access the properties of the

ii. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the transmitter as given by the DTM. iii. Enter the Azimuth and the Mechanical Downtilt. Note: You can click the Calculate button to update azimuth and downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.

If you selected Air Link 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 ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at Reception. 5. Click the Coverage Site tab. You can modify the following parameters: Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Data tab of the Explorer window) are calculated. Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before clicking the Calculate button. Atoll uses the forward link total gain values to calculate the signal level received from the repeater. The reverse link total gain value is considered in reverse link EbNt service area studies. The forward link total gain is applied to each power (pilot power, SCH power, etc.). It takes into account losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder losses). The reverse link total gain is applied to each terminal power. It takes into account losses between the donor transmitter and the repeater, donor part characteristics (donor antenna gain, transmission feeder losses), amplification gain and coverage part characteristics (coverage antenna gain and reception feeder losses). Under Antennas, you can modify the following parameters: i. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the site as given by the DTM.

ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the properties of the antenna. Then, enter the Azimuth and the Mechanical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater coverage side correspond to the characteristics of the donor. iii. 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. For information on working with data tables, see "Working with Data Tables" on page 53. Under Feeders, you can modify the following information: i. Select a Type of feeder from the list. You can click the Browse button ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at Reception. Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.

6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see "Chapter 5: Managing Calculations in Atoll".

684

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

8.1.6.5

Tips for Updating Repeater Parameters

Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: You can update the calculated azimuth and downtilt of the donor-side antennas of all repeaters by selecting Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu. You can update the reverse link and forward link total gains of all repeaters by selecting Repeaters > Calculate Gains from the Transmitters context menu. Note: You can prevent Atoll from updating the UL and DL total gains of selected repeaters by creating a custom field called "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 31) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32).

8.1.7

Creating a Remote Antenna

Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optic fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise. In certain cases, you may want to model a remote antenna with equipment or a remote antenna connected to a base station that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a Repeater" on page 682. In this section, the following are explained: "Placing a Remote Antenna on the Map Using the Mouse" on page 685 "Creating Several Remote Antennas" on page 686 "Defining the Properties of a Remote Antenna" on page 686 "Tips for Updating Remote Antenna Parameters" on page 687.

8.1.7.1

Placing a Remote Antenna on the Map Using the Mouse

In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the Transmitters folder of the Explorer windows Data tab or directly on the map. Note: Ensure that the remote antennas donor transmitter does not have any antennas.

2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Remote Antenna from the menu.

) on the Radio toolbar.

4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tooltip and label display the same information as displayed for the donor transmitter. As well, its tooltip identifies the remote antenna and the donor transmitter. In the Explorer window, the remote antenna is found in the Transmitters folder of the Data tab under its donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 686. Note: You can see to which base station the remote antenna is connected by clicking it; Atoll displays a link to the donor transmitter.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

685

Atoll User Manual

8.1.7.2

Creating Several Remote Antennas

In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. You can create several remote antennas at the same time by pasting the information into the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document. You can open the Remote Antennas table by right-clicking the Transmitters folder in the Data tab of the Explorer window and selecting Remote Antennas > Open Table from the context menu. Important: 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 59.

8.1.7.3

Defining the Properties of a Remote Antenna

To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or from the Transmitters folder of the Explorer windows Data tab. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: You can change the Name of the remote antenna. By default, remote antennas are named "RemoteAntennaN" where "N" is a number assigned as the remote antenna is created. You can change the Donor transmitter by selecting it from the Donor list. Clicking the Browse button ( opens the Properties dialogue of the donor transmitter. )

You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the site. You can enter a Position relative to site location, if the remote antenna is not located on the site itself. Note: 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 Cable Losses.

5. Click the Coverage Site 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 Data tab of the Explorer window) are calculated. Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before clicking the Calculate button. Atoll uses the forward link total gain values to calculate the signal level received from the remote antenna. The reverse link total gain value is considered in reverse link EbNt service area studies. The forward link total gain is applied to each power (pilot power, SCH power, etc.). It takes into account losses between the donor transmitter and the remote antenna. The reverse link total gain is applied to each terminal power. It takes into account losses between the donor transmitter and the remote antenna. Under Antennas, you can modify the following parameters: i. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude of the transmitter as given by the DTM. ) to access the

ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( properties of the antenna. Then, enter the Azimuth and the Mechanical Downtilt.

iii. 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. For information on working with data tables, see "Working with Data Tables" on page 53. Under Feeders, you can modify the following information: i. Select a Type of feeder from the list. You can click the Browse button ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at 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

686

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see "Chapter 5: Managing Calculations in Atoll".

8.1.7.4

Tips for Updating Remote Antenna Parameters

Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: You can update the reverse link and forward link total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from the Transmitters context menu. Note: You can prevent Atoll from updating the UL and DL total gains of selected remote antennas by creating a custom field called "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 31) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32).

8.1.8

Setting the Working Area of an Atoll Document

When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the sites that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of sites covered by a coverage prediction, each with its own advantages: Filtering the desired sites You can simplify the selection of sites to be studied by using a filter. You can filter sites according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 84. This enables you to keep only the base stations with the characteristics you want to study. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 74. Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated studies in order to see the effects of small changes in site configuration, the savings in time are considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot zone. The computation zone defines the area where Atoll calculates path loss matrices, coverage studies, Monte Carlo, power control simulations, etc., while the focus zone or hot spot zone is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 696. You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.

8.1.9

Studying a Single Base Station

As you create a site, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of sites can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the site you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of sites once you have optimised the settings for each individual site. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Atoll enables you to assign both a main propagation model, with a shorter radius and a higher resolution, and an extended propagation model, with a longer radius and a lower resolution. By using a calculation radius, Atoll limits the scope of calculations to a defined area. By using two matrices, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter, while reducing calculation time by using an extended matrix with a lower resolution. You can assign a propagation model to all transmitters at once, to a group of transmitters, or to a single transmitter. Assigning a propagation model is explained in "Assigning a Propagation Model" on page 693.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

687

Atoll User Manual In this section, the following are explained: "Making a Point Analysis to Study the Profile" on page 688 "Studying Signal Level Coverage" on page 689

8.1.9.1

Making a Point Analysis to Study the Profile

In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a CDMA user. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 693. To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Profile tab. In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you do a point analysis on all carriers, the values displayed will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier. In order to display the values of the 1xRTT carrier, you must select it. When you select the 1xRTT carrier, the point analysis displays the strength of the received pilot signal. 5. Select the Carrier to be displayed at the top of the Profile tab. The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude (in metres) is reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional attenuations peaks. The total attenuation is displayed above the main peak. The results of the analysis are displayed at the top of the Profile tab: The received signal strength of the selected transmitter The propagation model used The shadowing margin and the cell edge coverage probability used for calculating it The distance between the transmitter and the receiver.

You can change the following options at the top of the Profile tab: Transmitter: Select the transmitter from the list. Carriers: Select the carrier to be analysed. Display Geo Data Only: Select the Display Geo Data Only check box if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate nor display signal levels and losses.

6. Right-click the Profile tab to choose one of the following commands from the context menu: Properties: Select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. You can change the following: - Change the X and Y coordinates to change the present position of the receiver. - Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Select Signal Level, Path loss, and Total losses from the Result Type list. - You can select the Indoor Coverage check box to add indoor losses. Link Budget: Select Link Budget to display a dialogue with the link budget. Model Details: Select Model Details to display a text document with details on the displayed profile analysis. Model details are only available for the standard propagation model.

688

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Displays data, including received signal, shadowing margin, cell edge coverage probability, propagation model used, and transmitter-receiver distance.

You can select a different transmitter, and choose to display a profile only with a selected carrier.

Fresnel ellipsoid

Line of sight Figure 8.383: Point Analysis Tool - Profile tab

Attenuation with diffraction.

8.1.9.2

Studying Signal Level Coverage

As you are building your radio-planning project, you may want to check the coverage of a new site without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single site. A signal level coverage prediction displays the strength of the best signal received at each pixel of the area studied. Note: You can use the same procedure to study the signal level coverage of several sites by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 69.

To study the signal level coverage of a single base station: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder and select Group By > Site from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated.

Tip:

If you wish to study only transmitters by their status, at this step you could group them by status.

3. Select the propagation parameters to be used in the coverage prediction: a. Click the Expand button ( ) to expand the Transmitters folder.

b. Right-click the group of transmitters you want to study. The context menu appears. c. Select Open Table from the context menu. A table appears with the properties of the selected group of transmitters. d. In the table, you can configure two propagation models: one for the main matrix, with a shorter radius and a higher resolution, and another for the extended matrix, with a longer radius and a lower resolution. By calculating two matrices you can reduce the time of calculation by using a lower resolution for the extended matrix and you can obtain more accurate results by using propagation models best suited for each distance for the main and extended matrices. e. In the Main Matrix columns: f. Select a Main Propagation Model Enter a Main Calculation Radius and Main Resolution.

If desired, in the Extended Matrix columns: Select an Extended Propagation Model Enter an Extended Calculation Radius and Extended Resolution.

g. Close the table. 4. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. The Study Types dialogue lists the studies available. They are divided into Standard Studies, supplied with Atoll, and Customised Studies. Unless you have already created some customised studies, the Customised Studies list will be empty.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

689

Atoll User Manual 5. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 6. You can configure the following parameters in the Properties dialogue: General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient:

Size of the Coverage Prediction

City Centre City County State Country -

Display Resolution
5m 20 m 50 m 100 m According to the size of the country

Condition tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel (see Figure 8.384). At the top of the Condition tab, you can set the signal level range to be considered. In Figure 8.384, a signal level greater than or equal to -120 dBm will be considered. Under Server, select "All" to consider signal levels from all servers. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "All" to have all carriers taken into account. In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "All", the values displayed will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier. In order to make a coverage prediction on the transmitted power of the 1xRTT carrier, you must select the carrier. When you select the 1xRTT carrier, the coverage prediction displays the strength of the received pilot signal.

Figure 8.384: Condition settings for a signal level coverage prediction Display tab: You can modify how the results of the coverage prediction will be displayed. Under Display Type, select "Value Intervals." Under Field, select "Best signal level." Selecting "All" or "Best signal level" on the Conditions tab will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best signal level" necessitates, however, the longest time for calculation. You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 32. You can create a tooltip 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 tooltip. You can select the Add to Legend check box to add the displayed value intervals to the legend.

690

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Note:

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.

7. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level coverage prediction can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button ( ) beside the coverage prediction in the Predictions ). ), Atoll only calculates unlocked coverage predictions (

8.1.10

Studying Base Stations

When you make a coverage prediction on a group of base stations, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. The computation zone is the area covered by the rectangle defined by the calculation radius. When you set the propagation model, you can define the calculation radius. For information on setting the propagation model and defining the calculation radius, see "Assigning a Propagation Model" on page 693. Figure 8.385 gives an example of a computation zone. In Figure 8.385, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction.

Figure 8.385: An example of a computation zone Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main propagation model with a shorter radius (displayed with a blue square in Figure 8.385) and a higher resolution and an extended propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower resolution path loss matrices outside the area covered by the main propagation model.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

691

Atoll User Manual In this section, the following are explained: "Path Loss Matrices" on page 692 "Assigning a Propagation Model" on page 693 "The Calculation Process" on page 695 "Creating a Computation Zone" on page 696 "Setting Transmitters or Cells as Active" on page 696 "Signal Level Coverage Predictions" on page 697 "Analysing a Coverage Prediction" on page 701 "CDMA-Specific Coverage Predictions" on page 709 "Printing and Exporting Coverage Prediction Results" on page 727.

8.1.10.1

Path Loss Matrices

Path loss is caused by objects in the transmitter-receiver path and is calculated by the propagation model. In Atoll, the path loss matrices are needed for all base stations that are active, filtered and whose propagation zone intersects a rectangle containing the computation zone (for an explanation of the computation zone, see "Studying Signal Level Coverage" on page 689) and must be calculated before predictions and simulations can be made.

Storing Path Loss Matrices

Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: One file per transmitter with the extension LOS for its main path loss matrix A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.

To set the storage location of the path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss matrices and the location for the shared path loss matrices: Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are loading path loss matrices from a shared location, where you store your changes to shared path loss matrices. Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally. Note: Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private Directory.

Caution:

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. If you are working in a multi-user Atoll environment, ensure that the path to the Shared Directory is correct.

5. Click OK.

692

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check if the path loss matrices are invalid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the following display options: Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.

The Available Results table lists the following information for each displayed path loss matrix: Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a boolean field indicating whether or not the path loss matrix is valid. Origin of Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed.

5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 8.386) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.

Figure 8.386: Path loss matrices statistics

8.1.10.2

Assigning a Propagation Model

In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 695, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 694, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 694, this is the propagation model that will be used for all transmitters, except for those to which you have assigned a propagation model either individually or as part of a group. Important: 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, 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 assigned to individual transmitters or to a group of transmitters. 3. If you have assigned a default propagation model for coverage predictions, as described in "Assigning a Default Propagation Model for Coverage Predictions" on page 695, this is the propagation model that will be used for all

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

693

Atoll User Manual transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following methods of assigning a propagation model are explained: "Assigning a Propagation Model to All Transmitters" on page 694 "Assigning a Propagation Model to a Group of Transmitters" on page 694 "Assigning a Propagation Model to One Transmitter" on page 695 "Assigning a Default Propagation Model for Coverage Predictions" on page 695.

Assigning a Propagation Model to All Transmitters

In Atoll, you can choose a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

6. If desired, under Extended Matrix: Select a Propagation Model Enter a Radius and Resolution.

7. Click OK. The selected propagation models will be used for all transmitters. Note: Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 695 will override this entry.

Assigning a Propagation Model to a Group of Transmitters

Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. From the Group by submenu of the context menu, select the property by which you want to group the transmitters. The objects in the folder are grouped by that property. Note: You can group transmitters by several properties by using the Group By button on the Properties dialogue. For more information, see "Advanced Grouping" on page 70.

4. Click the Expand button (

) to expand the Transmitters folder.

5. Right-click the group of transmitters to which you want to assign a main and extended propagation model. The context menu appears. 6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected group. For each transmitter, you can set the propagation model parameters in the following columns: Main Propagation Model Main Calculation Radius (m) Main Resolution (m) Extended Propagation Model Extended Calculation Radius (m) Extended Resolution (m)

7. To enter the same values in one column for all transmitters in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells.

694

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Note:

If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

Assigning a Propagation Model to One Transmitter

If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

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

8. Click OK. The selected propagation models will be used for the selected transmitter.

Assigning a Default Propagation Model for Coverage Predictions

You can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters whose main propagation model is "(Default model)." To assign a default propagation model for coverage predictions: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Predictions tab. 5. Select a Default Propagation Model from the list. 6. Enter a Default Resolution. When you create a new coverage prediction, the resolution by default is the value you have entered here.

Tip:

By making the necessary entry in the atoll.ini file, if you clear the value entered in the Resolution box when you create a coverage prediction, Atoll will calculate the coverage prediction using the currently defined default resolution. That way, if you have many coverage predictions, you can change their resolution by changing the default resolution and recalculating the coverage predictions. Atoll will then calculate them using the updated resolution. For information on changing entries in the atoll.ini file, see the Administrator Manual.

7. Click OK. The selected propagation model will be used for coverage predictions for all transmitters whose main propagation model is "(Default model)."

8.1.10.3

The Calculation Process

When you create a coverage prediction and click the Calculate button ( ), Atoll follows the following process: 1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button ( ). ) beside the coverage prediction 3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( in the Predictions folder.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

695

Atoll User Manual

Notes: You can stop any calculations in progress by clicking the Stop Calculations button ( the toolbar. ) in

When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.

8.1.10.4

Creating a Computation Zone

To create a computation zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Computation Zone folder. The context menu appears. 4. Select Draw from the context menu. 5. Draw the computation zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. The computation zone is delimited by a red line. If you clear the computation zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a computation zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and selecting Use as > Computation Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a computation zone the size of the map window by selecting Fit to Map Window from the context menu. Note: You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: Saving the computation zone in the user configuration: For information on exporting the computation zone in the user configuration, see "Exporting a User Configuration" on page 79. Exporting the computation zone: You can export the computation zone by rightclicking the Focus Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

8.1.10.5

Setting Transmitters or Cells as Active

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Before you define a coverage prediction, you must ensure that all the transmitters on the sites you wish to study have been activated. In the Explorer window, active transmitters are indicated with a red icon ( ) in the Transmitters folder and with the defined colour on the map and inactive transmitters are indicated with an empty icon ( )in the Transmitters folder and on the map. In Atoll, you can also set individual cells on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zones context menu. To set an individual transmitter as active: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter you want to activate. The context menu appears. 4. Select Activate Transmitter from the context menu. The transmitter is now active.

696

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks To set more than one transmitter as active using the Transmitters context menu: 1. Click the Data tab of the Explorer window. 2. Select the transmitters you want to set as active: To set all transmitters as active, right-click the Transmitters folder. The context menu appears. To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and right-click the group of transmitters you want to set as active. The context menu appears.

3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one cell as active using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cells parameters in a second row. 4. For each cell that you want to set as active, select the check box in the Active column. To set transmitters as active using a zone: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder.

3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. Note: If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 41.

4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see "Chapter 5: Managing Calculations in Atoll". Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects. Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the Atoll computing server application on other workstations or on servers. Once the computing server application is installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on the network. For information on distributed calculations, see the Administrator Manual.

8.1.10.6

Signal Level Coverage Predictions

Atoll offers a series of standard coverage predictions that are common to all radio technologies. Coverage predictions specific to CDMA are covered in "CDMA-Specific Coverage Predictions" on page 709. Once you have created a coverage prediction, you can use the coverage predictions context menu to make the coverage prediction into a customised study which will appear in the Study Types dialogue. You can also select Duplicate from the coverage predictions context menu to create a copy. By duplicating an existing coverage prediction that has the parameters you wish to study, you can create a new coverage prediction more quickly. 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 import 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 "Exporting a User Configuration" on page 79. The following standard coverage predictions are explained in this section: "Making a Coverage Prediction by Signal Level" on page 697 "Making a Coverage Prediction by Transmitter" on page 699 "Making a Coverage Prediction on Overlapping Zones" on page 700.

8.1.10.6.1

Making a Coverage Prediction by Signal Level

A coverage prediction by signal level allows you to predict the best signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by signal level: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Signal Level and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

697

Atoll User Manual the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.387). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 8.387, a signal level greater than or equal to -120 dBm will be considered. Under Server, select "All" to consider all servers. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "All" to have all carriers taken into account. In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "All", the values displayed will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier. In order to make a coverage prediction on the transmitted power of the 1xRTT carrier, you must select the carrier. When you select the 1xRTT carrier, the coverage prediction displays the strength of the received pilot signal.

Figure 8.387: Condition settings for a coverage prediction by signal level 7. Click the Display tab. 8. Choose to display the results by best signal level. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. Selecting "All" or "Best Signal Level" on the Conditions tab will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. 9. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 8.388).

698

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Figure 8.388: Coverage prediction by signal level

8.1.10.6.2

Making a Coverage Prediction by Transmitter

A coverage prediction by transmitter allows the user to predict which server is the best at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by transmitter: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Transmitter and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.387). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 8.387, a signal level greater than or equal to -120 dBm or greater then -85 dBm will be considered. Under Server, select "Best signal level." You can also define a Margin. Atoll will then consider the best signal level on each pixel and any other signal level within the defined margin of the best one. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "All" to have all carriers taken into account.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

699

Atoll User Manual

Figure 8.389: Condition settings for a coverage prediction by transmitter 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Note: 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.

8.1.10.6.3

Making a Coverage Prediction on Overlapping Zones

Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction of overlapping zones on the signal level, path loss, or total losses within a defined range. To make a coverage prediction on overlapping zones: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Overlapping Zones and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.390). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 8.390, a signal level greater than or equal to -120 dBm will be considered. Under Server, select "Best signal level" and define a Margin. Atoll will then consider the best signal level on each pixel and any other signal level within the defined margin of the best one. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "All" to have all carriers taken into account. In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "All", the values displayed will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier. In order to make a coverage prediction on the transmitted power of the 1xRTT carrier, you must select the Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

700

Chapter 8: CDMA2000 Networks carrier. When you select the 1xRTT carrier, the coverage prediction displays the strength of the received pilot signal.

Figure 8.390: Condition settings for a coverage prediction on overlapping zones 7. Click the Display tab. For a coverage prediction on overlapping zones, the Display Type "Value Intervals" based on the Field "Number of Servers" is selected by default. Each overlapping zone will then be displayed in a colour corresponding to the number of servers received per pixel. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Note: By changing the parameters selected on the Condition 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.

8.1.10.7

Analysing a Coverage Prediction

Once you have completed a study, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 689). If several coverage predictions are visible on the map, it may be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which studies to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following tools are explained: "Displaying the Legend Window" on page 701 "Displaying Coverage Prediction Results Using Tooltips" on page 702 "Using the Point Analysis Reception Tab" on page 702 "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 703 "Viewing Coverage Prediction Statistics" on page 705 "Comparing Coverage Predictions: Examples" on page 706.

8.1.10.7.1

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

701

Atoll User Manual

8.1.10.7.2

Displaying Coverage Prediction Results Using Tooltips

You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltips. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 689). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined in the Display tab of the coverage prediction properties (see Figure 8.391).

Figure 8.391: Displaying coverage prediction results using tooltips

8.1.10.7.3

Using the Point Analysis Reception Tab

Once you have calculated the coverage prediction, you can use the Point Analysis tool to analyse the coverage prediction. Therefore, you will recreate the conditions of the coverage prediction. You can also use the Reception tab of the Point Analysis tool without a coverage prediction, to study reception at any point on the map as long as you have valid path loss matrices. 1. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 8.392). 3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue appears. 4. Recreate the conditions of the coverage prediction using the options in the Analysis Properties dialogue: Shadowing taken into account: If the coverage prediction using shadowing, select the Shadowing taken into account check box and enter a Cell Edge` Coverage Probability. Indoor Coverage: If the coverage prediction calculated indoor coverage, select the Indoor Coverage check box to add indoor losses.

You can also use the Analysis Properties dialogue to: Change the X and Y coordinates to change the present position of the receiver.

The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the colour of the transmitter it represents. In the Map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer location is displayed in the tool-tip. 5. At the top of the Reception tab, select the Carrier to be analysed.

Figure 8.392: Point Analysis Tool - Reception tab

702

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks You can also click the Results tab to get even more information than in the Reception tab. The results tab displays the current position and height of the receiver, the clutter class it is situated on, and for each transmitter, its signal level (or RSCP), its path loss, Ec/Io, C/I, DL and UL Eb/Nt values, PN Offsets.

8.1.10.7.4

Creating a Focus or Hot Spot Zone for a Coverage Prediction Report

The focus and hot spot zones define an area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spot zones in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the area where Atoll computes path loss matrices, coverage studies, Monte Carlo, power control simulations, etc., while the focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones. To define a focus zone or hot spot zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. Select Draw from the context menu. 5. Draw the focus or hot spot zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the focus or hot spot zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot zone by right-clicking it and selecting Use as > Focus Zone or Use as > New Hot Spot from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot spot zones, you can import the name given to each zone as well. Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map Window from the context menu. Notes: You can save the focus zone or hot spot zones, so that you can use it in a different Atoll document, in the following ways: Saving the focus zone in the user configuration: For information on exporting the focus zone in the user configuration, see "Exporting a User Configuration" on page 79. - Exporting the focus zone or hot spot zones: You can export the focus zone or hot spot zones by right-clicking the Focus Zone or the Hot Spot Zones folder on the Data tab of the Explorer window and selecting Export from the context menu.. You can include population statistics in the focus or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. -

8.1.10.7.5

Displaying a Coverage Prediction Report

Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage predictions Properties dialogue. The coverage prediction report is displayed in a table. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 58. Atoll bases the report on the area covered by the focus zone and hot spot zones; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot zone must be defined before you display a report; it is not necessary to define it before computing coverage. The focus or hot spot zone does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 703. Atoll can generate a report for a single prediction, or for all displayed predictions.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

703

Atoll User Manual To display a report on a single coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. The Open dialogue appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the focus zone if available or on the hot spot zones and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 4. 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. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. a appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. 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 spot zone: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. 2. Display the report as explained above. 3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears. 4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the population map: "Population" (Population): The number of inhabitants covered. "Population" (% Population): The percentage of inhabitants covered. "Population" (Population [total]: The total number of inhabitants inside the zone. to move it up or to move it up or

704

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Atoll saves the names of the columns you select and will automatically select them the next time you create a coverage prediction report. 5. Click OK. If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be value data (revenue, number of customers, etc.) or density data (revenue/km, number of customer/km, etc.). Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable Versus Non Integrable Data" on page 129.

8.1.10.7.6

Viewing Coverage Prediction Statistics

Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage study colours, interval steps, and shading as defined in the Display tab of the coverage predictions Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spot zones are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before computing coverage. For information on defining a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 703. To display the statistics on a coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction whose statistics you want to display. The context menu appears. 4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined by the focus zone (see Figure 8.396). Under Histogram Based on Covered Areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Detailed Results section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics Based on Study Conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

705

Atoll User Manual

Figure 8.393: Histogram of a coverage prediction by signal level

8.1.10.7.7

Comparing Coverage Predictions: Examples

Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison study coverage in one of the following ways: Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both studies 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 studies are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).

To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. 6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage between them. In this section, the following examples are explained: "Example 1: Studying the Effect of a New Base Station" on page 706 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 708.

Example 1: Studying the Effect of a New Base Station

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how you can verify if a newly added base station improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 697. The results are displayed in Figure 8.394. An area with poor coverage is visible on the right side of the figure.

706

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Figure 8.394: Signal level coverage prediction of existing network A new site is added, either by creating the site and adding the transmitters, as explained in "Creating a CDMA Base Station" on page 668, or by placing a station template, as explained in "Placing a New Station Using a Station Template" on page 674. Once the new base station has been added, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new base station (see Figure 8.395).

Figure 8.395: Signal level coverage prediction of network with new base station Now you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be displayed. You can choose among:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

707

Atoll User Manual Intersection Union Difference

In order to see what changes adding a new base station made, you should choose Difference. 5. Click OK to create the comparison. The comparison in Figure 8.396, shows clearly the area covered only by the new site.

Figure 8.396: Comparison of both signal level coverage predictions

Example 2: Studying the Effect of a Change in Transmitter Tilt

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 699. The results are displayed in Figure 8.397. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated with a red oval in the figure.

Figure 8.397: Coverage prediction by transmitter of existing network You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue. Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original coverage prediction by can be copied by selecting Duplicate from its context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see Figure 8.398).

708

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Figure 8.398: Coverage prediction by transmitter of network after modifications As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change in coverage, you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be displayed. You can choose among: Intersection Union Difference

In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The increase in coverage, seen in only the second coverage prediction, will be immediately clear. 5. Click OK to create the comparison. The comparison in Figure 8.399, shows clearly the increase in coverage due at the change in antenna tilt.

Figure 8.399: Comparison of both transmitter coverage predictions

8.1.10.8

CDMA-Specific Coverage Predictions

In CDMA, the quality of the signal and the size of the area that can be covered are influenced by the network load. As the network load increases, the area a cell can effectively cover decreases. For this reason, the network load must be defined in order to calculate CDMA-specific coverage predictions. If you have traffic maps, you can do a Monte-Carlo simulation to model power control and evaluate the network load for a generated user distribution. If you do not have traffic maps, Atoll can calculate the network load using the reverse link load factor and forward link total power defined for each cell.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

709

Atoll User Manual In this section, the CDMA-specific coverage predictions will be calculated using reverse link load factor and forward link total power parameters defined at the cell level. For the purposes of these studies, each pixel is considered a non-interfering user with a defined service, mobility type, and terminal. Before making a prediction, you will have to set the reverse link load factor and forward link total power and the parameters that define the services and users. These are explained in the following sections: "Setting the Reverse Link Load Factor and the Forward Link Total Power" on page 710. "Service and User Modelling" on page 710.

Several different types of CDMA-specific coverage predictions are explained in this section. The following quality studies are explained: "Making a Pilot Signal Quality Prediction" on page 716 "Studying Service Area (EbNt) Uplink and Downlink for 1xRTT" on page 717 "Studying Service Area (EbNt) Reverse Link for EV-DO" on page 719 "Studying Effective Service Area" on page 720.

The following noise studies, also coverage predictions, are explained: "Studying Forward Link Total Noise" on page 722 "Calculating Pilot Pollution" on page 723.

Another type of coverage prediction, the handoff study, is also explained: "Making a Handoff Status Coverage Prediction" on page 724.

You can also make a point analysis using the Point Analysis window. The analysis is calculated using reverse link load factor and forward link total power parameters defined at the cell level and provided for a user-definable probe receiver which has a terminal, a mobility and a service: "Making an AS Analysis" on page 725.

You can define a RSCP threshold to further define how results are displayed. Atoll uses the RSCP threshold to calculate coverage predictions and to make the AS analysis. Atoll checks which pixels have a pilot signal level which exceeds the defined RSCP threshold. Defining the RSCP threshold is explained in the following section: "Defining the RSCP Threshold" on page 716

Interferences coming from an external project can also be modelled and is explained in "Modelling Inter-Technology Interference" on page 806.

8.1.10.8.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 dialogue. However, you can set the reverse link load factor and the forward link total power for all cells using the Cells table. To set the reverse link load factor and the forward link total power using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Enter a value in the following columns: Total Power (dBm) UL Load Factor (%) For a definition of the values, see "Cell Definition" on page 671. 5. To enter the same values in one column for all cells in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

8.1.10.8.2

Service and User Modelling

The different services offered by a CDMA network require different data rates. Voice, for example, does not require a very high data rate whereas a data service being used for video conferencing requires a much higher data rate. CDMA responds to the differing data rate requirements with a range of carriers. For example, CDMA2000 can provide voice using 1xRTT. Data services, which require higher data rates than voice, can be provided using 1xRTT or 1xEV-DO Rev. 0 or Rev. A. For more information on the data rates available for voice, 1xRTT, and 1xEV-DO Rev. 0 and Rev. A, see "Data Rates Available for Services in CDMA" on page 800.

710

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Note:

You must define 1xEV-DO Rev. A radio bearers before you can model services using them. For information on defining 1xEV-DO Rev. A radio bearers, see "The 1xEV-DO Rev. A Radio Bearers" on page 801.

The CDMA2000 1xEV-DO Rev. 0 reverse link traffic channel allows five data rates. The CDMA2000 1xEV-DO Rev. A reverse link traffic channel can have many more different data rates. In Atoll, the CDMA2000 1xEV-DO Rev. A traffic channels are modelled using radio bearers. You must define 1xEV-DO Rev. A radio bearers before you can model services using them. In this section, the following are explained: "Modelling Services" on page 711 "Creating a Mobility Type" on page 714 "Modelling Terminals" on page 714.

Modelling Services
Services are the various services available to subscribers. CDMA2000 can provide voice using 1xRTT, and data using 1xRTT or 1xEV-DO. This section explains how to create a service. The options available depend on the type of service you create. Only the following parameters are used in coverage predictions: Voice-specific parameters: - Handoff capabilities - Max TCH Power (dBm) - UL Target (dB) - DL Target (dB) - Reception Equipment - UL Pilot Threshold (dB) - UL FCH/Pilot Offset (dB) - Body loss 1xRTT-specific parameters: - Handoff capabilities - Max TCH Power (dBm) - UL Target (dB) - DL Target (dB) - Reception Equipment - UL Pilot Threshold (dB) - UL FCH/Pilot Offset (dB) - UL SCH/Pilot Offset (dB) - Body loss 1xEV-DO-specific parameters: - Body loss

To create or modify a service: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. Note: You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.

5. Click the General tab. 6. Enter a Name for the service. Atoll proposes a name for the service, but you can change the name to something more descriptive. 7. Select a Type for the service. The options available depend on the type of service: Speech: Available for all CDMA projects. The following options are available for services with the type Speech: - 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. - 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

711

Atoll User Manual constant activity during connection. The activity factor is used to calculate the average power transmitted on the FCH. 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.

1xRTT Data: Only available for CDMA2000 projects. The following options are available for services with the type 1xRTT Data: - 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. - 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. - Application Throughput: The application throughput is not used for services with the type Speech. - Rate Probabilities SCH: Under Rate Probabilities SCH, you can enter the probability of the service having the specified rate, from 2 to 16 times the nominal rate (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 rate probabilities are used during simulations to determine the throughput requested by each user. - 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. 1xEV-DO Rev. 0 Data: Only available for CDMA2000 projects. The following options are available for services with the type 1xEV-DO Rev. 0 Data: - 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. - Downgrading Supported: Select the Downgrading Supported check box if the service supports downgrading on the reverse link. - Application Throughput: Under Application Throughput, enter a Scaling Factor between the application throughput and the RLC (Radio Link Control) throughput and a throughput Offset in kilobits per second. The application throughput is calculated by multiplying the RLC throughput by the scaling factor and subtracting the offset. - Rate Probabilities UL: Under Rate Probabilities UL, you can enter the probability of the service having the specified rate on the reverse link. The sum of the probabilities of the service having the specified rate must be lower than or equal to 1. The rate probabilities are used during simulations to determine the throughput requested by each user. If the service supports rate downgrading, you can define the probability of the service being upgraded or downgraded on the uplink (reverse link) for each 1xEV-DO Rev. 0 data rates. The probabilities are taken into account during the uplink load control part of simulations in order to determine if a user with a certain rate can be upgraded or downgraded. User rate downgrading and upgrading occurs when the cell is overor underloaded. The following table shows the data rate changes that are possible when a data rate is upgraded or downgraded. The probabilities are defined with a number from 1 to 255 for each rate.

Possible Rate Changes During Upgrading From

9.6 kbps 19.2 kbps 38.4 kbps 76.8 kbps

Possible Rate Changes During Downgrading From

153.6 kbps 76.8 kbps 38.4 kbps 19.2 kbps

To
19.2 kbps 38.4 kbps 76.8 kbps 153.6 kbps

To
76.8 kbps 38.4 kbps 19.2 kbps 9.6 kbps

Note:

If you want the algorithm to process 1xEV-DO Rev. 0 users as in previous versions of Atoll (i.e., downgrading 1xEV-DO Rev. 0 users with the highest rates, upgrading 1xEV-DO Rev. 0 users with the lowest rates) during uplink load control, you must enter 255 as the probability for each 1xEV-DO Rev. 0 data rate.

712

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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. 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.

1xEV-DO Rev. A Data: Only available for CDMA2000 projects. The following options are available for services with the type 1xEV-DO Rev. A Data: - Uplink Mode: The Uplink Mode describes 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 - 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. - Downgrading Supported: Select the Downgrading Supported check box if the service supports downgrading on the reverse link. - Application Throughput: Under Application Throughput, enter a Scaling Factor between the application throughput and the RLC (Radio Link Control) throughput and a throughput Offset in kilobits per second. The application throughput is calculated by multiplying the RLC throughput by the scaling factor and subtracting the offset. - Rate Probabilities UL: Under Rate Probabilities UL, you can enter the probability of the service having the specified rate. 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 rate probabilities are used during simulations to determine the throughput requested by each user. If the bearer is not defined under Rate Probabilities UL, it is assumed that there are no users using the bearer. - 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. - 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.

8. If you selected "1xEV-DO Rev. 0 Data" or "1xEV-DO Rev. A Data" as the Type in step 5., continue to step 9. If you selected "Speech" or "1xRTT Data" as the Type in step 5., an additional tab, the EbNt tab, is available. Click the EbNt tab. In the EbNt tab, you must define each possible combination of radio configuration, SCH factor and mobility. The SCH factor is the multiplying factor of the terminal nominal rate used to calculate the data rate. The following table lists the SCH factors available and the corresponding data rates.

SCH Factor
0 2 4 8 16

Data Rate
FCH nominal rate (FCH nominal rate) + 2*(FCH nominal rate) (FCH nominal rate) + 4*(FCH nominal rate) (FCH nominal rate) + 8*(FCH nominal rate) (FCH nominal rate) + 16*(FCH nominal rate)

For each combination, you must define the thresholds, targets, and gains: Terminal: Select a radio configuration from the list. SCH Factor: Enter an SCH factor. Min. and Max. TCH Power (dBm): Enter the minimum and maximum TCH power. The TCH can be equal to the FCH or the SCH, depending on the entered SCH factor. The values entered can be absolute or relative to the pilot power, depending on the option chosen on the Global Parameters tab of the Transmitters Properties dialogue, and have to be manually modified when the option is changed. The minimum and maximum traffic channel power make up the dynamic range for forward link power control. UL Target (dB): Enter the EbNt required on the reverse link for TCH. The TCH can be equal to the FCH or the SCH, depending on the entered SCH factor. The value defined for the UL Target is only used when the reverse link power control is based on traffic quality as set on the Global Parameters tab of the Transmitters Properties dialogue. DL Target (dB): Enter the EbNt required on the forward link for TCH. The TCH can be equal to the FCH or the SCH, depending on the entered SCH factor. UL Pilot Threshold (dB): Enter the pilot EcNt required on the reverse link. The value defined for the UL Pilot Threshold is only used when the reverse link power control is based on pilot quality as set on the Global Parameters tab of the Transmitters Properties dialogue.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

713

Atoll User Manual UL FCH/Pilot Offset (dB): Enter the FCH gain on the reverse link relative to the pilot. The value defined for the UL FCH/Pilot Offset is only used when the reverse link power control is based on pilot quality as set on the Global Parameters tab of the Transmitters Properties dialogue. UL SCH/Pilot Offset (dB): Enter the SCH gain on the reverse link relative to the pilot. The value defined for the UL SCH/Pilot Offset is only used when the reverse link power control is based on pilot quality as set on the Global Parameters tab of the Transmitters Properties dialogue. This value is not used for services of Type "Speech." Mobility: Select the mobility type for which the thresholds, targets, and gains are defined. If you select All, the thresholds, targets, and gains will be considered valid for all mobility types.

9. Click OK.

Creating a Mobility Type

In CDMA, information about receiver mobility is important to efficiently manage the active set: a mobile used by someone travelling a certain speed and a mobile used by a pedestrian will not necessarily be connected to the same transmitters. EcI0 requirements and the Ec/Nt threshold (used only by 1xEV-DO Rev 0) are largely dependent on mobile speed. The following parameters are used in coverage predictions: Delta Min. Ec/I0 Delta T_Drop Min. EcNt (UL)

To create or modify a mobility type: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.

3. Right-click the Mobility Types folder. The context menu appears. 4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears. Note: You can modify the properties of an existing mobility type by right-clicking the mobility type in the Mobility Types folder and selecting Properties from the context menu.

5. You can enter or modify the following parameters in the Mobility Types New Element Properties dialogue: Name: Enter or modify the descriptive name for the mobility type. 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. Max Rate = f(CI) (Rev 0): The graph of the data rate on the forward link as a function of (CI). This parameter is only used for CDMA2000 1xEV-DO Rev 0.

Under 1xEV-DO (Rev 0), enter or modify the following parameters: -

6. Click OK.

Modelling Terminals
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. The following parameters are used in coverage predictions: Reception equipment Main and secondary bands Maximum terminal power Gain and losses Noise figures Rho factor Voice and 1xRTT-specific parameters: Active set size on FCH and SCH Number of fingers DL rake factor Pilot power percentage Nominal rate Acknowledgement (ACK) channel gain Data Rate Control (DRC) channel gains

1xEV-DO Rev. 0-specific parameters:

714

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Data channel gains Acknowledgement (ACK) channel gain Radio Reverse Indicator (RRI) channel gain Data Rate Control (DRC) channel gains Data channel and Auxiliary pilot gains

1xEV-DO Rev. A-specific parameters:

To create or modify a terminal: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select New from the context menu. The Terminals New Element Properties dialogue appears. Note: You can modify the properties of an existing terminal by right-clicking the terminal in the Terminal folder and selecting Properties from the context menu.

5. Click the General tab. You can modify the following parameters: Name: You can change the name of the terminal. Type: You can change the type of equipment. Reception Equipment: Select a type of reception equipment from the list. You can create a new type of reception equipment by opening the Reception Equipment table. To open the Reception Equipment table, right-click the Terminals folder in the CDMA/CDMA2000 Parameters folder on the Data tab and select Reception Equipment from the context menu. Main Band: Select the frequency band with which the terminal is compatible and enter the terminal Noise Figure for the main frequency. Secondary Band: Select a second frequency band with which the terminal is compatible and enter the terminal Noise Figure for the second frequency. Leave the Secondary Band field empty if the terminal works only on one frequency band. Note: There are two different ways of defining dual-band terminals. Depending on the configuration, Atoll processes dual-band terminal users differently in the Monte-Carlo simulation. The first one consists of defining main and secondary frequency bands. This enables you to give a higher priority to one frequency band in the Monte-Carlo simulation (the main frequency band will have the higher priority). A user with such a dual-band terminal will be connected to transmitters using the main frequency band if carriers on this frequency band are not overloaded. In case of overloading, he will be connected to transmitters using the secondary frequency band. The second consists of selecting "All" as main frequency band. This means that the terminal works on any frequency band without any priority. In this case, the user can be connected to transmitters using any frequency band.

In coverage predictions, both configurations give the same results. The priority of frequency bands is not taken into account. Min. Power: Set the minimum transmission power. The minimum and maximum transmission power make up the dynamic range for reverse link power control in simulations. Max Power: Set the maximum transmission power. Gain: Set the antenna gain. Losses: Set the reception losses. Noise Figure: Set the terminal noise figure. 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 reverse link.

6. Click the 1xRTT tab. You can modify the following parameters: DL Rake Factor: Set the forward link rake factor. This enables Atoll to model the rake receiver on the forward link. Active Set Size: Set the active set size for both the fundamental channel (FCH) and the supplementary channel (SCH). The active set size is the maximum number of transmitters to which a terminal can be connected at one time. Note: For EV-DO-capable terminals, the FCH active set size also determines the active set size on the reverse link.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

715

Atoll User Manual 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. Nominal Rate: Set the nominal rate 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.

7. Click the 1xEV-DO Rev 0 tab (available only for CDMA2000). The values on this 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, DRC, and traffic data channels. You can modify the following parameters: Acknowledgement Channel Gain: Enter the gain on the acknowledgement (ACK) 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 Channel Gains (dB): Under Data Channel Gains, enter the gain for each supported reverse link rate on the traffic data channel.

8. Click the 1xEV-DO Rev A tab (available only for CDMA2000). The values on this 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, 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: 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 rates.

9. Click OK.

8.1.10.8.3

Defining the RSCP Threshold

To define the minimum pilot RSCP threshold: 1. Click the Data tab in the Explorer window. 2. Right-click on the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Predictions tab. 5. Under Calculation Limitation, enter a Min. Pilot RSCP Threshold. 6. Click OK.

8.1.10.8.4

Making Quality Studies

In Atoll, you can make several predictions to study the quality. In this section, the following quality predictions are explained: "Making a Pilot Signal Quality Prediction" on page 716 "Studying Service Area (EbNt) Uplink and Downlink for 1xRTT" on page 717 "Studying Service Area (EbNt) Reverse Link for EV-DO" on page 719 "Studying the Forward Link EV-DO Throughput" on page 718 "Studying Effective Service Area" on page 720 "Creating a Quality Study Using Quality Indicators" on page 721. Note: A table listing quality indicators (BER, BLER, etc.) to be analysed is available. Quality studies proposed by Atoll depend on quality indicators specified in this table.

Making a Pilot Signal Quality Prediction

A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is received sufficiently well to be added to the probe mobile active set. Atoll calculates the best pilot quality received on each pixel. Then, Atoll compares this value to the EcI0 threshold required to be the best server (Min Ec/I0 defined for the given cell plus the Delta Min Ec/I0 value defined for the selected mobility type). The pixel is coloured if the condition is fulfilled (in other words, if the best EcI0 is higher than the EcI0 threshold. To make a pilot signal quality prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Pilot Reception Analysis (Ec/I0) and click OK. The Pilot Reception Analysis (Ec/I0) Properties dialogue appears. 5. Click the General tab.

716

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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 710. 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 also select the Indoor Coverage check box to add indoor losses.

Figure 8.400: Load condition settings for a coverage prediction on pilot quality 7. 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 "Display Properties of Objects" on page 32. 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 quality relative to the EcI0 threshold: Select "Value Intervals" as the Display Type and "EcI0 Margin (dB)" as the Field.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying Service Area (EbNt) Uplink and Downlink for 1xRTT

Atoll calculates the traffic channel quality on FCH (as defined by EbNt) when using the maximum power allowed. In the coverage prediction, the forward link service area is limited by the maximum traffic channel power allowable on FCH per cell and by the pilot quality. The reverse link service area is limited by the maximum terminal power allowable on FCH and by the pilot quality. On both the forward and reverse links, if the received pilot is below the set threshold on a given pixel, Atoll will not display the traffic channel quality. Mobile macro-diversity is taken in consideration to evaluate the traffic channel quality (EbNt). Atoll combines the signal from each transmitter in the probe mobile active set.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

717

Atoll User Manual To make a coverage prediction on service area (Eb/Nt) forward link or reverse link: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select one of the following studies and click OK: Service Area (Eb/Nt) Uplink Service Area (Eb/Nt) Downlink

The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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 1xRTT-capable Terminal, a 1xRTT Service, and a Mobility, as defined in "Service and User Modelling" on page 710. 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. 7. 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 "Display Properties of Objects" on page 32. 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 Condition 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.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying the Forward Link EV-DO Throughput

Atoll calculates the pilot channel quality (as defined by EcNt) and, using the calculated EcNt, Atoll calculates the maximum data rate that can be supplied. To make a forward link EV-DO throughput coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Service Area (Eb/Nt) Downlink and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining

718

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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 710. You must also select an EV-DO Carrier. If you want the coverage prediction to calculate and display the average EV-DO Rev. A throughput on the forward link, select an EV-DO Rev. A-capable Terminal and an EV-DO Rev. A Service. Atoll will calculate and display the average EV-DO Rev. A throughput on the forward link using the early termination probabilities, defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request.) 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. 7. 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. The average EV-DO Rev. A throughput on the forward link: Select "Discrete values" as the Display Type and "Average Rate (Kbps)" as the Field.

For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying Service Area (EbNt) Reverse Link for EV-DO

Atoll calculates the reverse link EV-DO traffic channel quality (EbNt) with an uplink data channel rate of 9.6 kbps. The service area is limited by the maximum terminal power allowed and by the pilot quality. Mobile macro-diversity is taken in consideration to evaluate the traffic channel quality (EbNt). Atoll combines the signal from each transmitter in the probe mobile active set. To make a coverage prediction on service area (Eb/Nt) reverse link: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Service Area (Eb/Nt) Uplink and click OK. The Service Area (Eb/Nt) Uplink Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

719

Atoll User Manual You must select an EV-DO-capable Terminal, an EV-DO Service, and a Mobility, as defined in "Service and User Modelling" on page 710. You must also select an EV-DO Carrier. If you want the coverage prediction to calculate and display the average EV-DO Rev. A throughput, select an EV-DO Rev. A-capable Terminal and an EV-DO Rev. A Service. Atoll will calculate and display the average EV-DO Rev. A throughput using the early termination probabilities defined in the terminals reception equipment to model HARQ (Hybrid Automatic Repeat Request). 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. 7. 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 rate of 9.6 kbps. For information on defining display properties, see "Display Properties of Objects" on page 32. 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 Condition 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. The average EV-DO Rev. A throughput: Select "Discrete values" as the Display Type and "Average Rate (Kbps)" as the Field.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying Effective Service Area

The effective service area is the intersection zone between the pilot reception area, and the reverse link and forward link service areas. In other words, the effective service area prediction calculates where a service actually is available for the probe mobile. To make an effective service area prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Effective Service Area and click OK. the coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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 710. You must also select which Carrier is to be considered. 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. 7. Click the Display tab.

720

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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 with the nominal FCH rate for 1xRTT or with a data channel rate of 9.6 kbps for EV-DO. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Creating a Quality Study Using Quality Indicators

You can create a quality study based on a given quality indicators (BER, BLER, or FER). The coverage prediction will show for each pixel the measurement of the selected quality indicator. This type of coverage prediction is not available in the list of standard studies; you can, however, use quality indicators in a study by first ensuring that the parameters of the quality indicators have been correctly set and then creating a coverage prediction, selecting display parameters that use these quality indicators. Before you define the quality study, you must ensure that the parameters of the quality indicators have been correctly set. To check the parameters of the quality indicators: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select Quality Indicators from the context menu. The Quality Indicators table appears. For each quality indicator in the Name column, you can set the following parameters: Used for Packet Services: Select the Used for Packet Services check box if the quality indicator is to be used for 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.

5. Close the Quality Indicators table. 6. In the CDMA/CDMA2000 Parameters folder, right-click the Terminals folder. The context menu appears. 7. Select Reception Equipment from the context menu. The Reception Equipment table appears. "Standard" is the default reception equipment type for all terminals. 8. Double-click the reception equipment type for which you want to verify the correspondence between the measured quality and the quality indicator. The reception equipment types Properties dialogue appears. 9. Click the Quality Graphs tab. 10. Ensure that a Quality Indicator has been chosen for each 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. 11. Click OK to close the reception equipment types Properties dialogue. Once you have ensured that the parameters of the quality indicators have been correctly set, you can use the measured quality to create a quality study. How you define a coverage prediction according to the measured quality indicator, depends several parameters: The settings made in the Quality Indicators table The service you want to study The quality indicator you want to use (BER, BLER, or FER) The coverage prediction you want to use (Pilot Reception Analysis, the Service Area Downlink, or Service Area Uplink).

In the following example, you will create a quality study showing BLER, for a user on foot, and with a 1xRTT data service. To create a quality study showing BLER for a user on foot, and with a 1xRTT data service: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Service Area (EbNt) Downlink and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

721

Atoll User Manual the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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. 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

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).

8.1.10.8.5

Studying Noise
Atoll has several coverage predictions that enable you to study the forward link total noise, forward link noise rise or pilot pollution. In this section, the following noise predictions are explained: "Studying Forward Link Total Noise" on page 722 "Calculating Pilot Pollution" on page 723 "Studying Inter-Technology Downlink Noise" on page 724.

Studying Forward Link Total Noise

In the forward link total noise prediction, Atoll calculates and displays the areas where the forward link total noise or the forward link noise rise exceeds a set threshold. To make a forward link total noise or forward link noise rise prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Downlink Total Noise and click OK. The Downlink Total Noise Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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 710.

722

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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. 7. Click the Display tab. For a forward link total noise or forward link noise rise prediction, the Display Type "Value Intervals" is selected by default. The Field you choose determines which information the forward link total noise or forward link noise rise prediction makes available. Downlink total noise prediction: When making a forward link total noise prediction, select one of the following in the Field list: Min. noise level Average noise level Max noise level

Downlink noise rise prediction: When making a forward link noise rise prediction, select one of the following in the Field list: Min. noise rise Average noise rise Max noise rise

For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Calculating Pilot Pollution

A transmitter which fulfils all the criteria to enter a mobiles active set but which is not admitted because the active set limit has already been reached is considered a polluter. In the pilot pollution prediction, Atoll calculates and displays the areas where the probe mobile is interfered by the pilot signal from polluter transmitters. For 1xRTT, pilot pollution is the same on the forward and on the reverse links because 1xRTT can be connected to more than one transmitter on both the forward and on the reverse links. EV-DO, on the other hand, can only be connected to one transmitter on the forward link, but several on the reverse link. Therefore, pilot pollution for EV-DO will be different on the forward link and on the reverse link. The pilot pollution coverage prediction only calculates pilot pollution on the forward link. To make a pilot pollution prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Pilot Pollution and click OK. the coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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 710. You must also select which Carrier is to be considered. 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. 7. Click the Display tab.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

723

Atoll User Manual For a pilot pollution prediction, the Display Type "Value Intervals" and the Field "Number of Polluters" are selected by default. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Studying Inter-Technology Downlink Noise

In the inter-technology downlink noise prediction, Atoll calculates and displays the areas where the downlink noise or noise rise from external base stations and mobiles exceeds a set threshold. For more information on the modelling on intertechnology interference, see "Modelling Inter-Technology Interference" on page 806. To make an inter-technology downlink noise or noise rise prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Inter-technology Downlink Interference and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 a Service, as defined in "Service and User Modelling" on page 710. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. 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. 7. Click the Display tab. The Display Type "Value Intervals" is selected by default. The Field you choose determines which information the prediction makes available, Noise Level or Noise Rise. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

8.1.10.8.6

Making a Handoff Status Coverage Prediction

In the handoff status prediction, Atoll calculates and displays the zones where a handoff can be made. For a handoff to be possible, there must be a potential active transmitter, i.e., a transmitter that fulfils all the criteria to enter the mobile active set, and the service chosen by the user must be available. You can also use the handoff status coverage prediction to display the number of potential active transmitters. For 1xRTT, the handoff status is the same on the forward and on the reverse links because 1xRTT can be connected to more than one transmitter on both the forward and on the reverse links. EV-DO, on the other hand, can only be connected to one transmitter on the forward link, but several on the reverse link. Therefore, the handoff status coverage prediction for EV-DO is calculated on the reverse link.

724

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks To make a handoff status coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Handoff Status and click OK. the coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 8.400). 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. Note: 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 710. 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. 7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. To display the handoff status: i. Select "Discrete Values" from the Display Type list.

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. To display the number of potential active transmitters: i. Select "Value Intervals" from the Display Type list.

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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

8.1.10.8.7

Making an AS Analysis
The Point Analysis window gives you information on reception for any point on the map. The AS Analysis tab gives you 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. Analysis is based on the reverse link load percentage and the forward link 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 an AS analysis to verify a coverage prediction. In this case, before you make the AS analysis, ensure the coverage prediction you want to use in the AS analysis is displayed on the map. For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 803. To make an AS analysis: 1. Click the Point Analysis button ( Figure 8.402). 2. Click the AS Analysis tab. 3. At the top of the AS Analysis tab, select "Cells Table" from Load Conditions. ) on the toolbar. The Point Analysis Tool window appears (see

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

725

Atoll User Manual 4. If you are making an AS analysis to verify a coverage prediction, you can recreate the conditions of the coverage prediction: a. Select the same Terminal, Service, Mobility, Carrier, DL Rate, and UL Rate studied in the coverage prediction. If the coverage prediction was for 1xRTT, you must select "FCH" for both the DL Rate and UL Rate. If the coverage prediction was for EV-DO, you must select "9.6 kbps" for the UL Rate. b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select the Indoor Coverage check box to add indoor losses.

c. Click OK to close the Properties dialogue. Note: If you are making an AS 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 an active set analysis for the current location of the pointer. As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 8.401). Information on the current position is given on the AS Analysis tab of the Point Analysis window. See Figure 8.402 on page 726 for an explanation of the displayed information.

Figure 8.401: Point analysis on the map 6. Click the map to leave the point analysis pointer at its current position. To move the pointer again, click the point analysis pointer on the map and drag it to a new position. 7. Click the Point Analysis button ( Select the load conditions (DL Power and UL Load from a simulation or user-defined values) to use in this analysis. ) on the toolbar again to end the point analysis.

Select the parameters of the probe user to be studied.

Ec/I0 threshold to enter the active set as best server (Min Ec/I0 as defined in the serving cell + Delta Min Ec/I0 as defined in the Mobility type).

The pilot reception in terms of active set components for the set conditions. The active set is displayed in grey. Solid bars indicate the cells which respect the active set constraints. Even if more cells respect the constraints, the active set size is limited to the number defined in the terminal properties and is a function of the current service.

Lower boundary of the active set (T_Drop as defined for the serving cell + Delta T_Drop as defined in the Mobility type)

The connection status (pilot and uplink and downlink traffic) for the current point. : successful connection : failed connection

Figure 8.402: Point Analysis Tool - AS Analysis tab The bar graph displays the following information: The pilot quality (EcI0) reception of all transmitters using the selected carrier (the colour of the bar colour 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. The pilot and the availability of service on the reverse link and forward link.

726

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks If there is at least one successful connection (for pilot, forward link, or reverse link), double-clicking the icons in the righthand frame will open a dialogue with additional information.

8.1.10.9

Printing and Exporting Coverage Prediction Results

Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. 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 65. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 46. 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 49.

8.1.11

Planning Neighbours
You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you set. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbours to the cells within the computation zone. The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo tab in the Explorer window is selected. Usually, you will allocate neighbours globally during the beginning of a radio planning project. Afterwards, you will allocate neighbours to base stations or transmitters as you add them. You can use automatic allocation on all cells in the document, or you can define a group of cells either by using a focus zone or by grouping transmitters in the Explorer window. For information on creating a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 703. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 69. Atoll supports the following neighbour types in a CDMA network: Intra-technology Neighbours: Intra-technology neighbours are cells defined as neighbours that both use CDMA. Intra-technology neighbours can be divided into: Intra-carrier Neighbours: Cells defined as neighbours which perform handoff using the same carrier. Inter-carrier Neighbours: Cells defined as neighbours which perform handoff using a different carrier.

Inter-technology Neighbours: Inter-technology neighbours are cells defined as neighbours that use a technology other than CDMA.

In this section, the following are explained: "Importing Neighbours" on page 727 "Defining Exceptional Pairs" on page 728 "Configuring Importance Factors for Neighbours" on page 728 "Allocating Neighbours Automatically" on page 728 "Checking Automatic Allocation Results" on page 732 "Allocating and Deleting Neighbours per Cell" on page 734 "Calculating the Importance of Existing Neighbours" on page 736 "Checking the Consistency of the Neighbour Plan" on page 738 "Exporting Neighbours" on page 739.

8.1.11.1

Importing Neighbours
You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Data tab of the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 63.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

727

Atoll User Manual

8.1.11.2

Defining Exceptional Pairs

In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs may be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Intra-Technology Exceptional Pairs from the context menu. The Exceptional Pairs of Intra-Technology Neighbours table appears. 4. In the row marked with the New Row icon ( from the Cell column. ), select the cell for which you want to define neighbour constraints

5. From the Neighbour column, select the second cell of the exceptional pair. 6. In the Status column, select one of the following: Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell.

7. Click elsewhere in the table when you have finished creating the new exceptional pair. Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table by right-clicking the Transmitters folder and selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.

8.1.11.3

Configuring Importance Factors for Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible intra- and inter-carrier neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. Select the Intra-carrier Neighbours tab. On the Intra-carrier Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency Factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 728. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 728.

5. Select the Inter-carrier Neighbours tab. On the Inter-carrier Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 728.

6. Click OK.

8.1.11.4

Allocating Neighbours Automatically

Atoll can automatically allocate both intra- and inter-carrier neighbours in a CDMA network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. To automatically allocate intra-carrier CDMA neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Intra-Carrier Neighbours tab. You can set the following parameters:

728

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour. Max. Number of Neighbours: Set the maximum number of intra-carrier neighbours that can be allocated to a cell. This value can be either set here for all transmitters, or specified for each cell in the Cells table. Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. - Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A and possible neighbour cell B. - Min. Ec/I0: Enter or modify the minimum EcI0 required from a transmitter to enter the active set as best server. - T_Drop: Enter or modify the minimum EcI0 required from a transmitter not to be rejected from the active set. - DL Load Contributing to Io: You can let Atoll base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). - Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations. % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must overlap the reference cells coverage area. -

5. Select the desired calculation parameters: Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers; Atoll will allocate neighbours to cells using the selected carriers. Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located on the same site as the reference cell to be automatically considered as neighbours. Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell is the best server, or where the possible neighbour cell is the second best server in the reference cells active set. Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from the list of neighbours of the reference cell. Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 728. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.

6. Click Calculate. Atoll begins the process of allocating intra-carrier neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance as calculated with the options selected in "Calculating the Importance of Existing Neighbours" on page 736 Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the reference cell, as identified in the Cell column. Co-site Adjacency Symmetry Coverage Existing

Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell is best server or second best server.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

729

Atoll User Manual 7. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

8. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue. To automatically allocate inter-carrier CDMA neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Inter-Carrier Neighbours tab. You can set the following parameters: Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour. Max. Number of Neighbours: Set the maximum number of inter-carrier neighbours that can be allocated to a cell. This value can be either set here for all transmitters, or specified for each transmitter in the Cells table. Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. - Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A and possible neighbour cell B. - Margin: Enter the signal margin relative to the pilot signal of the reference cell A. See the Technical Reference Guide for an explanation of how the margin is used in different inter-carrier handoff scenarios. - Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must overlap the reference cells coverage area. -

5. Select the desired calculation parameters: Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers; Atoll will allocate neighbours to cells using the selected carriers. Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located on the same site as the reference cell to be automatically considered as neighbours. Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from the list of neighbours of the reference cell. Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 728. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.

6. Click Calculate. Atoll begins the process of allocating inter-carrier neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

730

Chapter 8: CDMA2000 Networks Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance as calculated with the options selected in "Calculating the Importance of Existing Neighbours" on page 736 Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the reference cell, as identified in the Cell column. Co-site Symmetry Coverage Existing

Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square kilometres.

7. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

8. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue. Notes: A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint on the forbidden neighbour will be ignored by the algorithm because the neighbour already exists. When the options Force exceptional pairs and Force symmetry are selected, Atoll considers the constraints between exceptional pairs in both directions in order to respect symmetry. On the other hand, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event Viewer. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Exporting a User Configuration" on page 79.

8.1.11.4.1

Allocating Neighbours to a New Base Station

When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects with the coverage area of the cells of the new base station. To allocate neighbours to a new base station: 1. On the Data tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects" on page 69. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 728.

8.1.11.4.2

Allocating Neighbours to a New Transmitter

When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new transmitters and other cells whose coverage area intersects with the coverage area of the cells of the new transmitter. To allocate neighbours to a new transmitter: 1. Click the Data tab of the Explorer window. 2. In the Transmitters folder, right-click the new transmitter. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

731

Atoll User Manual 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 728.

8.1.11.5

Checking Automatic Allocation Results

You can verify the results of automatic neighbour allocation in the following ways: "Displaying Neighbour Relations on the Map" on page 732 "Displaying the Coverage of Each Neighbour of a Cell" on page 733.

8.1.11.5.1

Displaying Neighbour Relations on the Map

You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

2. Select Display Options from the context menu. The Visual Management dialogue appears. 3. Under Intra-technology Neighbours, select the Display Links check box. 4. Click the Browse button ( ) beside the Display Links check box.

5. The Intra-technology Neighbour Display dialogue appears. 6. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours table, or according to the neighbour carrier. In this case, you can view on the map intra-carrier and inter-carrier neighbour relations. Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

Tip:

You can display the number of handoff attempts for each cell-neighbour pair by first 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 along with "Value Intervals" as the Display Type. For information on adding a new field to a table, see "Adding a Field to an Object Types Data Table" on page 54.

Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you can display or hide neighbour link display types individually. For information on changing display properties, see "Display Properties of Objects" on page 32. 7. Select the Add to Legend check box to add the displayed neighbour links to the legend. 8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each neighbour link. 9. Click OK to save your settings. 10. Under Advanced, select which neighbour links to display: Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations where the selected cell is the reference cell and where the neighbour relation is not symmetric. Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations where the selected cell is neighbour and where the neighbour relation is not symmetric. Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the selected cell and the neighbour.

11. Click OK to save your settings. 12. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 14. Click the Visual Management button ( ) in the Radio toolbar.

15. Click a transmitter on the map to display the neighbour relations. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). Atoll displays the following information (see Figure 8.403) for the selected cell:

732

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks The symmetric neighbour relations of the selected (reference) cell are indicated by a line. The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see Site1_2(0)) in Figure 8.403.). The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see Site9_3(0)) in Figure 8.403.).

In Figure 8.403, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is coloured as the reference transmitter as it is neighbour of Site9_3(0) here.

Figure 8.403: Neighbours of Site 22_3(0) - Display According to the Neighbour In Figure 8.404, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and inter-carrier neighbour links. Here, all neighbour relations are symmetric.

Figure 8.404: ntra-carrier and Inter-Carrier Neighbours of Site 14_3(0) Note: You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

8.1.11.5.2

Displaying the Coverage of Each Neighbour of a Cell

By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cells neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a "Coverage by transmitter" prediction, with the Display Type set to "Discrete Values" and the Field set to Transmitter (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 699). 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

3. Select Display Options from the context menu. The Visual Management dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

733

Atoll User Manual 4. Under Intra-technology Neighbours, select the Display Coverage Areas check box. 5. Click the Browse button ( ) beside the Display Coverage Areas check box.

6. The Intra-technology Neighbour Display dialogue appears. 7. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neighbours with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology Neighbours table. Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each coverage area. 9. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 11. Click the Visual Management button ( ) in the Radio toolbar.

12. Click a transmitter on the map to display the coverage of each neighbour. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). Note: Only intra-carrier neighbour coverage areas are displayed.

13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( Radio toolbar.

) in the

8.1.11.6

Allocating and Deleting Neighbours per Cell

Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of the Transmitter Properties dialogue. This section explains the following: "Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 734 "Allocating or Deleting Neighbours Using the Neighbours Table" on page 735 "Allocating or Deleting Neighbours on the Map" on page 736.

Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete CDMA neighbours using the Cells tab of the transmitters Properties dialogue: 1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cells Properties dialogue appears. 5. Click the Intra-technology Neighbours tab. 6. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." 7. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column.

734

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 8. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 9. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 10. Click OK.

Allocating or Deleting Neighbours Using the Neighbours Table

To allocate or delete CDMA neighbours using the Neighbours table: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. Note: For information on working with data tables, see "Working with Data Tables" on page 53.

4. To allocate a neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." 5. To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 6. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. 7. To take into consideration all exceptionnal pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either some forced neighbours or some forbidden neighbours using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu. ), select a reference cell in the Cell column.

8. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 9. To delete several symmetric neighbour relations: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

735

Atoll User Manual 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour.

Allocating or Deleting Neighbours on the Map

You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 732. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters to the intra-technology neighbours list. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitters from the intra-technology neighbours. To add an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the intra-technology neighbour list of the reference transmitter. To remove an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the intra-technology neighbours list of the reference transmitter. To add an inward neighbour relation: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the intra-technology neighbours list of the reference transmitter. Notes: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

8.1.11.7

Calculating the Importance of Existing Neighbours

After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Select the Intra-carrier Neighbours tab. 5. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 728):

736

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference transmitters when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.

6. Coverage Conditions: Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the neighbour. Min. Ec/Io: Enter the minimum EcIo which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage. T_Drop: Enter the minimum EcIo required from a transmitter not to be rejected from the active set. DL Load Contributing to Io: Under DL Load Contributing to Io, select whether you want Atoll to base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

7. Click OK to save your modifications and close the Coverage Conditions dialogue. 8. Select the Inter-carrier Neighbours tab. 9. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 728): 10. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the neighbour. Min. Ec/Io: Enter the minimum EcIo which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage. T_Drop: Enter the minimum EcIo required from a transmitter not to be rejected from the active set. DL Load Contributing to Io: Under DL Load Contributing to Io, select whether you want Atoll to base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

11. Click OK to save your modifications and close the Coverage Conditions dialogue. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. Notes: You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

12. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information: Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 5. Cause: The reason Atoll has allocated value in the Importance column. Co-site Adjacency Symmetry Coverage

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

737

Atoll User Manual Coverage: The amount of reference transmitters coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neighbour transmitter is best server or second best server. This information is not relevant for inter-carrier neighbours and is therefore not present on the Inter-carrier Neighbours tab. Distance: The distance in kilometres between the reference cell and the neighbour.

The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

8.1.11.8

Checking the Consistency of the Neighbour Plan

You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Intra-technology Nieghbours tab. 5. Define the parameters of the audit: Neighbourhood Type: Select whether you want to perform an audit on Intra-Carrier or Inter-Carrier neighbour relations. Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want 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 transmitters, or specified for each transmitter in the Cells table. Lists > Max Number: Select the Lists > Max Number check box if you want 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 transmitters, or specified for each transmitter in the Cells table Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours > check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax: |CELL|

Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax: Note: |CELL| |NUMBER| |MAX NUMBER| If the field Maximum number of intra-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.

738

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

8.1.11.9

Exporting Neighbours
The neighbour data of an Atoll document is stored in a series of tables. You can export the neighbour data for use in another application or in another Atoll document. To export neighbour data: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours and then select the neighbour table containing the data you want to export from the context menu: Intra-Technology Neighbours: This table contains the data for the intra-technology (intra-carrier and intercarrier) neighbours in the current Atoll document. Intra-Technology Exceptional Pairs Neighbours: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document.

4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files" on page 61.

8.1.12

Planning PN Offsets
In CDMA, 512 pseudo noise (PN) offsets are available, numbered from 0 to 511. Atoll facilitates the management of available PN offsets during automatic allocation with the pilot PN sequence offset index increment (PILOT_INC) parameter. For example, if you set PILOT_INC to "4," all PN offsets from 4 to 508 with a separation interval of 4 can be allocated. If you need to restrict the range of PN offsets available further, you can create groups of PN offsets and domains, where each domain is a defined set of groups. You can also assign PN offsets manually or automatically to any cell in the network. Once allocation is completed, you can audit the PN offsets, view PN offset reuse on the map, and made an analysis of PN offset distribution. The procedure for planning PN offsets for a CDMA project is: Preparing for PN offset allocation - "Creating PN Offset Domains and Groups for PN Offset Allocation" on page 805. This step is needed only if you must restrict the range of PN offsets. - "Defining Exceptional Pairs for PN Offset Allocation" on page 739. Allocating PN offsets "Automatically Allocating PN Offsets to CDMA Cells" on page 740 "Allocating PN Offsets to CDMA Cells Manually" on page 742.

"Checking the Consistency of the PN Offset Plan" on page 742. Displaying the allocation of PN offsets "Using the Search Tool to Display PN Offset Allocation" on page 743 "Displaying PN Offset Allocation Using Transmitter Display Settings" on page 744 "Grouping Transmitters by PN Offset" on page 744 "Displaying the PN Offset Allocation Histogram" on page 744 "Making a PN Offset Interference Zone Prediction" on page 745. "Making a PN Offset Interference Analysis" on page 745 Note: Within the context of PN offset allocation, "neighbours" refer to intra-carrier neighbours.

8.1.12.1

Defining Exceptional Pairs for PN Offset Allocation

You can also define pairs of cells which cannot have the same PN offset. These pairs are referred to as exceptional pairs. Exceptional pairs are used along with other constraints, such as neighbours, reuse distance, and domains, in allocating PN offsets. To create a pair of cells that cannot have the same PN offset: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > PN Offsets > Exceptional Pairs. The Exceptional Separation Constraints table appears. For information on working with data tables, see "Working with Data Tables" on page 53.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

739

Atoll User Manual 4. 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. 5. Click in another cell of the table to create the new exceptional pair and add a new blank row to the table.

8.1.12.2

Allocating PN Offsets
Atoll can automatically assign PN offsets to the cells of a CDMA network according to set parameters. For example, it takes into account any constraints imposed by neighbours, minimum PN offset reuse distance, the selected PN offset allocation strategy (PN offset per cell, Adjacent PN-clusters per site, Distributed PN-clusters per site) and the definition of groups and domains of PN offsets. You can also allocate PN offsets manually to the cells of a CDMA network. In this section, the following methods of allocating PN offsets are described: "Defining Automatic Allocation Constraint Costs" on page 740 "Automatically Allocating PN Offsets to CDMA Cells" on page 740 "Allocating PN Offsets to CDMA Cells Manually" on page 742.

Defining Automatic Allocation Constraint Costs

You can define the costs of the different types of constraints used in the automatic PN offset allocation algorithm. To define the different constraint costs: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > PN Offsets > Constraint Costs. The Allocation Constraint Costs dialogue appears. In this dialogue you can define the following costs of constraint violations for the automatic allocation process (the cost is a value from 0 to 1): 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. 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. 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. Note: 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}).

740

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks To automatically allocate PN offsets: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > PN Offsets > Automatic Allocation. The PN Offsets dialogue appears. 4. Set the following parameters in the PN Offsets dialogue: 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 PN-chips, 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 "Planning Neighbours" on page 727. Note: Atoll can take into account inter-technology neighbour relations as constraints when allocating PN offsets to the CDMA2000 neighbours of a GSM transmitter. In order to consider inter-technology neighbour relations in PN offset allocation, you must make the Transmitters folder of the GSM Atoll document accessible in the CDMA2000 Atoll document. For information on making links between GSM and CDMA2000 Atoll documents, see "Creating a CDMA Sector From a Sector in the Other Network" on page 797 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 dialogue, 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. Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations. Reuse Distance: Select the Reuse Distance check box if you want to the automatic allocation process to consider the reuse distance constraint. Enter the Default reuse distance within which two cells on the same carrier cannot have the same PN offset. A reuse distance can be defined at the cell level (in the cell Properties dialogue or in the Cells table). If defined, a cell-specific reuse distance will be used instead of the value entered here. Exceptional Pairs: Select the Exceptional Pairs check box if you want the automatic allocation process to consider the exceptional pair constraints.

Note:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

741

Atoll User Manual From the Strategy list, you can select an automatic allocation strategy: 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.

5. Click Run. Atoll begins the process of allocating PN offsets. Once Atoll has finished allocating PN offsets, they are visible under Results. Atoll only displays newly allocated PN offsets. The Results table contains the following information. Site: The name of the base station. Cell: The name of the cell. Code: The PN offset allocated to the cell.

6. Click Commit. The PN offsets are committed to the cells. Note: You can save automatic PN offset allocation parameters in a user configuration. For information on saving automatic PN offset allocation parameters in a user configuration, see "Exporting a User Configuration" on page 79.

Tips:

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.

Allocating PN Offsets to CDMA Cells Manually

When you allocate PN offsets to a large number of cells, it is easiest to let Atoll allocate PN offsets automatically, as described in "Automatically Allocating PN Offsets to CDMA Cells" on page 740. However, if you want to add a PN offset to one cell or to modify the PN offset of a cell, you can do it by accessing the properties of the cell. To allocate a PN offset to a CDMA cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a PN offset. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Select the Cells tab. 4. Enter a PN Offset in the cells column. 5. Click OK.

8.1.12.3

Checking the Consistency of the PN Offset Plan

Once you have completed allocating PN offsets, you can verify whether the allocated PN offsets respect the specified constraints by performing an audit of the plan. The PN offset audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > PN Offsets > Audit. The Code Audit dialogue appears. 4. In the Code Audit dialogue, select the allocation criteria that you want to check:

742

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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 Neighbours: 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 Neighbours: 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 ones defined for the two cells in their properties and the value that you set in the Code Audit dialogue. 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.

8.1.12.4

Displaying the Allocation of PN Offsets

Once you have completed allocating PN offsets, you can verify several aspects of PN offset allocation. You have several options for displaying PN offsets: "Using the Search Tool to Display PN Offset Allocation" on page 743 "Displaying PN Offset Allocation Using Transmitter Display Settings" on page 744 "Grouping Transmitters by PN Offset" on page 744 "Displaying the PN Offset Allocation Histogram" on page 744 "Making a PN Offset Interference Zone Prediction" on page 745. "Making a PN Offset Interference Analysis" on page 745

Using the Search Tool to Display PN Offset Allocation

In Atoll, you can search for PN offsets and PN offset groups using the Search Tool. Results are displayed in the map window in red. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. PN offsets and PN offset 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 699. To find PN offsets or PN offset groups using the Search Tool: 1. Create, calculate, and display a coverage prediction by transmitter. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 699. 2. Click View > Search Tool. The Search Tool window appears. The Search Tool window is a docking window. For information on docking windows, see "Docking or Floating an Atoll Window" on page 26. 3. You can search either for a specific PN offset or PN offset group: To search for a PN offset: a. Select PN Offset. b. Enter a PN offset in the text box. To search for a PN offset group: a. Select PN Offset Group. b. Select a PN offset group from the list. 4. Select the carrier you wish to search for from the For the Carrier list, or select "(All)" to search for the PN offset or PN offset group in all carriers. 5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match the search criteria are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

743

Atoll User Manual

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. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue 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 tooltip: PN offset: To display the PN offset of a transmitters cell in the transmitter label or tooltip, "Cells: PN Offset" from the Label or Tip Text Field Definition dialogue. PN offset domain: To display the PN offset domain of a transmitters cell in the transmitter label or tooltip, "Cells: PN Offset Domain" from the Label or Tip Text Field Definition dialogue.

5. Click OK. For information on display options, see "Display Properties of Objects" on page 32.

Grouping Transmitters by PN Offset

You can group transmitters on the Data tab of the Explorer window by their PN offset or by their PN offset domain. To group transmitters by PN offset: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: 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" on page 70. 8. Click OK to save your changes and close the Group dialogue. Note: 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. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > PN Offset > PN Offset Distribution. The Distribution Histograms dialogue appears. Each bar represents a PN offset, its height depending on the frequency of its use. 4. Move the pointer over the histogram to display the frequency of use of each PN offset. The results are highlighted simultaneously in the Detailed Results list.

744

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Making a PN Offset Interference Zone Prediction

You can make a PN offset interference zone prediction to view areas covered by cells using the same PN offset. Atoll checks on each pixel if the best server and other servers satisfying the conditions to enter the user active set have the same PN Offset. If so, Atoll considers that there is PN Offset interference. To make a PN Offset interference zone prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select PN Offset Interference Zones and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition 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. Note: 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 710. You must also select which Carrier is to be considered. If you want the PN Offset interference 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. 7. Click the Display tab. For a PN Offset interference zone prediction, the Display Type "Discrete Values" based on the Field "Transmitter" is selected by default. Each pixel with PN Offset interference 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 "Display Properties of Objects" on page 32. 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.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Making a PN Offset Interference Analysis

The PN Offset Interference tab of the Point Analysis window gives you information on the reception for any point on the map where there is PN Offset interference. PN Offset interference occurs when the best server and other servers satisfying the conditions to enter the user active set have the same PN Offset. When there is PN Offset interference, 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 interference analysis to review the PN Offset interference zone coverage prediction. In this case, before you make the PN Offset interference analysis, you should ensure that the coverage prediction you want to use in the PN Offset interference analysis is displayed on the map. To make a PN Offset interference analysis: 1. Click the Point Analysis button ( 2. Click the PN Offset Interference tab. ) on the toolbar. The Point Analysis Tool window appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

745

Atoll User Manual 3. At the top of the PN Offset Interference tab, select "Cells Table" from Load Conditions. 4. If you are making a PN Offset interference analysis to verify a coverage prediction, you can recreate the conditions of the coverage prediction: a. Select the Terminal, Service, and Mobility studied in the coverage prediction. b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select the Indoor Coverage check box to add indoor losses.

c. Click OK to close the Properties dialogue. Note: If you are making a PN Offset interference analysis to make a coverage 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 PN Offset interference 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 ( ) on the toolbar again to end the point analysis.

8.2

Studying Network Capacity

A CDMA network automatically regulates power with the objective of minimising interference and maximising network capacity. In the case of CDMA2000 1xRTT, fast power control is made on both the forward and reverse links (uplink and downlink, respectively). In CDMA2000 1xRTT, power control can be performed on either the FCH and SCH or on the pilot channel. In CDMA2000 EV-DO, rate control is used instead of power control on the forward link. On the reverse link, power control is made on the pilot channel. Atoll can simulate these network regulation mechanisms, thereby enabling you to study the capacity of the CDMA network. 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 active set for each mobile, the required power of the mobile, SHO gain, the total forward link power and forward link throughput per cell, and the reverse link load per cell. Simulations are calculated in an iterative fashion. When several simulations are performed at the same time using the same traffic information, the distribution of users will be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to another. 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: "Defining Multi-service Traffic Data" on page 746 "Creating a Traffic Map" on page 747 "Calculating and Displaying Traffic Simulations" on page 756 "Analysing the Results of a Simulation" on page 771.

8.2.1

Defining Multi-service Traffic Data

The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters used in the network, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: 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 711. 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 "Creating a Mobility Type" on page 714. 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 714.

746

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

8.2.2

Creating a Traffic Map

The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for CDMA projects. Sector traffic map User profile traffic map User density traffic map (number of users per km2)

These maps can be used for 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 reverse and forward links 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 747. User profile traffic maps can be used if you have marketing-based traffic data. User profile traffic maps, where each vector (polygon, line, or point) describes subscriber densities (or numbers of subscribers for points) with user profiles and mobility types, and user profile environment based traffic maps, where each pixel has an assigned environment class. For more information, see "Importing a User Profile Traffic Map" on page 750, "Creating a User Profile Environment Based Traffic Map" on page 752, and "Importing a User Profile Environment Based Traffic Map" on page 751. User density traffic maps (number of users per km2) can be used if you have population-based traffic data, or 2G network statistics. Each pixel has a user density assigned. The value either includes all activity statuses or it corresponds to a particular activity status. For more information, see "Importing a User Density Traffic Map" on page 753, "Creating a User Density Traffic Map" on page 754, "Converting 2G Network Traffic" on page 755 and "Exporting Cumulated Traffic" on page 755.

8.2.2.1

Creating a Sector Traffic Map

The section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the reverse and forward links or the number of users per activity status or the total number of users including all activity statuses. A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 699. Note: Because each of the CDMA technologies has capabilities and services that are specific to it, it is recommended to create a separate traffic map for: voice 1xRTT data EV-DO data

To create a sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector Traffic Map. 5. Select the type of traffic information you want to input. You can choose between Throughputs in Uplink and Downlink, Total Number of Users (All Activity Statuses) or Number of Users per Activity Status. 6. Click the Create button. The Sector Traffic Map dialogue appears. Note: You can also import a traffic map from a file by clicking the Import button. You can import AGD (Atoll Geographic Data) format files that you have exported from an other Atoll document.

7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 8. Enter the data required in the Map per Sector dialogue: If you selected Throughputs in Uplink and Downlink, enter the throughput demands in the reverse and forward links for each sector and for voice and each 1xRTT data service. Because only one EV-DO data service user is served at a time, all EV-DO users are considered as active in the forward link. Therefore, you can only enter the throughput demand in the reverse link for each sector and for each EV-DO data service. If you selected Total Number of Users (All Activity Statuses), enter the number of connected users for each sector and for each listed service.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

747

Atoll User Manual If you selected Number of Users per Activity Status, enter the number of users active in the reverse and forward links for each sector and for voice and each 1xRTT data service. Because only one EV-DO data service user is served at a time, all EV-DO users are considered as active in the forward link. Therefore, you can only enter the number of inactive users (in the reverse link) and the number of active users in the reverse link for each sector and for each EV-DO data service. Note: You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 63.

9. Click OK. The Sector Traffic Map Properties dialogue appears. 10. Select the Traffic tab. 11. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. 12. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 13. Under Clutter Distribution, for each clutter class, enter: A weight to spread the traffic over the vector. The percentage of indoor users. An additional loss will be counted for indoor users during Monte-Carlo simulations.

14. Click OK. Atoll creates the traffic map in the Traffic folder. You can modify the sector traffic map after it has been created. To modify the sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 5. Select the Traffic tab. 6. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 7. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 8. Under Clutter Distribution, for each clutter class, enter a weight to spread the traffic over the clutter classes and the percentage of indoor users. 9. Click OK. Atoll saves the traffic map with its modifed values. You can update the information, throughput demands and the number of users, on the map afterwards. You can update sector traffic maps if you add or remove a base station. You must first recalculate the coverage prediction by transmitter. For more information, see "Making a Coverage Prediction by Transmitter" on page 699. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map that you want to update. The context menu appears. 4. 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. 5. Click OK. The Sector Traffic Map Properties dialogue appears. If desired you can update the values under Terminals (%), Mobilities (%), and Clutter Distribution. 6. 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 754.

8.2.2.2

Creating a User Profile Traffic Map

The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There may also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments. A user profile models the behaviour of different subscriber categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration.

748

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Environment classes are used to describe the distribution of subscribers on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km). The sections "Importing a User Profile Traffic Map" on page 750, "Importing a User Profile Environment Based Traffic Map" on page 751 and "Creating a User Profile Environment Based Traffic Map" on page 752 describe how to use traffic data from the marketing department in Atoll to model traffic. In this section, the following are explained: "Modelling User Profiles" on page 749 "Modelling Environments" on page 749.

Modelling User Profiles

You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user may be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.

3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. Note: 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.

5. You can modify the following parameters: Service: Select a service from the list. For information on services, see "Modelling Services" on page 711. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 714. Calls/Hour: Enter the average number of calls per hour for the service. One call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each. Duration: Enter the average duration of a call in seconds. The calls per hour and duration are used to calculate the activity probability. Note: 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.

Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers for each clutter class. In a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss. To create or modify a CDMA environment: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.

3. Right-click the Environments folder. The context menu appears. 4. Select New from the context menu. The Environments New Element Properties dialogue appears. Note: You can modify the properties of an existing environment by right-clicking the environment in the Environments folder and selecting Properties from the context menu.

5. Click the General tab. 6. Enter a Name for the new CDMA environment. 7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility combination that this CDMA environment will describe: User: Select a user profile. Mobility: Select a mobility type. Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination of user profile and mobility type.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

749

Atoll User Manual 8. Click the Clutter Weighting tab. 9. For each clutter class, enter a weight that will be used to distribute users on the map. The number of users per clutter class is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

For example: An area of 10 km with a subscriber density of 100/km. Therefore, in this area, there are 1000 subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in the Building clutter class. 10. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss.

8.2.2.2.1

Importing a User Profile Traffic Map

User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscriberskm, or polygons with a number of subscriberskm) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Densities from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue.

7. Select the file to import. The file must be in one of the following supported vector formats: DXF format (DXF), Atoll Geographic Data File (AGD), ArcView format (SHP), MapInfo file (MIF or TAB), or Planet Data File (index). 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab (see Figure 8.405). Under Traffic Fields, you can specify the user profiles to be considered, their mobility type (kmh), and their density. If the file you are importing has this data, you can define the traffic characteristics by identifying the corresponding fields in the file. If the file you are importing does not have data describing the user profile, mobility, or density, you can assign values. When you assign values, they apply to the entire map.

750

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Figure 8.405: Traffic map properties dialogue - Traffic tab Define each of the following: User Profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the CDMA/ CDMA2000 Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the CDMA/CDMA2000 Parameters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points. Important: 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 CDMA/CDMA2000 Parameters folder of the Data tab. If the imported user profile or mobility does not match, Atoll will display a warning. 12. Under Clutter Distribution, enter a weight for each class that will be used to distribute users on the map. The user distribution per clutter class is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

13. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss. 14. Click OK to finish importing the traffic map.

8.2.2.2.2

Importing a User Profile Environment Based Traffic Map

Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

751

Atoll User Manual 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 752.

7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST, BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Description tab. In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the Code column. 12. For each Code, select the environment it corresponds to from the Name column. The environments available are those available in the Environments folder, under CDMA/CDMA2000 Parameters on the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 749. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 32.

8.2.2.2.3

Creating a User Profile Environment Based Traffic Map

Atoll enables you to create a user profile environment based traffic map based on by drawing it in the map window. To draw a traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 8.406).

Draw Map

Delete Map

Figure 8.406: Environment Map Editor toolbar 7. Select the environment class from the list of available environment classes. 8. Click the Draw Polygon button ( 9. Click the Delete Polygon button ( ) to draw the polygon on the map for the selected environment class. ) and click the polygon to delete the environment class polygon on the map.

10. Click the Close button to close the Environment Map Editor toolbar and end editing.

8.2.2.2.4

Displaying Statistics on a User Profile Environment Based Traffic Map

You can display the statistics of a user profile environment based traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment based traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the user profile environment based traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears.

752

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks The Statistics window lists the surface (Si in km) and the percentage of surface (% of i) for each environment Si class "i" within the focus zone. The percentage of surface is given by: % of i = ------------- 100 Sk

You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.

8.2.2.3

Creating User Density Traffic Maps (No. Users/km2)

User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. This can be either the density of users per activity status or the density of users including all activity statuses. In this section, the following ways of creating a user density traffic map are explained: "Importing a User Density Traffic Map" on page 753 "Creating a User Density Traffic Map" on page 754.

User density traffic maps may be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. for more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 754.

8.2.2.3.1

Importing a User Density Traffic Map

The user density traffic map defines the density of users per pixel. For a traffic density of X users per km, Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic maps properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. Note: Because each of the CDMA technologies has capabilities and services that are specific to it, it is recommended to create a separate traffic map per user density for: voice 1xRTT data EV-DO data

To create a user density traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (No. Users/km2). 5. Select the type of traffic information you input: All Activity Statuses: Select All Activity Statuses if the map you are importing provides a density of users with any activity status. Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.

6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue.

7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP, PlaNET, TIF, ISTAR, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

753

Atoll User Manual 11. Select the Traffic tab. 12. Select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink. 13. Under Terminals (%), enter the percentage of each type of radio configuration used in this map. The total percentage must equal 100 for this map. 14. Under Mobilities (%), enter the percentage of each mobility type used in this map. The total percentage must equal 100 for this map. 15. Under Services (%), enter the percentage of each service type used in this map. The total percentage must equal 100. 16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel. 17. Click OK. Atoll creates the traffic map in the Traffic folder.

8.2.2.3.2

Creating a User Density Traffic Map

Atollenables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (Number of users per km2). 5. Select the type of traffic information you input. You can choose between: All Activity Statuses: Select All Activity Statuses if the map you are importing provides a density of users with any activity status. Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.

6. Click the Create button. The traffic maps property dialogue appears. 7. Select the Traffic tab. 8. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. 9. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 10. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 11. Under Clutter Distribution, enter for each clutter class the percentage of indoor users. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for user density traffic maps because the traffic is provided in terms of user density per pixel. 12. Click OK. Atoll creates the traffic map in the Traffic folder. 13. Right-click the traffic map. The context menu appears. 14. Select Edit from the context menu. 15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit contours, see "Editing Polygons, Lines, and Points" on page 46. Atoll creates an item called Density values in the User Density Map folder. 16. Right-click the item. The context menu appears. 17. Select Open Table from the context menu. 18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn. 19. Right-click the item. The context menu appears. 20. Select Edit from the context menu to end editing.

8.2.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.

754

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks To create user density traffic maps from a sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map from which you want to create user density traffic maps. The context menu appears. 4. Select Create density maps from the context menu. Atoll creates as many user density traffic maps as the number of services present in the sector traffic map. The user density map files use the resolution of the coverage prediction used for the sector traffic map and are embedded in the document.

8.2.2.4

Converting 2G Network Traffic

Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as user density traffic maps into your CDMA document. These maps can then be used in traffic simulations like any other type of ma For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 755, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 753. To import a 2G traffic map into a CDMA document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 254. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 755. 3. Import the traffic exported in step 2 to your CDMA document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 753.

8.2.2.5

Exporting Cumulated Traffic

Atollallows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: The Entire Project Area: This option allows you to export the cumulated traffic over the entire project. The Computation Zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible.

7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains at "0" and no data will be exported. 8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic data to be exported. Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal. Service: Select the service that will be exported, or select "Circuit services" to export speech type traffic, or select "Packet services" to export data type traffic. Mobility: Select the mobility type that will be exported or select "All" to export all mobility types. Activity: Select one of the following: All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status. Uplink: Select Uplink to export mobiles active in the uplink only. Downlink: Select Downlink to export mobiles active in the downlink only. Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity. Inactive: Select Inactive to export only inactive mobiles.

9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the cumulated traffic. 10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

755

Atoll User Manual

8.2.3

Exporting a Traffic Map

To export a traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save. If you are exporting a raster traffic map, you have to define: The Export Region: Entire Project Area: Saves the entire traffic map. Only Pending Changes: Saves only the modifications made to the map. Computation Zone: Saves only the part of the traffic map inside the computation zone.

An export Resolution.

8.2.4

Calculating and Displaying Traffic Simulations

Once you have modelled the network services and users and have created traffic maps, you can create simulations. The simulation process consists of two steps: 1. Obtaining a realistic user distribution: Atoll generates a user distribution using a Monte-Carlo algorithm; this user distribution is based on the traffic database and traffic maps and is weighted by a Poisson distribution between simulations of a 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 network interference. A user may be either active or inactive. Both active and inactive users consume radio resources and create interference. Additionally, each 1xEV-DO Rev. 0 user is assigned a transition flag ("True" or "False") for each possible rate transition (from 9.6 to 19.2 kbps, 19.2 to 38.4 kbps, 38.4 to 76.8 kbps, and 76.8 to 153.6 kbps for rate upgrading and from 153.6 to 76.8 kbps, 76.8 to 38.4 kbps, 38.4 to 19.2 kbps, and 19.2 to 9.6 kbps for rate downgrading). These transition flags are based on the rate downgrading and upgrading probabilities. If a transition flag is "True," the user rate can be downgraded or upgraded if necessary. 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 756.

8.2.4.1

The Power Control Simulation Algorithm

The power control algorithm simulates the way a CDMA network regulates itself by using forward link and reverse link power controls or, in the case of CDMA2000 1xEV-DO, rate control in the forward link and power control in the reverse link in order to minimize interference and maximize capacity. Atoll simulates the network regulation mechanisms for each user distribution. During each iteration of the algorithm, all the mobiles (voice, 1xRTT data, and EV-DO data service users) selected during the user distribution generation attempt to connect one by one to network transmitters. The process is repeated until the network is balanced, i.e., until the convergence criteria (on the forward and the reverse link) are satisfied.

The CDMA2000 1xRTT Power Control Simulation Algorithm

The CDMA2000 1xRTT power control simulation algorithm (see Figure 8.407) simulates the power control, congestion, and radio resource control performed for CDMA2000 1xRTT users. Atoll considers each user in the order established during the generation of the user distribution, determines his best server and his active set. Atoll 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, depending on the option selected under UL 1xRTT Power Control Based On on the Global Parameters tab of the Transmitter Properties dialogue (see "Creating or Modifying a Transmitter" on page 673).

756

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks After performing power control, Atoll updates the reverse link load factor and the total forward link transmitted power. Atoll then carries out congestion and radio resource control, verifying the cell reverse link load, the forward link load, and the number of channel elements and Walsh codes consumed by the cell.

Figure 8.407: Power control simulation for CDMA2000 1xRTT The SCH rate on the forward and the reverse links can be downgraded. Atoll will downgrade the forward link SCH rate until: The required forward link quality level on SCH is reached, 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.

Atoll will downgrade the reverse link SCH rate until: The required reverse link quality level on SCH or on pilot is reached, The number of channel elements consumed on the reverse link by a site is lower than the maximum number of channel elements allowed.

Downgraded SCH rates cannot be lower than the FCH nominal rate. When downgrading the SCH rate 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: The signal quality is not sufficient: On the forward link, 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."

The network is saturated: -

The CDMA2000 1xEV-DO Rate and Power Control Simulation Algorithm

The CDMA2000 1xEV-DO simulation algorithm (see Figure 8.408) simulates the power and rate controls, congestion, and radio resource control performed for CDMA2000 1xEV-DO users. Atoll considers each user in the order established during the generation of the user distribution, determines his best server and his active set. Atoll performs the reverse link power control on the pilot channel. On the forward link, there is no power control; the transmitter transmits at full power. Instead, Atoll performs rate control based on the CI ratio calculated for the mobile.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

757

Atoll User Manual After performing rate and power control, Atoll updates the reverse link load factor. Atoll then carries out congestion and radio resource control, verifying the cell reverse link load and the number of channel elements and MAC indexes consumed by the cell.

Figure 8.408: Power control simulation for CDMA2000 1xEV-DO During reverse link power control, if the service supports downgrading, Atoll may downgrade the rate on the reverse link traffic data channel until the required reverse link quality level is reached. If downgrading does not allow the quality level to be reached, the mobile is rejected. During congestion control, if the service supports downgrading, Atoll may adjust the rate on the reverse link traffic data channel of mobiles until the reverse link cell noise rise is between the noise rise threshold plus the acceptable noise rise margin and the noise rise threshold minus the acceptable noise rise margin. Atoll starts downgrading or upgrading 1xEVDO Rev. 0 users and then if necessary, it continues with 1xEV-DO Rev. A users. If the noise rise is too high, Atoll downgrades all 1xEV-DO Rev. 0 users that can be downgraded. Then, if the noise rise is still too high, it downgrades 1xEV-DO Rev. A users, starting with the users with the highest rates. When the noise rise is too low, Atoll upgrades all 1xEV-DO Rev. 0 users that can be upgraded. Then, if the noise rise is still too low, it upgrades 1xEV-DO Rev. A users starting with the users with the lowest rates. A 1xEV-DO Rev. 0 user can be downgraded or upgraded if the transition flag of his rate was set to "True" during the generation of the user distribution. At this point, users can be either connected or rejected. They are rejected if: The signal quality is not sufficient: On the forward link, 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 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."

The network is saturated:

8.2.4.2

Creating Simulations
In Atoll, simulations enable you to model CDMA network regulation mechanisms used to minimise interference and maximise capacity. You can create one simulation or a group of simulations that will be performed in sequence. To create a simulation or a group of simulations: 1. Click the Data tab in the Explorer window. 2. Right-click the CDMA/CDMA2000 Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name and Comments for this simulation or group of simulations. 5. Under Execution on the General tab, you can set the following parameters:

758

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Number of Simulations: Enter the number of simulations to be carried out. All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. Information to retain: You can select the level of detail that will be available in the output: Only the Average Simulation and Statistics: None of the individual simulations are displayed or available in the group. Only an average of all simulations and statistics is available. Some calculation and display options available for prediction studies 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 Anformation About Mobiles: All the simulations are listed and can be displayed. The properties window for each simulation contains an additional tab with output related to mobiles. Detailed Information About Mobiles: All the simulations are listed and can be displayed. The properties window for each simulation contains additional mobile-related output on the Mobiles and Mobiles (Shadowing values) tabs.

Note:

Tip:

When you are working on very large radio-planning projects, you can reduce memory consumption by selecting Only the Average Simulation and Statistics under Information to retain.

6. Under Cell Load Constraints on the General tab, you can set the constraints that Atoll must respect during the simulation: Number of Channel Elements: Select the Number of Channel Elements check box if you want Atoll to respect the maximum number of channel elements defined for each site. Number of Codes: Select the Number of Codes check box if you want Atoll to respect the number of Walsh codes available for each cell. UL Load Factor: If you want the reverse link load factor to be verified in the simulation and not to exceed the Max UL Load Factor, select the UL Load Factor check box and define a value for the Max UL Load Factor. Max UL Load Factor: If you want to enter a global value for the maximum reverse link cell load factor, click the button ( ) beside the box and select Global Threshold. Then, enter a maximum reverse link cell load factor. If you want to use the maximum reverse link 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 forward link load to be verified in the simulation and not to exceed the Max DL Load, select the DL Load (% Pmax) check box and enter a maximum forward link cell load in the Max DL Load box. Max DL Load (% Pmax): If you want to enter a global value for the maximum forward link cell load, as a percentage of the maximum power, click the button ( ) beside the box and select Global Threshold. Then, enter a maximum forward link cell load, as a percentage of the maximum power. If you want to use the maximum forward link cell load as defined in the properties for each cell, click the button ( select Defined per Cell. 7. On the Source Traffic tab, enter the following: Global Scaling Factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). Select Traffic Maps to Be Used: Select the traffic maps you want to use for the simulation. You can select traffic maps of any type. However, if you have several different types of traffic maps and want to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 747. 8. Click the Advanced tab. 9. Under Generator Initialisation, enter an integer as the generator initialisation value. If you enter "0", the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. ) beside the box and

Tip:

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.

10. Under Convergence, enter the following parameters: Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the reverse link that must be reached between two iterations. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

759

Atoll User Manual DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the forward link that must be reached between two iterations.

11. Once you have defined the simulation, you can run it immediately or you can save it to run it later: Run: Click Run to save the defined simulation and run it immediately OK: Click OK to save the defined simulation without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. You can now use the completed simulations for specific CDMA coverage predictions (see "Making Coverage Predictions Using Simulation Results" on page 772) or for an AS analysis using the Point Analysis window (see "Making an AS Analysis of Simulation Results" on page 771).

8.2.4.3

Displaying the Traffic Distribution on the Map

Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to service, activity status, or soft handoff gain. You can set the display of the traffic distribution according to discrete values and then select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 33. In this section are the following examples of traffic distribution display: "Displaying the Traffic Distribution by Handoff Status" on page 760 "Displaying the Traffic Distribution by Connection Status" on page 761 "Displaying the Traffic Distribution by Service" on page 761.

Tip:

You can make the traffic distribution easier to see by hiding geo data and predictions. For information, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.

8.2.4.3.1

Displaying the Traffic Distribution by Handoff Status

In this example, the traffic distribution is displayed by the handoff status. To display the traffic distribution by the handoff status: 1. Click the Data tab in the Explorer window. 2. Right-click the CDMA/CDMA2000 Simulations folder. The context menu appears. 3. Select Properties from the context menu. The CDMA/CDMA2000 Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "HO Status (Sites/No. Transmitters Act. Set)" as the Field. The handoff status is displayed as "XY" where "Y" is the number of transmitters to which the mobile is connected and "X" is the number of sites. For example, "12" means that the mobile is connected to two different transmitters on one site. "23" would mean that the mobile is connected to three different transmitters on two sites. If a mobile is not connected, the handoff status is given as "00". 5. Click OK. The traffic distribution is now displayed by handoff status (see Figure 8.409).

Figure 8.409: Displaying the traffic distribution by handoff status

760

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

8.2.4.3.2

Displaying the Traffic Distribution by Connection Status

In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Click the Data tab in the Explorer window. 2. Right-click the CDMA/CDMA2000 Simulations folder. The context menu appears. 3. Select Properties from the context menu. The CDMA/CDMA2000 Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Connection Status" as the Field. 5. Click OK. The traffic distribution is now displayed by connection status (see Figure 8.410).

Figure 8.410: Displaying the traffic distribution by connection status

8.2.4.3.3

Displaying the Traffic Distribution by Service

In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Click the Data tab in the Explorer window. 2. Right-click the CDMA/CDMA2000 Simulations folder. The context menu appears. 3. Select Properties from the context menu. The CDMA/CDMA2000 Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 8.411).

Figure 8.411: Displaying the traffic distribution by service

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

761

Atoll User Manual

8.2.4.4

Displaying the User Active Set on the Map

Atoll enables you to display on the map the active set for each user generated by a simulation. To display the active set for a user: On the map, click and hold the icon of the user whose best and second-best servers you want to display. The servers in the users active set are connected to the user with lines the same colour as the serving transmitter. The best server is indicated with the number "1", the second-best with number "2" and so on. Figure 8.412 shows a user with three servers in his active set.

Figure 8.412: The active set of a user

8.2.4.5

Displaying the Results of a Single Simulation

After you have created a simulation, as explained in "Creating Simulations" on page 758, you can display the results. To access the results of a single simulation: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( you want to access. ) to expand the CDMA/CDMA2000 Simulations folder. ) to expand the folder of the simulation group containing the simulation whose results

4. Right-click the simulation. The context menu appears. 5. Select Properties from the context menu. The simulation properties dialogue appears. One tab gives statistics of the results of the simulation. Other tabs in the simulation properties dialogue contain simulation results as identified by the tab title. A final tab lists the initial conditions of the simulation. The amount of detail available when you display the results depends on the level of detail you selected from the Information to retain list on the General tab of the properties dialogue for the group of simulations. For more information on the different options, see step 5. of "Creating Simulations" on page 758. The Statistics tab: The Statistics tab contains the following two sections: Request: Under Request, you will find data on the connection requests: Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet 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 rates 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 rates) 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 a dual-band network, the number of users per activity status, and the reverse link and forward link total rates they generate. The breakdown per service (total number of users, number of users per frequency band for a dual-band network, number of users per activity status, and reverse link and forward link rates) 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.

762

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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. Service kbps Throughput FCH (Uplink and Downlink): The throughput in kbitss for each service on the FCH. The result is detailed on the forward and reverse link only when relevant. Service kbps Throughput SCH (Uplink and Downlink): The throughput in kbitss for each 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. 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. BTS Noise Figure (dB): The BTS 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 dialogue). 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 userdefined 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 intra-cell 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), softersoft (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. Kbps Throughput (FCH Uplink and Downlink): The throughput of the FCH on the forward and reverse links. Kbps Throughput (SCH Uplink and Downlink): 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

763

Atoll User Manual 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, Multiple Causes, 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: 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. BTS Noise Figure (dB): The BTS 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, 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 dialogue). 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 intra-cell 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. No. of Active Users: The number of active users connected to the cell. No. of Inactive Users: The number of inactive users among the users connected to the cell. 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, Multiple Causes, 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 Mobiles (1xRTT) tab: The Mobiles (1xRTT) tab contains the following information for CDMA2000 1xRTT users: Note: The Mobiles (1xRTT) tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 758, 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: The assigned user profile. Mobility: The mobility type assigned during the first random trial during the generation of the user distribution. Activity: The activity status assigned during the first random trial during the generation of the user distribution. DL and UL Total Requested Rate (kbps): The downlink and uplink total requested rates correspond to the forward and reverse data rates requested by the user before power control. DL and UL Total Obtained Rate (kbps): The total obtained rates are the same as the total requested rates 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 total obtained rate 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.

764

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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/I0 AS1, AS2, AS3, AS4, AS5, AS6 (dB): EcI0 is given in a separate column for each cell in the active set. The Ec/I0 AS1 column lists the Ec/I0 from the best server for the rejected mobiles as well. Indoor: This field indicates whether indoor losses have been added or not.

The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on page 758, 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 rate will be downgraded if the requested rate 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. I Intra ( ic ) = ( 1 F Ortho ) P tot ( ic )
txi 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. I extra ( ic ) =
DL

Ptot ( ic ) txj, j i
DL

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: Note: The Mobiles (1xEV-DO) tab only applies to CDMA2000 projects and only appears if, when creating the simulation as explained in "Creating Simulations" on page 758, 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: The assigned user profile. Mobility: The mobility type assigned during the first random trial during the generation of the user distribution. Activity: The activity status assigned during the first random trial during the generation of the user distribution. UL Total Requested Rate (kbps): The UL Total Requested Rate corresponds to the data rate, including the control channel rate, requested by the user before power control. UL Total Obtained Rate (kbps): The total obtained rate is the same as the total requested rate 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 total obtained rate is zero.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

765

Atoll User Manual DL Max Data Rate: The maximum data rate on the forward link depends on the value of CI at the terminal. Atoll calculates this value from the Max rate=f(CI) graph specified in the mobility type properties. Carrier: The carrier used for the mobile-transmitter connection. 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. 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/I0 AS1, AS2, AS3, AS4, AS5, AS6 (dB): EcI0 is given in a separate column for each cell in the active set. The Ec/I0 AS1 column lists the Ec/I0 from the best server for the rejected mobiles as well. Indoor: This field indicates whether indoor losses have been added or not.

The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on page 758, you select "Detailed information about mobiles" under Information to Retain: UL Requested Data Peak Rate (kbps): The uplink requested data peak rate corresponds to the data rate requested by the user before power control. UL Obtained Data Peak Rate (kbps): The uplink obtained data peak rate is the same as the requested data peak rate 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 data peak rate is zero. UL Downgrading Factor: The downgrading factor on the reverse link. The downgrading factor is used to calculated how much the data rate will be downgraded if the requested rate cannot be provided. DL CI (Pilot) (dB): CI for the pilot on the forward link. 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 rate transition and for each 1xEV-DO user. If the flag for a rate transition is "True," the rate 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 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. Note: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 758, you select "Detailed information about mobiles" under Information to Retain.

Name: The name assigned to the mobile. Value at Receiver (dB): The value of the shadowing error at the receiver. This value is the same for a given receiver for each given receiver-potential transmitter link. The value is generated randomly. Clutter: The clutter class on which the mobile is located. Path To: The name of the potential transmitter. Value (dB): The shadowing error for the receiver-potential transmitter link in the corresponding Path To column. These values are generated randomly.

The Initial Conditions tab: The Initial Conditions tab contains the following information: The global transmitter parameters: The spreading width Whether the power values on the forward link are absolute or relative to the pilot The default reverse link soft handoff gain Whether the MRC in softer/soft is defined or not The method used to calculate Nt Whether the reverse link 1xRTT power control is based on the traffic quality or the pilot quality.

766

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks The input parameters specified when creating the simulation: The maximum number of iterations The global scaling factor The generator initialisation value The reverse link and forward link convergence thresholds The simulation constraints such as maximum power, the maximum number of channel elements, the reverse link load factor and the maximum load The name of the traffic maps used.

The parameters related to the clutter classes, including the default values.

8.2.4.6

Displaying the Average Results of a Group of Simulations

After you have created a group of simulations, as explained in "Creating Simulations" on page 758, you can display the average results of the group. If you wish to display the results of a single simulation of a group, see "Displaying the Results of a Single Simulation" on page 762. To access the averaged results of a group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Simulations folder.

3. Right-click the group of simulations whose results you want to access. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. The Statistics tab: The Statistics tab contains the following two sections: Request: Under Request, you will find data on the connection requests: Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet 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 rates 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 rates) 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 dual-band networks, the number of users per activity status, and the reverse link and forward link total rates they generate. The breakdown per service (total number of users, number of users per frequency band for dual-band networks, number of users per activity status, and reverse link and forward link rates) is given.

Results: Under Results, you will find data on the connection results: -

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 dialogue). 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 intra-cell 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 userdefined 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 Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

767

Atoll User Manual 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), softersoft (23) and soft-soft (33) handoffs; the other handoff status (other HO) are grouped. Kbps Throughput (FCH Uplink and Downlink): The throughput of the FCH on the forward and reverse links. Kbps Throughput (SCH Uplink and Downlink): 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, Multiple Causes, 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 dialogue). 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 intra-cell 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), softersoft (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, Multiple Causes, 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 global transmitter parameters: The spreading width Whether the power values on the forward link are absolute or relative to the pilot The default reverse link soft handoff gain Whether the MRC in softer/soft is defined or not The method used to calculate Nt Whether the reverse link 1xRTT power control is based on the traffic quality or the pilot quality. The maximum number of iterations The global scaling factor The generator initialisation value The reverse link and forward link convergence thresholds The simulation constraints such as maximum power, the maximum number of channel elements, the reverse link load factor and the maximum load The name of the traffic maps used.

The input parameters specified when creating the group of simulations:

The parameters related to the clutter classes, including the default values.

8.2.4.7

Updating Cell Values With Simulation Results

After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 758, you can update values for each cell with the results calculated during the simulation. The following values are updated: UL Load Factor Total DL Power Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

768

Chapter 8: CDMA2000 Networks To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the CDMA/CDMA2000 Simulations folder.

c. Right-click the group of simulations whose results you want to access. d. Select Average Simulation from the context menu. A properties dialogue appears. To display the results for a single simulation: a. Click the Data tab in the Explorer window. b. Click the Expand button ( c. Click the Expand button ( sults you want to access. ) to expand the CDMA/CDMA2000 Simulations folder. ) to expand the folder of the simulation group containing the simulation whose re-

d. Select Properties from the context menu. The simulation properties dialogue appears. 2. Click the Cells tab. 3. On the Cells tab, click Commit Results. The following values are updated for each cell: UL Load Factor Total DL Power.

8.2.4.8

Adding New Simulations to an Atoll Document

When you have created a simulation or group of simulations, you can re-examine the same conditions by adding new simulations to the Atoll document. In Atoll, there are the following ways of adding new simulations: Adding to a group: When you add one or more simulations to an existing group of simulations, Atoll reuses the same input (radio, traffic, and simulation parameters) as those used to generate the group of simulations. It then generates a new user distribution and performs the power control simulation. To add a simulation to a group of simulations, see "Adding a Simulation to a Group of Simulations" on page 769. Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution (users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shadowing error distribution between simulations is different. Traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) may be taken into account or not. Finally, radio data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the power control (or rate/power control) simulation. To replay a group of simulations, see "Replaying a Group of Simulations" on page 770. Using the Generator Initialisation Number: When you create groups of simulations using the same generator initialisation number (which must be an integer other than 0) Atoll generates the same user and shadowing error distributions (user with a service, a mobility, an activity status and a shadowing error) in all groups using the same number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers allowed, EbNt thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during the power control simulation. By creating and calculating one group of simulations, making a change to the network and then creating and calculating a new group of simulations using the same generator initialisation number, you can see the difference your parameter changes make. To create a new simulation to a group of simulations using the generator initialisation number, see "Adding a Simulation to a Group of Simulations" on page 769. Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation parameters as those used to generate the group of simulations. You can then modify the simulation parameters before calculating the group. To duplicate a group of simulations, see "Duplicating a Group of Simulations" on page 770.

Adding a Simulation to a Group of Simulations

To add a simulation to an existing group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Simulations folder.

3. Right-click the group of simulations to which you want to add a simulation. The context menu appears. 4. Select New from the context menu. The properties dialogue of the group of simulations appears. Note: When adding a simulation to an existing group of simulations, the parameters originally used to calculate the group of simulations are used for the new simulations. Consequently, few parameters can be changed for the added simulation.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

769

Atoll User Manual 5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations. 6. Under Execution on the General tab, you can set the following parameters: Number of Simulations: Enter the number of simulations to added to this group of simulations.

7. Once you have added the simulation, you can run it immediately or you can save it to run it later: Run: Click Run to save the defined simulation and run it immediately OK: Click OK to save the defined simulation without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

Replaying a Group of Simulations

To replay an existing group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Simulations folder.

3. Right-click the group of simulations you want to replay. The context menu appears. 4. Select Replay from the context menu. The properties dialogue of the group of simulations appears. Note: When replaying an existing group of simulations, some parameters originally used to calculate the group of simulations are reused for the replayed group. Consequently, few parameters can be changed for the replayed group.

5. In the General tab of the dialogue, you can set the following parameters: Select the level of detail as explained in "Creating Simulations" on page 758 that will be available in the output from the Information to retain list. Under Cell Load Constraints, you can set the constraints as explained in "Creating Simulations" on page 758 that Atoll must respect during the simulation.

6. In the Source Traffic tab of the dialogue, select the Refresh Traffic Parameters check box if you want to take into account traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) in the replayed simulation. 7. In the Advanced tab, you can set the following parameters: Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the uplink that must be reached between two iterations. DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the downlink that must be reached between two iterations.

8. Click Run. Atoll immediately begins the simulation.

Creating a New Group of Simulations Using the Generator Initialisation Number

To create a new group of simulations using the generator initialisation number: 1. Click the Data tab in the Explorer window. 2. Right-click the CDMA/CDMA2000 Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new group of simulations appears. 4. Click the Advanced tab. 5. Under Generator Initialisation, enter an integer as the generator initialisation value. The integer must be the same generator initialisation number as used in the group of simulations with the user and shadowing error distributions you want to use in this group of simulations. If you enter "0", the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. 6. For information on setting other parameters, see "Creating Simulations" on page 758.

Tip:

You can create a new group of simulations with the same parameters as the original group of simulations by duplicating an existing one as explained in "Duplicating a Group of Simulations" on page 770.

Duplicating a Group of Simulations

To duplicate an existing group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Simulations folder.

3. Right-click the group of simulations you want to duplicate. The context menu appears.

770

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 4. Select Duplicate from the context menu. The properties dialogue for the duplicated group of simulations appears. You can change the parameters for the duplicated simulation or group of simulations as explained in "Creating Simulations" on page 758.

8.2.4.9

Estimating a Traffic Increase

When you create a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increased traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a group of simulations by: Creating a new group of simulations as described in "Creating Simulations" on page 758. Duplicating an existing group of simulations as described in "Adding New Simulations to an Atoll Document" on page 769.

2. Click the Source Traffic tab of the properties dialogue. 3. Enter a Global Scaling Factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).

8.2.5

Analysing the Results of a Simulation

In Atoll, you have several methods available to help you analyse simulation results. You can make an active set analysis of a real-time probe user or you can make a coverage study where each pixel is considered as a probe user with a defined terminal, mobility, and service. The analyses are based on a single simulation or on an averaged group of simulations. You can find information on the analysis methods in the following sections: "Making an AS Analysis of Simulation Results" on page 771 "Making Coverage Predictions Using Simulation Results" on page 772.

8.2.5.1

Making an AS Analysis of Simulation Results

The Point Analysis window gives you information on reception for any point on the map. The AS Analysis tab gives you 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. Analysis is based on the reverse link load factor and the forward link total power of cells. In this case, these parameters can be either outputs of a given simulation, or average values calculated from a group of simulations. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 803. Before you make an AS analysis: Ensure the simulation or group of simulations you want to use in the AS analysis is displayed on the map. Replay the simulation or group of simulations you want to use if you have modified radio parameters since you made the simulation. Note: The AS analysis does not take possible network saturation into account. Therefore, there is no guarantee that a simulated mobile with the same receiver characteristics can verify the point analysis, simply because the simulated network may be saturated.

To make an AS analysis of simulation results: 1. Click the Point Analysis button ( 2. Click the AS Analysis tab. 3. At the top of the AS Analysis tab, select from the Load Conditions list, the simulation or group of simulations you want to base the AS analysis on. 4. Select the Terminal, Service, Mobility, Carrier, and DL and UL Rates. 5. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. 6. Select or clear the following options: Whether shadowing is to be taken into account (and, if so, the cell edge coverage probability). Whether indoor coverage is to be taken into account. ) on the toolbar. The Point Analysis window appears. (see Figure 8.383).

7. Click OK to close the Properties dialogue. 8. Move the pointer over the map to make an active set analysis for the current location of the pointer.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

771

Atoll User Manual As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 8.401 on page 726). Information on the current position is given on the AS Analysis tab of the Point Analysis window. See Figure 8.402 on page 726 for an explanation of the displayed information. 9. 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. 10. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.

8.2.5.2

Making Coverage Predictions Using Simulation Results

When no simulations are available, Atoll uses the reverse link load factor, the total forward link power defined for each cell to make coverage predictions. For information on cell properties, see "Creating or Modifying a Cell" on page 674; for information on modifying cell properties, see "Cell Definition" on page 671. Once you have made simulations, Atoll can use this information instead of the defined parameters in the cell properties to make coverage predictions where each pixel is considered as a probe user with a terminal, mobility, profile, and service. For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, choosing either an average analysis of all simulations in the group or a statistical analysis based on a defined probability. The coverage predictions that can use simulation results are: Coverage predictions on the pilot or on a service: Pilot Reception Analysis: For information on making a pilot reception analysis, see "Making a Pilot Signal Quality Prediction" on page 716. Service Area Downlink: For information on making a coverage prediction on the forward link service area, see "Studying Service Area (EbNt) Uplink and Downlink for 1xRTT" on page 717 or "Studying the Forward Link EV-DO Throughput" on page 718. Service Area Uplink: For information on making a coverage prediction on the reverse link service area, see "Studying Service Area (EbNt) Uplink and Downlink for 1xRTT" on page 717 or "Studying Service Area (EbNt) Reverse Link for EV-DO" on page 719. Effective Service Area: For information on making a pilot pollution coverage analysis, see "Studying Effective Service Area" on page 720. Downlink Total Noise: For information on making a forward link total noise coverage prediction, see "Studying Forward Link Total Noise" on page 722. Pilot Pollution: For information on making a pilot pollution coverage analysis, see "Calculating Pilot Pollution" on page 723. Handoff Status: For information on making a handoff status coverage prediction, see "Making a Handoff Status Coverage Prediction" on page 724.

Coverage predictions on noise and interference: -

A handoff status coverage prediction to analyse macro-diversity performance: -

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 Condition 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 Condition 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.

8.3

Verifying Network Quality

An important step in the process of creating a CDMA network is verifying the quality of the network. This is done using measurements of the strength of the pilot signal and other parameters in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: "Importing a Drive Test Data Path" on page 773 "Displaying Drive Test Data" on page 775 "Defining the Display of a Drive Test Data Path" on page 775 "Network Verification" on page 776

772

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks "Exporting a Drive Test Data Path" on page 781 "Extracting CW Measurements from Drive Test Data" on page 781 "Printing and Exporting the Drive Test Data Window" on page 782.

8.3.1

Importing a Drive Test Data Path

In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In CDMA networks, a cell is identified by its PN offset. Therefore, you must indicate during the import process which columns contain the PN offset of cells. Because a PN offset can belong to several groups, you can also indicate from which group the PN offset has been selected.

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. Click the Data tab in the Explorer window. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. You can import one or several files. Select the file or files you want to open. Note: If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import.

5. Click Open. The Import of Measurement Files dialogue appears. Note: Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue.

6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Configuration, select an import configuration from the Configuration list. b. Continue with step 10. Notes: When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. In case several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual. 7. Click the General tab. On the General tab, you can set the following parameters: Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

773

Atoll User Manual document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document. 8. Click the Setup tab (see Figure 8.413).

Figure 8.413: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click Setup to link file columns and internal Atoll fields. The Drive Test Data Configuration dialogue appears. c. 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. Note: 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. In the PN 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 Group Identifier box empty. e. In the PN Offset Identifier box, enter a string that must be 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 will then search for columns with this string in the column name. f. Ensure that the PN offset format selected in the PN Offset Format list is "Decimal."

g. Click OK to close the Drive Test Data Configuration dialogue. Important: If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Configuration dialogue, Atoll should recognize all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>". If a column is marked with "<Ignore>", it will not be imported.

774

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 9. If you wish 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 Configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a special 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, "*.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. Notes: 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 button ( ) in front of the file in the Setup part to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Setup 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.

8.3.2

Displaying Drive Test Data

When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see information about the active set at that location. To display information about a single drive test data point: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want active set information. Atoll displays an arrow pointing towards the serving cells (see Figure 8.415 on page 780), with a number identifying the server as numbered in the drive test data. If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display Type" on page 33.

8.3.3

Defining the Display of a Drive Test Data Path

You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to manage permanent labels on the map, tooltips and the legend. In other words, the display of measurement path are managed in the same way as sites, transmitters, etc. To display the Display tab of a drive test data paths Properties dialogue: 1. Click the Data tab in the Explorer window. 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: a text or integer attribute (discrete value) a numerical value (value interval).

In addition, you can display points by more than one criterion at a time using the Advanced option in the Display Type list. When you select Advanced from the Display Type list, a dialogue opens in which you can define the following display for each single point of the measurement path: a symbol according to any attribute a symbol colour according to any attribute a symbol size according to any attribute

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

775

Atoll User Manual 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. Notes: Fast Display forces Atoll to use the lightest symbol to display the points. This is particularly useful when you have a very large number of points. You can not use Advanced Display if the Fast Display check box has been selected. You can sort drive test data paths in alphabetical order on the Data tab of the Explorer window by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can export the display settings of a drive test data path in a configuration file to make them available for future use. You can export the display settings or import display settings by clicking the Actions button on the Display tab of the drive test data paths Properties dialogue and selecting Export or Import from the menu.

8.3.4

Network Verification
The imported drive test data is used to verify the CDMA network. To improve the relevance of the data, Atoll allows you to filter out incompatible or inaccurate points. You can then compare the imported measurements with previously calculated coverage predictions. In this section, the following are explained: "Filtering Incompatible Points Along Drive Test Data Paths" on page 776 "Creating Coverage Predictions from Drive Test Data Paths" on page 777 "Displaying Statistics Over a Drive Test Data Path" on page 778 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 779 "Analysing Data Variations Along the Path" on page 779.

8.3.4.1

Filtering Incompatible Points Along Drive Test Data Paths

When using a drive test data path, some measured points may present values that are too far outside of the median values to be useful. As well, test paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder.

The context menu appears. 3. Select Filter from the context menu. The Drive Test Data Filter dialogue 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. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder.

The context menu appears. 3. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 4. Click More. The Filter dialogue appears.

776

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 5. Click the Filter tab: a. Select a Field from the list. b. Under Values to Include, you will find all the values represented in the selected field. Select the check boxes next to the values you want to include in the filter. Click Clear All to clear all check boxes. 6. Click the Advanced tab: a. In the Column row, select the name of the column to be filtered on from the list. Select as many columns as you want (see Figure 8.414).

Figure 8.414: The Filter dialogue - Advanced tab b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table:

Formula
=X <> X <X >X <=X >=X *X* *X X*

Data are kept in the table only if

value equal to X (X may be a number or characters) value not equal to X (X may be a number or characters) numerical value is less than X numerical value is greater than X numerical value is less than or equal to X numerical value is greater than or equal to X text objects which contain X text objects which end with X text objects which start with X

7. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. For more information on how filters work, see "Advanced Data Filtering" on page 75. Note: You can permanently delete the points that do not fulfil the filter conditions by selecting the Delete points outside the filter check box.

8. Click OK to apply the filter and close the dialogue.

8.3.4.2

Creating Coverage Predictions from Drive Test Data Paths

You can create the following coverage predictions for all transmitters on each point of a drive test data path: Pilot signal level and coverage by signal level Pilot reception analysis (EcI0), service area (EbNt) downlink, and service area (EbNt) uplink.

To create a coverage prediction along a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

777

Atoll User Manual 4. Select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. 5. Under Standard Studies, select one of the following coverage predictions and click OK: Coverage by Signal Level: Click the Condition tab. At the top of the Condition tab, you can set the range of signal level to be calculated. Under Server, you can select whether to calculate the signal level from all transmitters, or only the best or second-best signal. If you choose to calculate the best or second-best signal, you can enter a Margin. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. Finally, you can select the Carrier to be studied. On the Condition 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 710. 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. On the Condition 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 710. 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. On the Condition 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 710. 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.

Pilot Reception Analysis (EcI0): Click the Condition tab. -

Service Area (EbNt) Downlink: Click the Condition tab.

Service Area (EbNt) Uplink: Click the Condition tab.

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 Studies from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see "Chapter 5: Managing Calculations in Atoll"). You can display the information in these new columns in the Drive Test Data window. For more information on the Drive Test Data window, see "Analysing Data Variations Along the Path" on page 779.

8.3.4.3

Displaying Statistics Over a Drive Test Data Path

Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path.

778

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks To display the statistics for a specific Drive Test Data path: 1. Click the Data tab in the Explorer window. 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 dialogue 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.

8.3.4.4

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. Click the Data tab in the Explorer window. 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 dialogue 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.

8.3.4.5

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. Click the Data tab in the Explorer window. 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 dialogue appears. 5. Select a transmitter from the On the Transmitter list. 6. Click the For the Fields list. The list opens. 7. Select the check box beside the field you want 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.

8.3.4.6

Analysing Data Variations Along the Path

In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

779

Atoll User Manual To analyse data variations using the Drive Test Data window. 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 8.415).

Figure 8.415: The Drive Test Data window 5. Click Display at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 8.416).

Figure 8.416: The Drive Test Data window 6. In the Display Parameters dialogue: Select the check box next to any field you want to display in the Drive Test Data window. If you 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 dialogue. Note: 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:

780

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks Click the values in the Drive Test Data window. Click the points on the drive test path in the map window.

The drive test data path appears in the map window as an arrow pointing towards the serving cell, with a number identifying the best server (see Figure 8.415 on page 780). If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display Type" on page 33. 8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the secondary Y-axis from the right-hand list on the top of the Drive Test Data window. The selected values are displayed in the colours defined for this variable in the Display Parameters dialogue. 9. You can change the zoom level of the Drive Test Data window display in the Drive Test Data window in the following ways: Zoom in or out: i. Right-click the Drive Test Data window.

ii. Select Zoom In or Zoom Out from the context menu. Select the data to zoom in on: i. Right-click the Drive Test Data window on one end of the range of data you want to zoom in on.

ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data window on the other end of the range of data you want to zoom in on. iv. Select Last Zoom Point from the context menu. The Drive Test Data window zooms in on the data between the first zoom point and the last zoom point. 10. Click the data in the Drive Test Data window to display the selected point in the map window. Atoll will recentre the map window on the selected point if it is not presently visible.

Tip:

If you open the table for the drive test data you are displaying in the Drive Test Data window, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data window (see Figure 8.415 on page 780).

8.3.5

Exporting a Drive Test Data Path

You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.

8.3.6

Extracting CW Measurements from Drive Test Data

You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears. 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the Transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the For the Fields list. 6. Under CW Measurement Creation Parameters: a. Enter the Min. Number of Points to Extract per Measurement Path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured Signal Levels. CW measurements are created with drive test data points where the signal levels are within this specified range.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

781

Atoll User Manual 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.

8.3.7

Printing and Exporting the Drive Test Data Window

You can print or export the contents of the Drive Test Data window, using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 8.415 on page 780). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 779. 6. Right-click the Drive Test Data window. The context menu appears. To export the Drive Test Data window: a. Select Copy from the context menu. b. Open the document into which you want to paste the contents of the Drive Test Data window. c. Paste the contents of the Drive Test Data window into the new document. To print the Drive Test Data window: a. Select Print from the context menu. The Print dialogue appears. b. Click OK to print the contents of the Drive Test Data window.

8.4

Co-planning CDMA Networks with Other Networks

Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a CDMA and a GSM network for the same area in Atoll, and then work with Atolls co-planning features to study the mutual impacts of the two networks. Important: Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other networks Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In this section, the following are explained: "Switching to Co-planning Mode" on page 782. "Working with Coverage Predictions in a Co-Planning Project" on page 784. "Performing Inter-Technology Neighbour Allocation" on page 787. "Creating a CDMA Sector From a Sector in the Other Network" on page 797. "Ending Co-planning Mode" on page 797.

8.4.1

Switching to Co-planning Mode

Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a CDMA Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, the CDMA document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Important: Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems. To switch to co-planning mode: 1. Open the main document. Select File > Open or File > New > From an Existing Database. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

782

Chapter 8: CDMA2000 Networks 2. Link the other document with the open main document. a. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document. b. Select File > Link With. The Link With dialogue appears. c. Select the document to be linked. d. Click Open. The selected document is opened in the same Atoll session as the main document and the two documents are linked. The Explorer window of the main document now contains a folder named Transmitters in [linked document], where [linked document] is the name of the linked document and another folder named Predictions in [linked document]. Note: By default, only the Transmitters and Predictions folders of the linked document appear in the main document. If you want the Sites folder of the linked document to appear in the main document as well, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.

As soon as a link is created between the two documents, Atoll switches to co-planning mode and Atolls co-planning features are now available. When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll syncronises the display for the following: Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.

Displaying Both Networks in the Same Atoll Document

After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 782, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the Explorer window of the linked document to the Explorer window of the main document (e.g., you can display GSM sites and measurement paths in a CDMA document). To display sites from the linked document in the main document: 1. Click the linked documents map window. The linked documents map window becomes active and the Explorer window shows the contents of the linked document. 2. Click the Data tab of the Explorer window. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In > [main document] from the context menu, where [main document] is the name of the main document. 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 rightclicking 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 82. You can also set the tool tips to enable you to distinguish the objects and data displayed on the map. For more information on tool tips, see "Defining the Object Type Tip Text" on page 36. In order to more easily view differences between the networks, you can also change the order of the folders or items in the Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers Using the Explorer" on page 28.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

783

Atoll User Manual Figure 8.417 shows an example of CDMA transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in a tool tip.

Figure 8.417: GSM and CDMA Transmitters displayed on the map

8.4.2

Working with Coverage Predictions in a Co-Planning Project

Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: "Updating Coverage Predictions" on page 784 "Analysing Coverage Predictions" on page 785.

8.4.2.1

Updating Coverage Predictions

You can access the properties of the coverage predictions in the linked Predictions folder in the main documents Explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button ( ) in the toolbar.

When you click the Calculate button, Atollfirst calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 185. If you want, you can make Atoll recalculate all path loss matrices, including valid ones, before calculating unlocked coverage predictions in the main and linked Predictions folders. To force Atoll to recalculate all path loss matrices before calculating coverage predictions: Click the Force Calculate button ( ) in the toolbar.

When you click the Force Calculate button, Atoll first removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions defined in the main and linked Predictions folders.

784

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Note:

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.4.2.2

Analysing Coverage Predictions

In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tooltips to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which studies to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following are explained: "Co-Planning Coverage Analysis Process" on page 785 "Displaying the Legend Window" on page 785 "Comparing Coverage Prediction Results Using Tooltips" on page 786 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 786 "Studying Differences Between Coverage Areas" on page 786.

8.4.2.2.1

Co-Planning Coverage Analysis Process

The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. Note: In a co-planning environment, many sites share the same antennas, using one mast for both technologies. When transmitter, remote antenna, or repeater antennas have the same co-ordinates and the same value set for the SHAREDMAST field in both coplanning documents, Atoll assumes that the antennas are shared. Atoll then automatically synchronises changes made to shared antenna parameters in one coplanning document in the other document. The shared antenna parameters include the site location (X and Y coordinates), the antenna's position relative to the site (Dx, Dy), antenna height, azimuth and mechanical tilt. The SHAREDMAST field is not available by default and must be added in order for the synchronization mechanism to operate. For information on setting up shared antenna parameter synchronisation, see the Administrator Manual.

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 (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the main document. For more information, see "Making a Coverage Prediction by Transmitter" on page 699 and "Studying Signal Level Coverage" on page 689. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tool tip contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage predictions Properties dialogue. 4. Make the two new coverage predictions in the linked document accessible in the main document as described in "Displaying Both Networks in the Same Atoll Document" on page 783. 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 786 and "Studying Differences Between Coverage Areas" on page 786. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.

8.4.2.2.2

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to Legend check box on the Display tab.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

785

Atoll User Manual To display the Legend window: 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.

8.4.2.2.3

Comparing Coverage Prediction Results Using Tooltips

You can compare coverage predictions by by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltip. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Co-Planning Coverage Analysis Process" on page 785). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 8.391). The tooltip for the working document is on top and the tooltip for the linked document, with the linked document identified by name is on the bottom.

Figure 8.418: Comparing coverage prediction results using tooltips

8.4.2.2.4

Comparing Coverage Areas by Overlaying Coverage Predictions

You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is dislayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 32. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is dislayed on the map. 11. Right-click the coverage prediction. The context menu appears. 12. Select Properties from the context menu. The coverage prediction Properties dialogue 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 "Working with Layers Using the Explorer" on page 28.

8.4.2.2.5

Studying Differences Between Coverage Areas

You can compare coverage predictions to find differences in coverage areas.

786

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks To compare coverage predictions: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Right-click the coverage prediction of the main document you want to compare. The context menu appears. 5. Select Compare With > [linked coverage prediction] from the context menu, where [linked coverage prediction] is the linked coverage prediction you want to compare with the coverage prediction of the main document. The Comparison Properties dialogue opens. 6. Select the display parameters of the comparison and add a comment if you want. 7. Click OK. The two coverage predictions are compared and a comparison coverage prediction is added to the main documents Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 706.

8.4.3

Performing Inter-Technology Neighbour Allocation

The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between a CDMA and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to CDMA cells. In this section, the following are explained: "Setting Inter-Technology Exceptional Pairs" on page 787 "Configuring Importance Factors for Inter-Technology Neighbours" on page 789 "Allocating Inter-Technology Neighbours Automatically" on page 789 "Displaying Inter-Technology Neighbours on the Map" on page 791 "Allocating and Deleting Inter-Technology Neighbours per Cell" on page 792 "Calculating the Importance of Existing Inter-technology Neighbours" on page 794 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 796.

In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Co-planning Mode" on page 782.

8.4.3.1

Setting Inter-Technology Exceptional Pairs

You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Exceptional Pairs from the context menu. The Exceptional Pairs of Inter-technology Neighbours table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. d. Atoll fills the Number and Distance (m) fields automatically. In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector). You can access a cells inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cells Properties dialogue: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Double-click the row corresponding to the cell whose properties you want to access. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

787

Atoll User Manual In GSM, the Inter-technology Neighbours tab is found on the transmitters Properties dialogue.

Displaying Inter-Technology Exceptional Pairs on the Map

You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select which exceptional pair links to display: Outwards Non-Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Selecting this option displays an exceptional pair link for each transmitter/cell in the linked document that has an exceptional pair defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Forced Neighbours or Forbidden Neighbours from the menu. The exceptional pair of a cell will be displayed when you select a transmitter. 8. Click the Visual Management button ( ) in the Radio toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Visual Management button again. 9. Click a transmitter on the map to show its exceptional pair links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map.

Adding and Removing Inter-Technology Exceptional Pairs on the Map

You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-Technology Exceptional Pairs on the Map" on page 788. To add a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set an exceptional pair. Atoll adds both transmitters to the list of inter-technology exceptional pairs of the other transmitter. To remove a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes both transmitters from the list of inter-technology exceptional pairs of the other transmitter. To add an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set an exceptional pair. Atoll adds the reference transmitter to the list of inter-technology exceptional pairs of the other transmitter.

788

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks To remove an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the reference transmitter from the list of inter-technology exceptional pairs of the other transmitter. To add an inwards forced or forbidden exceptional pair: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric exceptional pair relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation. If there is no existing exceptional pair relation between the two transmitters, first create a symmetric exceptional pair relation between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation.

To remove an inwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the transmitter from the inter-technology exceptional pairs list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

8.4.3.2

Configuring Importance Factors for Inter-Technology Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. Note: In a GSM project, you must select Neighbours > Configure Importance from the Transmitters folders context menu.

4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when performing automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Inter-Technology Neighbours Automatically" on page 789.

5. Click OK.

8.4.3.3

Allocating Inter-Technology Neighbours Automatically

Atoll can automatically determine handover relations between networks of different technologies, for example, CDMA and GSM. In this case, inter-technology handovers from CDMA to GSM may occur when the CDMA coverage is not continuous. The networks overall coverage is extended by a CDMA-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database. To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 5. Click the Inter-technology Neighbours tab. 6. Define the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. 7. Define the maximum number of inter-technology neighbours that can be allocated to a cell in the Max Number of Neighbours box. This value can be either set here for all the cells, or specified for each cell in the Cells table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

789

Atoll User Manual 8. Clear the Use Overlapping Coverage check box in order to base the neighbour allocation on distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour allocation on coverage conditions. a. Click the Define button to change the coverage conditions for the cells in the main document. The CDMA Coverage Conditions dialogue appears. In the CDMA Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell. Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the best server in terms of pilot quality or a cell of the active set. Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the reference cell. DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink load for all the cells, or the downlink loads Defined per Cell. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is an LTE document, the LTE Coverage Conditions dialogue appears. In the LTE Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. e. In the % Min. Covered Area box, enter the minimum percentage of the cells coverage area that the neighbours coverage area should also cover to be considered as a neighbour. 9. Under Calculation Options, define the following: CDMA Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers; Atoll will allocate neighbours to cells using the selected carriers. Force co-site as neighbours: Selecting the Force co-site as neighbours check box will include the co-site transmitters/cells in the neighbour list of the CDMA cell. The check box is automatically selected when the neighbour allocation is based on distance. Force exceptional pairs: Selecting the Force exceptional pairs check box will apply the inter-technology exceptional pair criteria on the neighbours list of the CDMA cell. Delete existing neighbours: Selecting the Delete existing neighbours check box will delete all existing neighbours in the neighbours list and perform a clean neighbour allocation. If the Delete existing neighbours check box is not selected, Atoll keeps the existing neighbours in the list.

10. Click the Calculate button to start calculations. 11. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the names of the neighbours, the number of neighbours of each cell, and the reason they are included in the neighbours list. The reasons include:

790

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Reason
Exceptional Pair Co-site Distance % of covered area and overlapping area Existing

Description
Neighbour relation is defined as an exceptional pair. The neighbour is located at the same site as the reference cell. The neighbour is within the maximum distance from the reference cell. Neighbour relation that fulfils coverage conditions. The neighbour relation existed before running the automatic allocation.

When
Force exceptional pairs is selected Force co-site as neighbours is selected Use Coverage Overlapping is not selected Use Coverage Overlapping is selected Reset is not selected

12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

13. Click the Commit button. The allocated neighbours are saved in the Intra-technology Neighbours tab of each cell. 14. Click Close.

8.4.3.4

Displaying Inter-Technology Neighbours on the Map

You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select the neighbour links to display: Outwards Non-Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Neighbours as the type of neighbour links to display. 8. Click the Visual Management button ( ) in the Radio toolbar. Neighbours are now displayed on the map. Neighbours and displayed until you click the Visual Management button again.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

791

Atoll User Manual 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.

8.4.3.5

Allocating and Deleting Inter-Technology Neighbours per Cell

Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Intertechnology Neighbours table. This section explains the following: "Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 792. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 793. "Allocating and Removing Inter-Technology Neighbours on the Map" on page 794.

Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Cells tab of the transmitters Properties dialogue: 1. On the main documents map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. 6. If desired, you can enter the Maximum Number of Neighbours. 7. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, and sets the Type to "manual." 8. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column.

792

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 9. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 11. Click OK. In GSM, the inter-technology neighbours tab is available in each transmitters Properties dialogue.

Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table

To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Neighbours from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. To allocate an inter-technology neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Type to "manual." 7. To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 8. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. 9. To take all exceptionnal pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either forced neighbours or forbidden neighbours using the Exceptional Pairs of Inter-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu. ), select a reference cell in the Cell column.

10. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

793

Atoll User Manual 11. To delete several symmetric neighbour relations: a. Click in the left margin of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. a. Right-click the Neighbours table. The context menu appears. b. Select Delete Link and Symmetric Relation from the context menu. 12. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector).

Allocating and Removing Inter-Technology Neighbours on the Map

You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-Technology Neighbours on the Map" on page 791. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. T remove an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the list of inter-technology neighbours of the other transmitter. To add an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. There can be two cases: If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the inter-technology neighbours list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

8.4.3.6

Calculating the Importance of Existing Inter-technology Neighbours

After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing inter-technology neighbours: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window.

794

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. Note: In a GSM project, you must select Neighbours > Calculate Importance from the Transmitters folders context menu.

5. Select the Inter-technology Neighbours tab. 6. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance. 7. Clear the Use Overlapping Coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour importance calculation on coverage conditions. 8. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for the cells in the main document. The CDMA Coverage Conditions dialogue appears. In the CDMA Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell. Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the best server in terms of pilot quality or a cell of the active set. Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the reference cell. DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink load for all the cells, or the downlink loads Defined per Cell. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is an LTE document, the LTE Coverage Conditions dialogue appears. In the LTE Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. 9. If you cleared the Use Overlapping Coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

795

Atoll User Manual

Notes:

You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

10. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 5. Cause: The reason Atoll has calculated the value in the Importance column. Co-site Symmetry Coverage

Distance: The distance in kilometres between the reference cell and the neighbour.

11. Click Close. The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

8.4.3.7

Checking the Consistency of the Inter-technology Neighbour Plan

You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Nieghbours tab. 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want 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 transmitters, or specified for each transmitter in the Cells table. Lists > Max Number: Select the Lists > Max Number check box if you want 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 transmitters, or specified for each transmitter in the Cells table Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax: |CELL|

Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

796

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Note:

If the field Maximum number of inter-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

8.4.4

Creating a CDMA Sector From a Sector in the Other Network

You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main documents map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new CDMA transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder of the main document. The context menu appears. 4. Select Apply Current Configuration from the context menu.

Figure 8.419: New sector Before and after applying the configuration Note: 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.

8.4.5

Ending Co-planning Mode

once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

797

Atoll User Manual To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select File > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.

8.5

Advanced Configuration
In this section, the following advanced configuration options are explained: "Defining Inter-Carrier Interference" on page 798 "Defining Frequency Bands" on page 798 "The Global Transmitter Parameters" on page 799 "Data Rates Available for Services in CDMA" on page 800 "The 1xEV-DO Rev. A Radio Bearers" on page 801 "Site Equipment" on page 801 "Receiver Equipment" on page 802 "Conditions for Entering the Active Set" on page 803 "Modelling Shadowing" on page 804 "Creating PN Offset Domains and Groups for PN Offset Allocation" on page 805 "Modelling Inter-Technology Interference" on page 806.

8.5.1

Defining Inter-Carrier Interference

If you want Atoll to take into account the interference between two carriers, you must create a carrier pair with an interference reduction factor. Atoll will take the interference reduction factor into account on both the reverse link and the forward link. To create a pair of carriers with an interference reduction factor: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Intra-technology IRF from the context menu. The Inter-Carrier Interference Reduction Factor table appears. 4. For each carrier pair for which you want define inter-carrier interference: a. Enter the first carrier of the pair in the 1st Carrier column. b. Enter the second carrier of the pair in the 2nd Carrier column. c. Enter an interference reduction factor in the Reduction Factor (dB) column. When Atoll is calculating interference, it subtracts the interference reduction factor from the calculated interference. If the interference reduction factor is set to "0," Atoll assumes that the carriers in the defined pair generate as much interference as cells with the same carrier interference. Important: The interference reduction factor must be a positive value. For every pair of carriers that is not defined, Atoll assumes that there is no inter-carrier interference. d. Press ENTER to create the carrier pair and to create a new row in the table.

8.5.2

Defining Frequency Bands

To define frequency bands: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Bands from the context menu. 4. In the table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each frequency band, enter: Name: Enter a name for the frequency, for example, "Band 1900." This name will appear in other dialogues when you select a frequency band. Average Frequency (MHz): Enter the average frequency. First Carrier: Enter the number of the first carrier in this frequency band. Last Carrier: Enter the number of the last carrier in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First Carrier field.

798

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

Important: 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 5. Click the Carrier Types button. The Carrier Types table appears. 6. In the table, define the carriers and whether the carrier is 1xRTT or 1xEV-DO. 7. When you have finished describing carriers, click Close. 8. When you have finished adding frequency bands, click Close.

8.5.3

The Global Transmitter Parameters

On the Global Parameters tab of the Transmitters Properties dialogue, you can define many network parameters that are used in CDMA power control simulations and predictions. Many parameters are used as default values for all transmitters. This section explains the options available on the Global Parameters tab of the Transmitters Properties dialogue, and explains how to access the tab: "The Options on the Global Parameters Tab" on page 799 "Modifying Global Transmitter Parameters" on page 799.

8.5.3.1

The Options on the Global Parameters Tab

The Global Parameters tab has the following options: DL Powers: Under DL Powers, you can define whether the power values on the 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. Atollautomatically 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). Atollautomatically 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 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): - 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 Condition 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 Condition tab, Atoll calculates the reverse link macrodiversity 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.

8.5.3.2

Modifying Global Transmitter Parameters

You can change global transmitter parameters on the Global Parameters tab of the Transmitters Properties dialogue. To change global transmitter parameters: 1. Click the Data tab in the Explorer window. 2. Right-click on the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Transmitters Properties dialogue appears. 4. Click the Global Parameters tab. 5. Modify the parameters described in "The Options on the Global Parameters Tab" on page 799. 6. Click OK.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

799

Atoll User Manual

8.5.4

Data Rates Available for Services in CDMA

The different services offered by a CDMA network require different data rates. CDMA responds to the differing data rate requirements with a range of carriers. For example, CDMA2000 can provide voice using 1xRTT. Data services, which require higher data rates than voice, can be provided using 1xRTT or 1xEV-DO Rev. 0 or Rev. A. The following table gives the data rates available for voice, 1xRTT, and 1xEV-DO Rev. 0 and Rev. A.

Service
Speech 1xRTT Data

Reverse Link
N FCH * N FCH 3 X N FCH 5 X N FCH

Forward Link
N FCH N FCH 3 X N FCH 5 X N FCH 9 X N FCH 17 X N FCH 38.4 76.8 153.6 307.6 614.4 921.6 1228.8 1843.2 2457.6

For 1xRTT, N FCH can be 9.6 or 14.4 kbps on either the forward or reverse link.

9 X N FCH 17 X N FCH

1xEV-DO Rev. 0 Data

9.6 19.2 38.4 76.8 153.6

1xEV-DO Rev. A Data

4.8 9.6 19.2 38.4 76.8 115.2 153.6 230.4 307.2 460.8 614.4 921.6 1228.8 1848.2

4.8 9.6 19.2 38.4 76.8 115.2 153.6 230.4 307.2 460.8 614.4 921.6 1228.8 1848.2 2457.6 3072.0

* N FCH is the nominal throughput of FCH.

800

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

8.5.5

The 1xEV-DO Rev. A Radio Bearers

In Atoll, 1xEV-DO Rev. A forward and reverse link traffic channels are modelled using radio bearers. The 1xEV-DO Rev. A Radio Bearer tables list the 1xEV-DO Rev. A radio bearers with their RLC peak rate, index numbers, and packet size. You must define the 1xEV-DO Rev. A radio bearers before you can model services using them. In this section, the following are explained: "Defining the Forward Link 1xEV-DO Rev. A Radio Bearer" on page 801 "Defining the Reverse Link 1xEV-DO Rev. A Radio Bearer" on page 801.

8.5.5.1

Defining the Forward Link 1xEV-DO Rev. A Radio Bearer

The Downlink 1xEV-DO Rev. A Radio Bearer table lists the different transport block sizes that can be transmitted in one timeslot and the corresponding RLC peak rates. To create or modify a 1xEV-DO Rev. A forward link radio bearer: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select 1xEV-DO Rev. A Radio Bearer (DL) from the context menu. The Downlink 1xEV-DO Rev. A Radio Bearer table appears. 5. In the Downlink 1xEV-DO Rev. A Radio Bearer table, you can enter or modify the following fields: Radio Bearer Index: You can modify the index number of the radio bearer. This index number is used to identify the 1xEV-DO Rev. A forward link radio bearer. If you are creating a new 1xEV-DO Rev. A forward link radio bearer, enter an index number in the row marked with the New Row icon ( ). RLC Peak Rate (bps): Enter or modify the RLC peak rate in bits per second. Packet Size (bits): Enter or modify the packet size in bits transmitted in one timeslot.

8.5.5.2

Defining the Reverse Link 1xEV-DO Rev. A Radio Bearer

The Uplink 1xEV-DO Rev. A Radio Bearer table lists the different transport block sizes that can be transmitted in one subframe (i.e., 4 timeslots) and the corresponding RLC peak rates. To create or modify a 1xEV-DO Rev. A reverse link radio bearer: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select 1xEV-DO Rev. A Radio Bearer (UL) from the context menu. The Uplink 1xEV-DO Rev. A Radio Bearer table appears. 5. In the Uplink 1xEV-DO Rev. A Radio Bearer table, you can enter or modify the following fields: Radio Bearer Index: You can modify the index number of the radio bearer. This index number is used to identify the 1xEV-DO Rev. A reverse link radio bearer. If you are creating a new 1xEV-DO Rev. A reverse link radio bearer, enter an index number in the row marked with the New Row icon ( ). RLC Peak Rate (bps): Enter or modify the RLC peak rate in bits per second. Packet Size (bits): Enter or modify the packet size in bits transmitted in one subframe (4 timeslots).

8.5.6

Site Equipment
In this section, the following are explained: "Creating Site Equipment" on page 801 "Defining Channel Element Consumption per CDMA Site Equipment and Radio Configuration" on page 802.

8.5.6.1

Creating Site Equipment

To create a new piece of CDMA site equipment: 1. Click the Data tab in the Explorer window. 2. Right-click on the Sites folder. The context menu appears. 3. Select Equipment > Open Table from the context menu. The Equipment table appears. 4. In the Equipment table, each row describes a piece of equipment. For information on working with data tables, see "Working with Data Tables" on page 53. For the new piece of CDMA equipment you are creating, enter the following: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

801

Atoll User Manual MUD Factor: Multi-User Detection (MUD) is a technology used to decrease intra-cell interference on the reverse link. MUD is modelled by a coefficient from 0 to 1; this factor is considered in the reverse link interference calculation. In case MUD is not supported by equipment, enter 0 as value. Rake Factor: This factor enables Atoll to model the rake receiver on the reverse link. Atoll uses this factor to calculate the reverse link signal quality in simulations, point analysis and coverage studies. This parameter is considered on the reverse link for softer and softer-softer handoffs; 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. Note: The rake efficiency factor used to model the recombination on the forward link 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 (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 studies). 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 numbers 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. ) to close the table.

5. Click the Close button (

8.5.6.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. Click the Data tab in the Explorer window. 2. Right-click on the Sites folder. The context menu appears. 3. Select Equipment > Channel Element Consumption from the context menu. The CE Consumption table appears. 4. 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. 5. Click the Close button ( ) to close the table.

8.5.7

Receiver Equipment
In this section, the following are explained: "Setting Receiver Height" on page 802 "Creating or Modifying Reception Equipment" on page 803.

8.5.7.1

Setting Receiver Height

When you make CDMA coverage predictions, you can define the height of the receiver. To define the height of the receiver: 1. Click the Data tab in the Explorer window. 2. Right-click on the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Receiver tab. 5. Enter a receiver Height. This value will be used when calculating a CDMA coverage predictions and during a point analysis.

802

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 6. Click OK.

8.5.7.2

Creating or Modifying Reception Equipment

In Atoll, reception equipment is used when you create a terminal. The graphs defined for each reception equipment entry are used for quality studies and for selecting 1xEV-DO Rev. A radio bearers. To create or modify reception equipment: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the CDMA Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select Reception Equipment from the context menu. The Reception Equipment table appears. "Standard" is the default reception equipment type for all terminals. 5. Double-click the reception equipment type you want to modify. The reception equipment types Properties dialogue appears. Note: You can create a new reception equipment type by entering a name in the row marked with the New Row icon ( 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 studies. 8. Click the 1xEV-DO Rev. A Bearer Selection (Downlink) tab. 9. Enter the Required CI (dB) 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 indicates the downlink transmission format. The Required C/I values are used in simulations and in the Service Area (Eb/Nt) Downlink coverage prediction to select the downlink 1xEV-DO Rev. A radio bearer and then to calculate the data rate provided on downlink. The Early Termination Probabilities are used in the Service Area (Eb/Nt) Downlink coverage prediction to calculate the average 1xEV-DO Rev. A throughput when HARQ (Hybrid Automatic Repeat Request) is used. 10. Click the 1xEV-DO Rev. A 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 ) and pressing ENTER.

The Required Ec/Nt values are used in simulations and in the Service Area (Eb/Nt) Uplink coverage prediction to select the uplink 1xEV-DO Rev. A radio bearer and then to calculate the data rate provided on uplink. The Early Termination Probabilities are used in the Service Area (Eb/Nt) Uplink coverage prediction to calculate the average 1xEV-DO Rev. A throughput when HARQ (Hybrid Automatic Repeat Request) is used. 12. Click OK to close the reception equipment types Properties dialogue.

8.5.8

Conditions for Entering the Active Set

The mobile active set is the list of the transmitters to which the mobile is connected. The active set may consist of one or more transmitters; depending on whether the service supports soft handoff and on the terminal active set size. Transmitters in the mobile active set must use a frequency band with which the terminal is compatible. It is, however, the quality of the pilot (EcI0) that finally determines whether or not a transmitter can belong to the active set. In order for a given transmitter to enter the mobile active set as best server, the quality of this transmitters pilot must be the highest one and it must exceed an upper threshold equal to the sum of the minimum Ec/I0 defined in the properties of the best serving cell and the Delta minimum Ec/I0 defined in the properties of the mobility type. The upper threshold is set for the carrier as defined in the cell properties and can also take into account the user mobility type if the Delta minimum Ec/I0 defined in the mobility type is different from 0. In order for a transmitter to enter the active set: It must use the same carrier as the best server transmitter. In Atoll, carriers are modelled using cells. For information on accessing cell properties, see "Creating or Modifying a Cell" on page 674. For a description of the properties of a cell, see "Cell Definition" on page 671. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

803

Atoll User Manual 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 801.

8.5.9

Modelling Shadowing
Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value with a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be greater and in 50% of the measured cases, the result will be worse. Atoll uses a model standard deviation with the defined cell edge coverage probability to model the effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. 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 CDMA projects, the standard deviation of the propagation model is used to calculate shadowing margins on signal levels. You can also calculate shadowing margins on EcI0 and EbNt values and the macro-diversity gain. For information on setting 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 121. Shadowing can be taken into consideration when Atoll calculates the signal level, EcI0, and EbNt for: A point analysis (see "Making a Point Analysis to Study the Profile" on page 688) A coverage prediction (see "Studying Signal Level Coverage" on page 689).

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 804.

8.5.9.1

Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class
To display the shadowing margins and macro-diversity gain per clutter class: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialogue appears (see Figure 8.420). 4. You can set the following parameters: Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macro-diversity 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.

804

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks 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 dialogue.

Figure 8.420: The Shadowing Margins and Gains dialogue

8.5.10

Creating PN Offset Domains and Groups for PN Offset Allocation

Atoll facilitates the management of available PN offsets during automatic allocation with the pilot PN sequence offset index increment (PILOT_INC) parameter. For example, if you set PILOT_INC to "4," all PN offsets from 4 to 508 with a separation interval of 4 can be allocated. If you need to restrict the range of PN offsets available further, you can create groups of PN offsets and domains, where each domain is a defined set of groups. Using PN offsets groups and domains is recommended for this purpose only. The procedure for managing PN offsets in a CDMA document consists of the following steps: 1. Creating a PN offset domain, as explained in this section. 2. Creating groups, each containing a range of PN offsets, and assigning them to a domain, as explained in this section. 3. Assigning a PN offset domain to a cell or cells. If there is no PN offset domain, Atoll will consider the PILOT_INC parameter only to determine the possible PN offsets when assigning PN offsets (e.g., If PILOT_INC is set to 4, all PN offsets from 4 to 508 with a separation interval of 4 can be allocated). To create a PN offset domain: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > PN Offsets > Domains. The Domains table appears. 4. In the row marked with the New Row icon ( ), enter a Name for the new domain.

5. Click in another cell of the table to create the new domain and add a new blank row to the table. 6. Double-click the domain to which you want to add a group. The domains Properties dialogue appears. 7. 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. Group: Enter a name for the new PN offset group. Min.: Enter the lowest available PN offset in this groups range. Max: Enter the highest available PN offset in this groups range. Step: Enter the separation interval between each PN offset. It must be the same as the PILOT_INC value. Excluded: Enter the PN offsets in this range that you do not want to use. Extra: Enter any additional PN offsets (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 PN offsets separated by either a comma, semi-colon, or a space. You can also enter a range of PN offsets separated by a hyphen. For example, entering, "1, 2, 3-5" means that the extra PN offsets are "1, 2, 3, 4, 5."

8. Click in another cell of the table to create the new group and add a new blank row to the table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

805

Atoll User Manual

8.5.11

Modelling Inter-Technology Interference

Analyses of CDMA networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a CDMA network. Atoll can take into account interference from coexisting networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modeled in Atoll: Interference received by mobiles on the downlink: Interference can be received by mobiles in a 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) may be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (CDMA, TDMA, OFDM). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-Technology IRFs" on page 807. Interference from external mobiles (also called uplink-to-downlink interference) may be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your CDMA 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 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 Inter-technology DL Noise Rise, see "Cell Definition" on page 671. 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 724.

Figure 8.421: Interference received by mobiles on the downlink 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) may 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) may be created by the use of same or nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possible to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the Inter-technology UL Noise Rise definable for each cell in the CDMA network. This noise rise is taken into account in uplink interference-based calculations in the simulation. However, this noise rise is not considered in predictions (AS Analysis and coverage predictions) and does not impact the calculation of the cell reuse factor. For more information on the Inter-technology UL Noise Rise, see "Cell Definition" on page 671.

Figure 8.422: Interference received by cells on the uplink

806

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 8: CDMA2000 Networks

8.5.11.1

Defining Inter-Technology IRFs

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 An IRF depends on: The interfering technology (TDMA, CDMA, and OFDM) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).

IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your CDMA document, i.e., when Atoll is in co-planning mode. For more information on how to switch to co-planning mode, see "Switching to Co-planning Mode" on page 782. To define the inter-technology IRFs in the victim network: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Inter-technology IRFs from the context menu. The Inter-technology Interference Reduction Factors table appears. 4. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: Technology: Select the technology used by the interfering network. Interferer Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfering network. This channel width must be consistent with that used in the linked document. Victim Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfered network. This channel width must be consistent with that used in the main document. Reduction Factors (dB): Click the cell corresponding to the Reduction Factors (dB) column and the current row in the table. The Reduction Factors (dB) dialogue appears. Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document.

Notes: Reduction values must be positive. Undefined reduction factors are assumed to be very high values. Click OK. The interference reduction factors are stored.

You can, if you wish, link more than one Atoll document with your main document following the procedure described in "Switching to Co-planning Mode" on page 782. If the linked documents model networks using different technologies, you can define the interference reduction factors in your main document for all these technologies, and Atollwill calculate interference from all the external base stations in all the linked documents.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

807

Atoll User Manual

808

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9
TD-SCDMA Networks

RF Planning & Optimisation Software

Atoll

Chapter 9: TD-SCDMA Networks

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 811. Creating the network of base stations is explained in "Planning and Optimising TD-SCDMA Base Stations" on page 812. Allocating neighbours and scrambling codes is also explained. 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 Network Capacity" on page 900, 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 "Verifying Network Capacity" on page 929. How to filter imported drive test data paths, and how to use the data in coverage predictions is also explained.

9.1

Designing a TD-SCDMA Network

Figure 9.423 depicts the process of planning and creating a TD-SCDMA network.

Figure 9.423: Planning a TD-SCDMA network - workflow The steps involved in planning a TD-SCDMA network are described below. The numbers refer to Figure 9.423. 1. Open an existing radio-planning document or create a new one ( 1

).

You can open an existing Atoll document by selecting File > Open. Creating a new Atoll document is explained in Chapter 2: Starting an Atoll Project.
2

2. Configure the network by adding network elements and changing parameters ( You can add and modify the following elements of base stations: "Creating or Modifying a Site" on page 819 "Creating or Modifying a Transmitter" on page 820 "Creating or Modifying a Cell" on page 820.

).

You can also add base stations using a base station template (see "Placing a New Base Station Using a Station Template" on page 820). 3. Carry out basic coverage predictions ( 3

"Making a Point Analysis to Study the Profile" on page 834 "Studying Signal Level Coverage" on page 835 and "Signal Level Coverage Predictions" on page 843
4

4. Allocate neighbours, automatically or individually (

).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

811

Atoll User Manual "Planning Frequencies" on page 879.

5

5. Before making more advanced coverage predictions, you need to define cell load conditions ( You can define cell load conditions in the following ways: -

).

You can generate realistic cell load conditions by creating a simulation based on a traffic map ( 5a and 5b ) (see "Studying Network Capacity" on page 900). You can define them manually either on the Cells tab of each transmitters Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 820) (
5c

).
6

6. Make TD-SCDMA-specific coverage predictions using the defined cell load conditions ( "Signal Quality Coverage Predictions" on page 858 "HSDPA Coverage Prediction" on page 877.
7

).

7. Allocate scrambling codes ( -

).

"Planning Scrambling Codes" on page 892.

9.2

Planning and Optimising TD-SCDMA Base Stations

As described in Chapter 2: Starting an Atoll Project, you can start an Atoll document from a template, with no base stations, or from a database with a set of base stations. As you work on your Atoll document, you will still need to create base stations and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any additional equipment, such as the TMA, feeder cables, etc. In a TD-SCDMA project, you must also add cells to each transmitter. A cell refers to the characteristics of a carrier on a transmitter. Atoll lets you create one site, transmitter, or cell at a time, or create several at once by creating a station template. Using a station template, you can create one base station or several 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 (received signal code power, or RSCP) or transmitter coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, and analysed. Atoll enables you to model network traffic by allowing you to create services, user terminals, user profiles, and traffic environments. These can be then used to make quality coverage predictions, such as effective service area, noise, or interference predictions, on the network. In this section, the following are explained: "Creating a TD-SCDMA Base Station" on page 812. "Creating a Group of Base Stations" on page 827. "Modifying Sites and Transmitters Directly on the Map" on page 828. "Display Tips for Base Stations" on page 828. "Creating a Dual-Band TD-SCDMA Network" on page 828. "Creating a Repeater" on page 828. "Creating a Remote Antenna" on page 831. "Setting the Working Area of an Atoll Document" on page 833. "Studying a Single Base Station" on page 834. "Studying Base Stations" on page 837. "Planning Frequencies" on page 879. "Planning Neighbours" on page 882. "Planning Scrambling Codes" on page 892.

9.2.1

Creating a TD-SCDMA Base Station

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

812

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

9.2.1.1

Definition of a Base Station

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

9.2.1.1.1

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

Figure 9.424: New Site dialogue Name: Atoll automatically enters a default name for each new site. You can modify the 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.

Tip:

While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.

Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can specify the actual altitude under Real, if you want. If an altitude is specified here, Atoll will use this value for calculations. Comments: You can enter comments in this field if you want.

The Equipment tab: - Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equipment" on page 961. If no equipment is assigned to the site, Atoll considers that the JD factor and MCJD factor have a value of "0".

9.2.1.1.2

Transmitter Description
The parameters of a transmitter can be found in the transmitters Properties dialogue. When you create a transmitter, the Properties dialogue has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Properties dialogue has three additional tabs: the Cells tab (see "Cell Description" on page 816), the Propagation tab (see Chapter 5: Managing Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 32). The General tab: Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names transmitters, see the Administrator Manual. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site on which the transmitter will be located. For information on the site Properties dialogue, see "Site Description" on page 813. You can click the New button to create a new site on which the transmitter will be located.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

813

Atoll User Manual 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 dialogue, see "Defining Frequency Bands" on page 953. Under Antenna Position, you can modify the position of the antennas (main and secondary): Relative to Site: Select this option if you wish 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 wish to enter the coordinates of the antenna positions, and enter the x-axis and y-axis coordinates, X and Y, respectively.

The Transmitter tab (see Figure 9.425):

Figure 9.425: Transmitter dialogue - Transmitter tab Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder of the Data tab. Note: 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. Equipment can be assigned by using the Equipment Specifications dialogue which appears when you click the Equipment button. On the Equipment Specifications dialogue (see Figure 9.426), the equipment you select and the gains and losses you define are used to provide initial values for 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 147. 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 147. BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defining BTS Equipment" on page 148. Feeder Length: You can enter the feeder length at transmission and reception. Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value you enter must be positive. Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter must be positive.

814

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.426: The Equipment Specifications dialogue Note: 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 BTS Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total Losses at transmission and reception and the real BTS Noise Figure at reception if you want. Any value you enter must be positive.

Diversity: Under Diversity, you can select the type of diversity from the Transmission and Reception lists. 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. The other fields, Azimuth, Mechanical Downtilt, and Additional Electrical Downtilt, display additional antenna parameters. Antenna models that you have added to an antenna list in order to create Grids of Beams are excluded from the list of antennas available for the main antenna model. For more information on Grid of Beams modelling, see "Grid of Beams (GOB) Modelling" on page 955. 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 equip-

ment. When you click the Browse button ( ), the Smart Antenna Equipment Properties dialogue 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 dialogue. Under Patterns, clicking the Combined button opens a dialogue displaying the combined antenna patterns of all the smart antenna beams and the main antenna (see Figure 9.427). For more information on smart antenna equipment, see "Smart Antenna Equipment" on page 958. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

815

Atoll User Manual

Figure 9.427: Smart antenna and main antenna patterns 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. For information on working with data tables, see "Working with Data Tables" on page 53. 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.

Important: Transmitters using smart antenna equipment should not be assigned any secondary antennas, remote antennas, or repeaters.

9.2.1.1.3

Cell Description
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 TD-SCDMA multi-carrier network. In other words, a transmitter has one cell for every carrier. When you create a transmitter, Atoll reminds you to create at least one cell for the transmitter. The following describes the parameters of a TD-SCDMA cell, including the parameters for HSDPA functionality. As you create a cell, Atoll calculates appropriate values for some fields based on the information you have entered. You can, if you want, modify these values. The properties of a TD-SCDMA cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned. The Cells tab has the following options: 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 879. 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. Carrier Type: The type of carrier, i.e., Standalone, Master, or Slave. Active: If this cell is to be active, you must select the Active check box. Max Power [Traffic TS] (dBm): The maximum available power for each downlink traffic timeslot of the cell. For a transmitter using N-Frequency mode, only the master carrier transmits the P-CCPCH, DwPCH, and other CCH. The traffic power is shared between the master and its slave carriers. This means that the Max Power [Traffic TS] (dBm) can be greater than the P-CCPCH, DwPCH, and other CCH powers because it will be shared among the master and all its slave carriers. 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 over a period of 10 s , you should enter P/10 dBm in order to correctly represent the average interference from these channels.

816

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 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. DwPCH Power [DwPTS] (dBm): The power transmitted on the DwPTS timeslot. Note: 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 by right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Properties from the context menu. On the Global Parameters tab of the Properties dialogue, under DL Powers, you can select Relative to Pilot. The DwPCH power and the Other CCH power values are automatically converted and set as relative to the pilot power.

Max Difference Between 2 Transmit Powers (dB): The maximum difference between the powers transmitted by this cell on two DCH. This parameter is used during Monte Carlo simulations in order to avoid too much difference between users in the same cell. 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 automatic scrambling code allocation algorithm. SC Reuse Distance: The scrambling code reuse distance. This and the scrambling code domain are used by the scrambling code planning algorithm. Scrambling Code: The scrambling code allocated to the cell. 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 "Studying UpPCH Interference" on page 874. 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 "TD-SCDMA Network Capacity" on page 901. Comments: If desired, you can enter any comments in this field. HSDPA: The HSDPA check box is selected if the cell has HSDPA functionality. When the HSDPA check box is selected, the following fields are also available: HS-PDSCH Dynamic Power Allocation: If you are modelling dynamic power allocation, you should select the HS-PDSCH Dynamic Power Allocation check box and enter a value in Available HS-PDSCH Power per DL TS (dBm). The HS-PDSCH power calculated for any downlink timeslot during a simulation cannot exceed the value defined in Available HS-PDSCH Power per DL TS (dBm). 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. Note: 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 HSPDSCH Dynamic Power 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 HSPDSCH 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 the HS-SCCH Dynamic Power Allocation check box and enter a value in HS-SCCH Power (dBm). The HSSCCH power calculated for HS-SCCH channel during a simulation cannot exceed the value defined in HS-SCCH Power (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 (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 HSSCCH channel per HSDPA user. Number of HS-SCCH Channels: The maximum number of HS-SCCH channels for this cell. Each HSDPA 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 the HS-SICH Dynamic Power Allocation 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

817

Atoll User Manual Number of HS-SICH Channels: The maximum number of HS-SICH channels for this cell. Each HSDPA user consumes one HS-SICH channel. Therefore, at any given time (over a transmission time interval), the number of HSDPA users cannot exceed the number of HS-SICH channels per cell. 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 that this cell can support at any given time. HSDPA Scheduler Algorithm: The scheduling technique that will be used to rank the HSDPA users to be served: - Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by the channel quality indicator (CQI). - Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order). - Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order according to a random parameter which corresponds to a combination of the user rank in the simulation and the channel quality indicator (CQI). Note: 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 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 dialogue in which you can set both intra-technology and inter-technology neighbours by clicking the Browse button ( ). For information on defining neighbours, see "Planning Neighbours" on page 882. Timeslots: You can access information about the cells traffic timeslots, i.e, for each of the six traffic timeslots, by clicking the Browse button ( ) (see Figure 9.428).

Tip:

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.

The timeslot Properties dialogue has the following options: 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., only R99 users, only HSDPA users, or R99 and HSDPA users. 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 R99 or HSDPA users on the downlink timeslots. This value can be a simulation result or can be entered by the user. Max DL Load (% Pmax): The percentage of the maximum downlink power (set in Max Power [Traffic TS]) not to be exceeded. This limit will be taken into account during simulations 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. 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 available HS-PDSCH power for the timeslot is entered in this box. This is the power available for the HS-PDSCH channels of HSDPA users. If no value is defined here, the value defined in Available HS-PDSCH Power per DL TS for the cell is considered for the timeslot. In case of dynamic HS-PDSCH power allocation, the value entered here represents the maximum power for 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. 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. Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit can be taken into account during the simulation. 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.

818

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Resource Units Overhead: The number of resource units corresponding to overhead. You can enter the Resource Units Overhead, which is taken into consideration during network dimensioning. For information on calculating network capacity, see "TD-SCDMA Network Capacity" on page 901.

Figure 9.428: Timeslot properties dialogue MBMS: You can access a dialogue in which you can set MBMS channel powers, channel data rates, and the timeslots allocated to MBMS channels by clicking the Browse button ( ). This option is only available if the optional MBMS feature has been activated. Activating this optional feature requires data structure modifications (for more information, see the Administrator Manual). If an MBMS SCCPCH is not used, you should leave the field corresponding to its transmission power empty. The MBMS channel powers are used to calculate the optional MBMS service area Eb/Nt coverage prediction, and are taken into account in other calculations in the same way as the other common control channel power, i.e., for the calculation of interference.

Tip:

The Browse button ( ) might not be visible in the MBMS box if this is a new cell. You can make the Browse button appear by clicking Apply.

9.2.1.2

Creating or Modifying a Base Station Element

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: "Creating or Modifying a Site" on page 819. "Creating or Modifying a Transmitter" on page 820. "Creating or Modifying a Cell" on page 820.

9.2.1.2.1

Creating or Modifying a Site

You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 813, through the sites Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create or modify a site: 1. If you are creating a new site: a. Click the Data tab in the Explorer window. b. Right-click the Sites folder. The context menu appears. c. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 9.424 on page 813). 2. If you are modifying the properties of an existing site: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Sites folder.

c. Right-click the site you want to modify. The context menu appears. d. Select Properties from the context menu. The sites Properties dialogue appears. 3. Modify the parameters described in "Site Description" on page 813. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

819

Atoll User Manual 4. Click OK.

9.2.1.2.2

Creating or Modifying a Transmitter

You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 813, through the transmitters Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create or modify a transmitter: 1. If you are creating a new transmitter: a. Click the Data tab in the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 9.425). 2. If you are modifying the properties of an existing transmitter: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Transmitters folder.

c. Right-click the transmitter you want to modify. The context menu appears. d. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Modify the parameters described in "Transmitter Description" on page 813. 4. 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 820.

Tips: 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 right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. 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.2.1.2.3

Creating or Modifying a Cell

You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Description" on page 816, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Description" on page 816. 7. Click OK.

Tips: If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 59), or import data into the table (see "Importing Tables from Text Files" on page 63). If you want to add a cell to an existing transmitter on the map, you can add the cell by rightclicking the transmitter and selecting New Cell from the context menu.

9.2.1.3

Placing a New Base Station Using a Station Template

In Atoll, a base station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing base stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells.

820

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks To place a new station using a station template: 1. In the Radio toolbar, select a template from the list.

2. Click the New Transmitter or Station button (

) in the Radio toolbar.

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.

Tips:

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 38. 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.

You can also place a series of base stations using a station template. You do this by defining an area on the map where you want to place the base stations. Atoll calculates the placement of each base station according to the defined hexagonal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 822. To place a series of base stations within a defined area: 1. In the Radio toolbar, select a template from the list. 2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of base stations created from the same station template.

Note:

If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this template is not defined. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 822.

3. Draw a zone delimiting the area where you want to place the series of base stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as sites and transmitters are also created and placed into their respective folders. You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for example, another antenna to a transmitter.

Placing a Base Station on an Existing Site

When you place a new base station using a station template as explained in "Placing a New Base Station Using a Station Template" on page 820, the site is created at the same time as the base station. However, you can also place a new base station on an existing site. To place a base station on an existing site: 1. On the Data tab, clear the display check box beside the Hexagonal Design folder. 2. In the Radio toolbar, select a template from the list. 3. Click the New Station button ( ) in the Radio toolbar.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

821

Atoll User Manual 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.

9.2.1.4

Managing Station Templates

Atoll comes with TD-SCDMA station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio toolbar (see Figure 9.429).

Figure 9.429: The Radio toolbar In this section, the following are explained: "Creating or Modifying a Station Template" on page 822 "Copying Data from One Station Template to Another" on page 825 "Modifying a Field in a Station Template" on page 825 "Deleting a Station Template" on page 826.

9.2.1.4.1

Creating or Modifying a Station Template

When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. As well, you can modify the properties of any station template. To create or modify a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. You can now create a new station template or modify an existing one: To create a new station template: Under Station Templates, select the station template that most closely resembles the station template you want to create and click Add. The Properties dialogue appears. To modify an existing station template: Under Station Templates, select the station template whose properties you want to modify and click Properties. The Properties dialogue appears.

4. Click the General tab of the Properties dialogue. On this tab (see Figure 9.430), you can modify the following: Name: The name of the station template. Sectors: The number of Sectors, each with a transmitter, of the base station created using this station template. Hexagon Radius: The theoretical radius of the hexagonal area covered by each sector. Frequency Band: You can select a Frequency Band for the transmitters of the station template. Under Antennas: 1st Sector Azimuth: The azimuth angle of the first sector. If it is a multi-sector station template, the azimuth of the other sectors are offset to offer complete coverage of the area. Mechanical Downtilt: The angle at which the antenna is mechanically tilted downward. Additional Electrical Downtilt: The additional angle of downtilt introduced into the antenna electrically. Height: The Height 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. Antenna models that you have added to an antenna list in order to create Grids of Beams are excluded from the list of antennas available for the main antenna model. For more information on Grid of Beams modelling, see "Grid of Beams (GOB) Modelling" on page 955. Smart Antenna: Under Smart Antenna, the available smart antenna equipment are visible in the Equipment list.

Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

822

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.430: Station Template Properties dialogue General tab 5. Click the Transmitter tab. On this tab (see Figure 9.431), if the Active check box is selected, you can modify the following: Under TransmissionReception, you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station (BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 813. The information in the real Total Losses in transmission and reception boxes is calculated from the information you entered in the Equipment Specifications dialogue (see Figure 9.426 on page 815). 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. 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 BTS Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if you want. Any value you enter must be positive. Under Diversity, you can select the diversity from the Transmission and Reception lists.

Figure 9.431: Station Template Properties dialogue Transmitter tab 6. Click the TD-SCDMA tab. On this tab (see Figure 9.432), you modify the Carriers (each corresponding to a cell) that this base station supports. For information on carriers and cells, see "Cell Description" on page 816. You can select whether the transmitters created with this template are compatible with N-Frequency Mode or not. If you select the N-Frequency Mode check box, 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

823

Atoll User Manual P-CCPCH, DwPCH, or Other CCH powers. If you do not select the N-Frequency Mode check box, the transmitters created using this template will have stand-alone carriers. You can select the Carrier numbers for each sector of the station template. To select the carriers to be added to the sectors of a base station created using this station template: i. Click the Browse button ( ). The Carriers per Sector dialogue appears.

ii. In the Carriers per Sector dialogue, select the carriers to be created for each sector of the station. iii. Click OK. Under Scrambling Code, you can modify the Reuse Distance, and the scrambling code Domain. Under Power, you can modify the Max, P-CCPCH, DwPCH, and the Other CCH powers. Under Timeslots, you can select a default Timeslot Configuration for the cells and set the numbers of UL Required Resource Units and DL Required Resource Units. You can also select the default Equipment for the sites.

Figure 9.432: Station Template Properties dialogue TD-SCDMA tab 7. Click the HSDPA tab. On this tab (see Figure 9.433), if the HSDPA Supported check box is selected, you can modify the following (for more information on the fields, see "Cell Description" on page 816): Under HSDPA, You can define a Power Headroom. You can select either Static or Dynamic Allocation Strategy for HS-SICH power. You can define the Number of Channels for HS-SICH. You can select either Static or Dynamic Allocation Strategy for HS-PDSCH power. You can enter the Fixed Power, if you selected Static power allocation. You can enter the Min. and Max Number of Codes for HS-PDSCH. You can select either Static or Dynamic Allocation Strategy for HS-SCCH power. You can enter the HS-SCCH Power for HS-SCCH, if you selected Static power allocation. You can define the Number of Channels for HS-SCCH. You can select the scheduler Algorithm. You can enter the Max Number of Users. Under HS-SICH,

Under HS-PDSCH,

Under HS-SCCH,

Under Scheduler,

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.

824

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.433: Station Template Properties dialogue HSDPA tab 8. Click the Neighbours tab. On this tab (see Figure 9.434), you can enter the maximum numbers of neighbours for different types, i.e., IntraTechnology Neighbours and Inter-Technology Neighbours.

Figure 9.434: Station Template Properties dialogue Neighbours tab 9. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Sites table, or if you have defined an additional field in the Station Template Properties dialogue. 10. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.

9.2.1.4.2

Copying Data from One Station Template to Another

You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Station Templates from the context menu. The Station Templates table appears. 4. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy from and paste them into the row corresponding to the station template you want to modify.

9.2.1.4.3

Modifying a Field in a Station Template

To modify a field in a station template: 1. In the Radio toolbar, click the arrow to the right of the Station Template list. 2. Select Manage Templates from the Station Template list. The Station Template Properties dialogue appears. 3. Select the template in the Available Templates list. 4. Click the Fields button.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

825

Atoll User Manual 5. In the dialogue that appears, you have the following options: Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Types Data Table" on page 54) for it to appear as an option in the station template properties. To add a new field: i. Click the Add button. The Field Definition dialogue appears.

ii. Enter a Name for the new field. This is the name that will be used in database. iii. If desired, you can define a Group that this custom field will belong to. When you open an Atoll document from a database, you can then select a specific group of custom fields to be loaded from the database, instead of loading all custom fields. iv. In Legend, enter the name for the field that will appear in the Atoll document. v. For Type, you can select from Text, Short integer, Long integer, Single, Double, TrueFalse, DateTime, and Currency. If you choose text, you can also set the field Size (in characters), and create a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER after each one. vi. Enter, if desired, a Default value for the new field. vii. Click OK to close the Field Definition dialogue and save your changes. Delete: To delete a user-defined field: i. Select the user-defined field you want to delete.

ii. Click the Delete button. The user-defined field appears in strikethrough. It will be definitively deleted when you close the dialogue. Properties: To modify the properties of a user-defined field: i. Select the user-defined field you want to modify.

ii. Click the Properties button. The Field Definition dialogue appears. iii. Modify any of the properties as desired. iv. Click OK to close the Field Definition dialogue and save your changes. 6. Click OK.

9.2.1.4.4

Deleting a Station Template

To delete a station template: 1. In the Radio toolbar, click the arrow to the right of the Station Template list. 2. Select Manage Templates from the Station Template list. The Station Template Properties dialogue appears. 3. Under Station Templates, select the station template you want to delete and click Delete. The template is deleted. 4. Click OK.

9.2.1.5

Duplicating of an Existing Base Station

You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same site, transmitter, cell, and timeslot parameter values as the original base station. Duplicating a base station allows you to: 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.

To duplicate an existing base station: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Sites folder.

3. Right-click the site you want to duplicate. The context menu appears. 4. From the context menu, select one of the following: Select Duplicate > 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. 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.

You can now place the new base station on the map using the mouse. 5. In the map window, move the pointer over the map to where you would like to place the new base station. The exact coordinates of the pointers current location are visible in the Status bar.

826

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.435: Placing a new base station

Tips:

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 38. If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact coordinates, allowing you to verify that the location is correct.

6. Click to place the duplicate base station. A new base station is placed on the map. The site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original station, preceded by "Copy of." The site, transmitters, cells, and timeslots of the duplicate base station have the same settings as those of the original base station. All the remote antennas and repeaters belonging to any transmitter of the site are also duplicated. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate base station. For more information on the site, transmitter, cell, and timeslot properties, see "Definition of a Base Station" on page 813.

9.2.2

Creating a Group of Base Stations

You can create base stations individually as explained in "Creating a TD-SCDMA Base Station" on page 812, or you can create one or several base stations by using station templates as explained in "Placing a New Base Station Using a Station Template" on page 820. However, if you have a large data-planning project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations. Note: 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 96.

You can import base station data in the following ways: Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files" on page 61. For information on importing table data, see "Importing Tables from Text Files" on page 63. Note: You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio toolbar. For information, see "Placing a New Base Station Using a Station Template" on page 820.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

827

Atoll User Manual

9.2.3

Modifying Sites and Transmitters Directly on the Map

In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu on the Data tab of the Explorer window. However, in a complex radio-planning project, it can be difficult to find the data object in the Data tab, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. If there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: "Selecting One of Several Transmitters" on page 31 "Moving a Site Using the Mouse" on page 31 "Moving a Site to a Higher Location" on page 31 "Changing the Azimuth of the Antenna Using the Mouse" on page 31 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32.

9.2.4

Display Tips for Base Stations

Atoll allows to you to display information about base stations in a number of different ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object types data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information will lead to a cluttered display. For information on defining the label, see "Defining the Object Type Label" on page 35. Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip 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 every field in that object types data table, including from fields that you add. For information on defining the tooltips, see "Defining the Object Type Tip Text" on page 36. 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 "Defining the Display Type" on page 33. 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 "Defining the Display Type" on page 33.

9.2.5

Creating a Dual-Band TD-SCDMA Network

In Atoll, you can model a dual-band TD-SCDMA network, i.e., a network consisting of 2100 MHz and 900 MHz transmitters, in one document. Creating a dual-band TD-SCDMA network consists of the following steps: 1. Defining the two frequency bands in the document (see "Defining Frequency Bands" on page 953). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Managing Calculations in Atoll). 3. Assigning a frequency band, with its propagation model, to each transmitter (see "Transmitter Description" on page 813).

9.2.6

Creating a Repeater
A repeater receives, amplifies, and re-transmits the radiated or conducted RF carrier both in downlink and uplink. It has a donor side and a server side. The donor side receives the signal from a donor transmitter, repeater, or remote antenna. This signal can be carried by different types of links such as radio link or microwave link. The server side re-transmits the received signal. Atoll models RF repeaters and microwave repeaters. The modelling focuses on: The additional coverage these systems provide to transmitters in the downlink. The UL total gain in service area coverage predictions (effective service area and UL EbNt or CI service area) and the noise rise generated at the donor transmitter by the repeater.

828

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Notes: It is advised not to assign repeaters to transmitters that have smart antenna equipment assigned to them. Broadband repeaters are not modelled. Atoll assumes that all carriers of 3G donor transmitters are amplified.

In this section, the following are explained: "Creating and Modifying Repeater Equipment" on page 829. "Placing a Repeater on the Map Using the Mouse" on page 829. "Creating Several Repeaters" on page 830. "Defining the Properties of a Repeater" on page 830. "Tips for Updating Repeater Parameters" on page 831.

9.2.6.1

Creating and Modifying Repeater Equipment

You can define repeater equipment to be assigned to each repeater in the network. To create or modify repeater equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Repeaters > Equipment from the context menu. The Repeater Equipment table appears. 4. To create repeater equipment, enter the following in the row marked with the New Row icon ( a. Enter a Name and Manufacturer for the new equipment. b. Enter a Noise Figure. The repeater causes a rise in noise at the donor transmitter, so the noise figure is used to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive value. c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain using the buttons to the right of the Amplification box ( dialogue. ) on the General tab of the repeater Properties ):

e. Enter the maximum power that the equipment can transmit on the downlink in the 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.

5. To modify repeater equipment, change the parameters in the row containing the repeater equipment you want to modify.

9.2.6.2

Placing a Repeater on the Map Using the Mouse

In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. For information on creating a remote antenna, see "Creating a Remote Antenna" on page 831. To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder of the Explorer windows Data tab, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Repeater from the menu. 4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tooltip and label display the same information as displayed for the donor. As well, its tooltip identifies the repeater and the donor. In the Explorer window, the repeater is found in the Transmitters folder of the Data tab under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 830. Note: You can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter, repeater, or remote antenna. ) on the Radio toolbar.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

829

Atoll User Manual

9.2.6.3

Creating Several Repeaters

In Atoll, the characteristics of each repeater are stored in the Repeaters table. You can create several repeaters at the same time by pasting the information into the Repeaters table: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document. Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

9.2.6.4

Defining the Properties of a Repeater

To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or from the Transmitters folder of the Explorer windows Data tab. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: You can change the Name of the repeater. By default, repeaters are named "RepeaterN" where "N" is a number assigned as the repeater is created. You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another repeater, or a remote antenna. Clicking the Browse button ( ) opens the Properties dialogue of the donor.

You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Properties dialogue of the site. You can enter a Position relative to site location, if the repeater is not located on the site itself. You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties dialogue of the equipment. You can change the Amplification gain. The amplification gain is used in the link budget to evaluate the repeater total gain.

4. Click the Donor Side tab. You can modify the following parameters: Under Donor-Repeater Link, select a Link Type. If you select Microwave Link, enter the Propagation Losses and continue with step 5. If you select Air Link, 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. Important: If you want to create a remote antenna, you must select Optical Fibre Link. If you selected Air Link under Donor-Repeater Link, enter the following information under Antenna: i. Select a Model from the list. You can click the Browse button ( antenna. ) to access the properties of the

ii. Enter the height off the ground of the antenna in the HeightGround box. This will be added to the altitude of the transmitter as given by the DTM. iii. Enter the Azimuth and the Mechanical Downtilt.

Note:

You can click the Calculate button ( ) to update azimuth and downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.

If you selected Air Link 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 ( the feeder. ) to access the properties of

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 Data tab of the Explorer window) are calculated. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

830

Chapter 9: TD-SCDMA Networks Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received from the repeater. The UL total gain value is considered in UL EbNt or CI service area coverage predictions. The DL total gain is applied to each power (P-CCPCH power, DwPCH power, etc.). It takes into account losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder losses). The UL total gain is applied to each terminal power. It takes into account losses between the donor transmitter and the repeater, donor part characteristics (donor antenna gain, transmission feeder losses), amplification gain and coverage part characteristics (coverage antenna gain and reception feeder losses). Under Antennas, you can modify the following parameters: i. Enter the height off the ground of the antenna in the HeightGround box. This will be added to the altitude of the site as given by the DTM.

ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and the Additional Electrical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater coverage side correspond to the characteristics of the donor. iii. 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. For information on working with data tables, see "Working with Data Tables" on page 53. Under Feeders, you can modify the following information: i. Select a Type of feeder from the list. You can click the Browse button ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at Reception. Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.

6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation parameters. On the Propagation tab, you can modify the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

9.2.6.5

Tips for Updating Repeater Parameters

Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: You can update the calculated 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. Note: You can prevent Atoll from updating the UL and DL total gains of selected repeaters by creating a custom field called "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 31) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32).

9.2.7

Creating a Remote Antenna

Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optic fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise. If desired, you can model a remote antenna with equipment or a remote antenna connected to a base station with antennas by creating a repeater. For information on creating a repeater, see "Creating a Repeater" on page 828.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

831

Atoll User Manual

Note:

You should not assign remote antennas to transmitters that have smart antenna equipment assigned to them.

In this section, the following are explained: "Placing a Remote Antenna on the Map Using the Mouse" on page 832. "Creating Several Remote Antennas" on page 832. "Defining the Properties of a Remote Antenna" on page 832. "Tips for Updating Remote Antenna Parameters" on page 833.

9.2.7.1

Placing a Remote Antenna on the Map Using the Mouse

In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the Transmitters folder of the Explorer windows Data tab, or directly on the map. Note: Ensure that the remote antennas donor transmitter does not have any antennas.

2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Remote Antenna from the menu.

) on the Radio toolbar.

4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tooltip and label display the same information as displayed for the donor transmitter. As well, its tooltip identifies the remote antenna and the donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 832. Note: You can see to which base station the remote antenna is connected by clicking it; Atoll displays a link to the donor transmitter.

9.2.7.2

Creating Several Remote Antennas

In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. You can create several remote antennas at the same time by pasting the information into the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document. Important: The table you copy data from must have the same column layout as the table you are pasting data into. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59.

9.2.7.3

Defining the Properties of a Remote Antenna

To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or from the Transmitters folder of the Explorer windows Data tab. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: You can change the Name of the remote antenna. By default, remote antennas are named "RemoteAntennaN" where "N" is a number assigned as the remote antenna is created. You can change the Donor transmitter by selecting it from the Donor list. Clicking the Browse button ( opens the Properties dialogue of the donor transmitter. )

You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the site. You can enter a Position relative to site location, if the remote antenna is not located on the site itself. Note: A remote antenna does not have equipment.

832

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 4. Click the Donor Side tab. You can modify the following parameters: Under Donor-Repeater Link, select Optical Fibre Link and enter the Cable 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 Data tab of the Explorer window) are calculated. Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If you have modified any parameter on the General, Donor Side, or Coverage Side tabs, click Apply before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received from the remote antenna. The UL total gain value is considered in UL EbNt or CI service area coverage predictions. The DL total gain is applied to each power (P-CCPCH power, DwPCH power, etc.). It takes into account losses between the donor transmitter and the remote antenna. The UL total gain is applied to each terminal power. It takes into account losses between the donor transmitter and the remote antenna. Under Antennas, you can modify the following parameters: i. Enter the height of the antenna off the ground in the HeightGround box. This will be added to the altitude of the transmitter as given by the DTM.

ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and the Additional Electrical Downtilt. iii. 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. For information on working with data tables, see "Working with Data Tables" on page 53. Under Feeders, you can modify the following information: i. Select a Type of feeder from the list. You can click the Browse button ( the feeder. ) to access the properties of

ii. Enter the Length of the feeder cable at Transmission and at 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 Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

9.2.7.4

Tips for Updating Remote Antenna Parameters

Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: You can update the UL and DL total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from the Transmitters context menu. Note: You can prevent Atoll from updating the UL and DL total gains of selected remote antennas by creating a custom field called "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 31) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32).

9.2.8

Setting the Working Area of an Atoll Document

When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the sites that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of sites covered by a coverage prediction, each with its own advantages: Filtering the desired sites You can simplify the selection of sites to be studied by using a filter. You can filter sites according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters,

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

833

Atoll User Manual see "Filtering Data Using a Filtering Zone" on page 84. Filtering enables you to keep only the base stations with the characteristics you want to study. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 74. Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated coverage predictions in order to see the effects of small changes in site configuration, the savings in time are considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot zone. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo power control simulations, etc., while the focus zone or hot spot zone is the area taken into consideration when generating reports and results. For information on creating a computation zone, see "Creating a Computation Zone" on page 842. You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.

9.2.9

Studying a Single Base Station

As you create a base station, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of sites can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the base station you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of base stations once you have optimised the settings for each individual base station. Before studying a base station, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Atoll enables you to assign both a main propagation model, with a shorter radius and a higher resolution, and an extended propagation model, with a longer radius and a lower resolution. By using a calculation radius, Atoll limits the scope of calculations to a defined area. By using two matrices, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter, while reducing calculation time by using an extended matrix with a lower resolution. You can assign a propagation model to all transmitters at once, to a group of transmitters, or to a single transmitter. Assigning a propagation model is explained in "Assigning a Propagation Model" on page 840. In this section, the following are explained: "Making a Point Analysis to Study the Profile" on page 834. "Studying Signal Level Coverage" on page 835.

9.2.9.1

Making a Point Analysis to Study the Profile

In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a TD-SCDMA user. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 840. To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Profile tab. The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude (in metres) is reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional attenuations peaks. The total attenuation is displayed above the main peak.

834

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Details of the analysis are displayed at the top of the Profile tab: The received signal strength of the selected transmitter The propagation model used The shadowing margin and the cell edge coverage probability used for calculating it The distance between the transmitter and the receiver.

You can change the following options at the top of the Profile tab: Transmitter: Select the transmitter from the list. Carriers: Select the carrier to be analysed. If you are studying a transmitter compatible with the N-frequency mode, you can analyse its master carrier. Display Geo Data Only: Select the Display Geo Data Only check box if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate nor display signal levels and losses.

5. Right-click the Profile tab to choose one of the following commands from the context menu: Properties: Select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. You can: 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 "From Model" from the Shadowing Margin list. - Select Signal Level, Path loss, and Total losses from the Result Type list. - You can select the Indoor Coverage check box to add indoor losses. Link Budget: Select Link Budget to display a dialogue with the link budget. Model Details: Select Model Details to display a text document with details on the displayed profile analysis. Model details are only available for the standard propagation model. Displays data, including received signal, shadowing margin, cell edge coverage probability, propagation model used, and transmitter-receiver distance. -

You can select a different transmitter and choose to display a profile only with a selected carrier.

Fresnel ellipsoid

Line of sight Figure 9.436: Point Analysis Tool - Profile tab

Attenuation with diffraction.

9.2.9.2

Studying Signal Level Coverage

As you are building your radio-planning project, you may want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single site. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. Note: You can use the same procedure to study the signal level coverage of several sites by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 69.

To study the signal level coverage of a single base station: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder and select Group By > Site from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated.

Tip:

If you want to study only sites by their status, at this step you could group them by status.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

835

Atoll User Manual 3. Select the propagation parameters to be used in the coverage prediction: a. Click the Expand button ( ) to expand the Transmitters folder.

b. Right-click the group of transmitters you want to study. The context menu appears. c. Select Open Table from the context menu. A table appears with the properties of the selected group of transmitters. d. In the table, you can configure two propagation models: one for the main matrix, with a shorter radius and a higher resolution, and another for the extended matrix, with a longer radius and a lower resolution. By calculating two matrices you can reduce the time of calculation by using a lower resolution for the extended matrix and you can obtain more accurate results by using for the main and extended matrices propagation models best suited for each distance. e. In the Main Matrix column: f. Select a Propagation Model Enter a Radius and Resolution.

If desired, in the Extended Matrix column: Select a Propagation Model Enter a Radius and Resolution.

g. Close the table. 4. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. The Study Types dialogue lists the coverage predictions available. They are divided into Standard Studies, supplied with Atoll, and Customised Studies. Unless you have already created some customised coverage predictions, the Customised Studies list will be empty. 5. Select Coverage by P-CCPCH RSCP and click OK. The Coverage by P-CCPCH RSCP Properties dialogue appears. 6. You can configure the following parameters in the Properties dialogue: General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient:

Size of the Coverage Prediction

City Centre City County State Country

Display Resolution
5m 20 m 50 m 100 m According to the size of the country

Note:

If you create a new coverage prediction from the context menu of either the Transmitters or Predictions folder, you can select the sites using the Group By, Sort, and Filter buttons under Configuration. Because you already selected the target sites, however, only the Filter button is available.

Condition tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel (see Figure 9.437). 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 R99 or HSDPA 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 (PCCPCH 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 "All" to have all carriers taken into account. 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 "All," 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

836

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 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 RSCP 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.

Figure 9.437: Condition settings for a coverage prediction by P-CCPCH RSCP Display tab: You can modify how the results of the coverage prediction will be displayed. Note: Under Display Type, select "Value Intervals." Under Field, select "Best Signal Level." You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 32. You can create a tooltip 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 tooltip. 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 prediction to obtain valid results.

7. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The coverage prediction by P-CCPCH RSCP can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( Predictions folder. When you click the Calculate button ( ) beside the coverage prediction in the ). ), Atoll only calculates unlocked coverage predictions (

9.2.10

Studying Base Stations

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Figure 9.438 gives an example of a computation zone. In Figure 9.438, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

837

Atoll User Manual

Figure 9.438: An example of a computation zone Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main propagation model with a shorter radius (displayed with a blue square in Figure 9.438) and a higher resolution and an extended propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower resolution path loss matrices outside the area covered by the main propagation model. In this section, the following are explained: "Path Loss Matrices" on page 838. "Assigning a Propagation Model" on page 840. "The Calculation Process" on page 842. "Creating a Computation Zone" on page 842. "Setting Transmitters or Cells as Active" on page 842. "Signal Level Coverage Predictions" on page 843. "Analysing a Coverage Prediction" on page 851. "Signal Quality Coverage Predictions" on page 858. "HSDPA Coverage Prediction" on page 877. "Printing and Exporting Coverage Prediction Results" on page 879.

9.2.10.1

Path Loss Matrices

Path loss is caused by objects in the transmitter-receiver path and is calculated by the propagation model. In Atoll, the path loss matrices are needed for all base stations that are active, filtered and whose propagation zone intersects a rectangle containing the computation zone (for an explanation of the computation zone, see "Studying Signal Level Coverage" on page 835) and must be calculated before predictions and simulations can be made.

Storing Path Loss Matrices

Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a large amount 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. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: One file per transmitter with the extension LOS for its main path loss matrix. A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.

838

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks To set the storage location of the path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss matrices and the location for the shared path loss matrices: Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are loading path loss matrices from a shared location, where you store your changes to shared path loss matrices. Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally. Note: Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private Directory.

Caution:

When you save the path loss files externally, the external files are updated as soon as calculations are performed and not only when you save the Atoll document. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it, if you have updated the path loss matrices.

Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the common path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual.

5. Click OK.

Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the following display options: Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.

The Available Results table lists the following information for each displayed path loss matrix: Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: Whether or not the path loss matrix is valid. Origin of Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed.

5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 9.439) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

839

Atoll User Manual

Figure 9.439: Path loss matrices statistics

9.2.10.2

Assigning a Propagation Model

In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 841, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 841, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 840, this is the propagation model that will be used for all transmitters, except for those to which you have assigned a propagation model either individually or as part of a group. Important: 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. 3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 170, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following are explained: "Assigning a Propagation Model to All Transmitters" on page 840. "Assigning a Propagation Model to a Group of Transmitters" on page 841. "Assigning a Propagation Model to One Transmitter" on page 841.

For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.

Assigning a Propagation Model to All Transmitters

In Atoll, you can choose a propagation model for a single transmitter or globally for all transmitters. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

6. If desired, under Extended Matrix: Select a Propagation Model Enter a Radius and Resolution.

7. Click OK. The selected propagation models will be used for all transmitters.

840

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Note:

Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 841 will override this entry.

Assigning a Propagation Model to a Group of Transmitters

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

4. Click the Expand button (

) to expand the Transmitters folder.

5. Right-click the group of transmitters to which you want to assign a main and extended propagation model. The context menu appears. 6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected group. For each transmitter, you can set the propagation model parameters in the following columns: Main Propagation Model Main Calculation Radius (m) Main Resolution (m) Extended Propagation Model Extended Calculation Radius (m) Extended Resolution (m)

7. To enter the same values in one column for all transmitters in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

Assigning a Propagation Model to One Transmitter

If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

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

8. Click OK. The selected propagation models will be used for the selected transmitter.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

841

Atoll User Manual

9.2.10.3

The Calculation Process

When you create a coverage prediction and click the Calculate button ( ), Atoll follows the following process: 1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button ( ). ) beside the coverage 3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of the coverage predictions as soon as they are calculated, as indicated by the icon ( predictions in the Predictions folder. Notes: You can stop any calculations in progress by clicking the Stop Calculations button ( the toolbar. ) in

When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.

9.2.10.4

Creating a Computation Zone

To create a computation zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Computation Zone folder. The context menu appears. 4. Select Draw from the context menu. 5. Draw the computation zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. The computation zone is delimited by a red line. If you clear the computation zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a computation zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and selecting Use as > Computation Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation Zone folder on the Geo tab and selecting Fit to Map Window from the context menu. Note: You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: Saving the computation zone in the user configuration: For information on exporting the computation zone in the user configuration, see "Exporting a User Configuration" on page 79. Exporting the computation zone: You can export the computation zone by rightclicking the Focus Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

9.2.10.5

Setting Transmitters or Cells as Active

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Before you define a coverage prediction, you must ensure that all the transmitters on the sites you want to study have been activated. In the Explorer window, active transmitters are indicated with a red icon ( ) in the Transmitters folder and with the defined colour on the map and inactive transmitters are indicated with an empty icon ( )in the Transmitters folder and on the map.

842

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks In Atoll, you can also set individual cells on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zones context menu. To set an individual transmitter as active: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter you want to activate. The context menu appears. 4. Select Active Transmitter from the context menu. The transmitter is now active. To set more than one transmitter as active using the Transmitters context menu: 1. Click the Data tab of the Explorer window. 2. Select the transmitters you want to set as active: To set all transmitters as active, right-click the Transmitters folder. The context menu appears. To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and right-click the group of transmitters you want to set as active. The context menu appears.

3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one transmitter as active using the Transmitters table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitters parameters in a second row. 4. For each transmitter that you want to set as active, select the check box in the Active column. To set more than one cell as active using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cells parameters in a second row. 4. For each cell that you want to set as active, select the check box in the Active column. To set transmitters as active using a zone: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder.

3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. Note: If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 41.

4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll. Calculating path loss matrices can be time and resource intensive when you are working on large projects. Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the Atoll computing server application on other workstations or servers. Once the computing server application is installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on the network. For information on distributed calculations, see the Administrator Manual.

9.2.10.6

Signal Level Coverage Predictions

Atoll offers a series of coverage predictions that are based on the received signal code power (RSCP) level per pixel. The RSCP can be the P-CCPCH RSCP on TS0, the DwPCH RSCP on the DwPTS timeslot, or the UpPCH RSCP on the UpPTS timeslot. Coverage predictions based on interference and network load conditions are covered in "Signal Quality Coverage Predictions" on page 858, and "HSDPA Coverage Prediction" on page 877. 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 study which will appear in the Study Types dialogue. You can also select Duplicate from the coverage predictions context menu to create a copy. By duplicating an existing coverage prediction that has the parameters you want to study, you can create a new coverage prediction more quickly. 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 import 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 "Exporting a User Configuration" on page 79.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

843

Atoll User Manual The following standard coverage predictions are explained in this section: "Making a Coverage Prediction by P-CCPCH RSCP" on page 844. "Making a Coverage Prediction by P-CCPCH Best Server" on page 845. "Making a P-CCPCH Pollution Coverage Prediction" on page 846. "Making a Coverage Prediction by DwPCH RSCP" on page 848. "Making a Coverage Prediction by UpPCH RSCP" on page 849.

9.2.10.6.1

Making a Coverage Prediction by P-CCPCH RSCP

A coverage prediction by P-CCPCH RSCP allows you to predict the signal strength (received signal code power) of the pilot channel (TS0) using the main antenna of the transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by P-CCPCH RSCP: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by P-CCPCH RSCP and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.440). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set the following: Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The R99 or HSDPA 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 "All" to have all carriers taken into account. 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 "All," 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 RSCP 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.

Figure 9.440: Condition settings for a coverage prediction by P-CCPCH RSCP 7. Click the Display tab. For a coverage prediction by P-CCPCH RSCP, the Display Type "Value Intervals" based on the Field "Best Signal Level" is selected by default. The Field you choose determines which information the coverage prediction makes available. Each pixel is displayed in a colour corresponding to the P-CCPCH RSCP level. For information on defining display properties, see "Display Properties of Objects" on page 32. You can also set parameters to display the following results:

844

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 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.

8. Click OK to save your settings. 9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 9.441).

Figure 9.441: Coverage prediction by P-CCPCH RSCP

9.2.10.6.2

Making a Coverage Prediction by P-CCPCH Best Server

A P-CCPCH best server coverage prediction allows you to predict which transmitter has the highest P-CCPCH RSCP at each pixel. The coverage prediction is performed for TS0 using the main antenna of the transmitter. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by P-CCPCH best server: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by P-CCPCH Best Server and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.440). On the Condition tab, you can define the signals that will be considered for each pixel. On the Condition tab, 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 R99 or HSDPA 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 "All" to have all carriers taken into account. 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 "All," 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

845

Atoll User Manual You can select the Indoor Coverage check box to add indoor losses.

Figure 9.442: Condition settings for a coverage prediction by P-CCPCH best server 7. 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 "Display Properties of Objects" on page 32. 8. Click OK to save your settings. 9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 9.443).

Figure 9.443: Coverage prediction by P-CCPCH best server

9.2.10.6.3

Making a P-CCPCH Pollution Coverage Prediction

A P-CCPCH pollution coverage prediction calculates the pixels that are, for a defined condition, covered by the P-CCPCH signal of at least two transmitters. The coverage prediction considers the P-CCPCH RSCP (TS0) transmitted using the main antenna of the transmitters. To make a P-CCPCH pollution coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select P-CCPCH Pollution and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74.

846

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 6. Click the Condition tab (see Figure 9.444). On the Condition tab, you can define the signals that will be considered for each pixel. On the Condition tab, 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 R99 or HSDPA 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 "All" to have all carriers taken into account. 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 "All," 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 pollution 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. 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.

Figure 9.444: Condition settings for a P-CCPCH pollution coverage prediction 7. Click the Display tab. For a P-CCPCH pollution coverage prediction, the Display Type "Value Intervals" based on the Field "Number of Servers" is selected by default. Each pixel experiencing P-CCPCH pollution will then be displayed in a colour corresponding to the number of servers received per pixel. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Click OK to save your settings. 9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 9.445). Note: By changing the parameters selected on the Condition 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

847

Atoll User Manual

Figure 9.445: P-CCPCH pollution coverage prediction

9.2.10.6.4

Making a Coverage Prediction by DwPCH RSCP

A coverage prediction by DwPCH RSCP allows you to predict the signal strength of the DwPCH channel (DwPTS timeslot) using the main antenna of the transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by DwPCH RSCP: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by DwPCH RSCP and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.446). 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 R99 or HSDPA 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 "All" to have all carriers taken into account. 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 "All," 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. You can select the Indoor Coverage check box to add indoor losses.

848

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.446: Condition settings for a coverage prediction by DwPCH RSCP 7. Click the Display tab. For a coverage prediction by DwPCH RSCP, the Display Type "Value Intervals" based on the Field "DwPCH RSCP" is selected by default. The Field you choose determines which information the DwPCH prediction makes available. Each pixel is displayed in a colour corresponding to the DwPCH RSCP level. For information on defining display properties, see "Display Properties of Objects" on page 32. You can also set parameters to display the following results: 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.

8. Click OK to save your settings. 9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 9.447).

Figure 9.447: Coverage prediction by DwPCH RSCP

9.2.10.6.5

Making a Coverage Prediction by UpPCH RSCP

A coverage prediction by UpPCH RSCP allows you to predict the signal strength of the UpPCH channel (UpPTS timeslot) using the main antenna of the transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by UpPCH RSCP: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by UpPCH RSCP and click OK. The Coverage by UpPCH RSCP Properties dialogue appears. 5. Click the General tab.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

849

Atoll User Manual On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.448). 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 UpPCH power, gains, and losses defined in the terminal properties are used. Service: The R99 or HSDPA 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 "All" to have all carriers taken into account. 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 "All," 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.

Figure 9.448: Condition settings for a coverage prediction by UpPCH RSCP 7. Click the Display tab. For a coverage prediction by UpPCH RSCP, the Display Type "Value Intervals" based on the Field "UpPCH RSCP" is selected by default. The Field you choose determines which information the coverage prediction by UpPCH RSCP makes available. Each pixel is displayed in a colour corresponding to the UpPCH RSCP level. For information on defining display properties, see "Display Properties of Objects" on page 32. You can also set parameters to display the following results: 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.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 9.449).

850

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.449: Coverage prediction by UpPCH RSCP

9.2.10.7

Analysing a Coverage Prediction

Once you have completed a coverage prediction, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 835). If several coverage predictions are displayed on the map, it may be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which coverage predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following tools are explained: "Displaying the Legend Window" on page 851. "Displaying Coverage Prediction Results Using Tooltips" on page 851. "Using the Point Analysis Reception Tab" on page 852. "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 852. "Viewing Coverage Prediction Statistics" on page 854. "Comparing Coverage Predictions: Examples" on page 855.

9.2.10.7.1

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

9.2.10.7.2

Displaying Coverage Prediction Results Using Tooltips

You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltip. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 835). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined in the Display tab of the coverage prediction properties (see Figure 9.450).

Figure 9.450: Displaying coverage prediction results using tooltips

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

851

Atoll User Manual

9.2.10.7.3

Using the Point Analysis Reception Tab

Once you have calculated the coverage prediction, you can use the Point Analysis tool. 1. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 9.451). The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer location is displayed in the tooltip. At the top of the Reception tab, you can select the carrier to be analysed.

Figure 9.451: Point Analysis Window - Reception tab 3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue appears. 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 "From Model" from the Shadowing Margin list. Select the Indoor Coverage check box to add indoor losses.

9.2.10.7.4

Creating a Focus or Hot Spot Zone for a Coverage Prediction Report

The focus and hot spot zones define an area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spot zones in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the area where Atoll computes path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while the focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones. To define a focus zone or hot spot zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. Select Draw from the context menu. 5. Draw the focus or hot spot zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the focus or hot spot zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot zone by right-clicking it and selecting Use as > Focus Zone or Use as > New Hot Spot from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus

852

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot spot zones, you can import the name given to each zone as well. Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map Window from the context menu. Notes: You can save the focus zone or hot spot zones, so that you can use it in a different Atoll document, in the following ways: Saving the focus zone in the user configuration: For information on exporting the focus zone in the user configuration, see "Exporting a User Configuration" on page 79. - Exporting the focus zone or hot spot zones: You can export the focus zone or hot spot zones by right-clicking the Focus Zone or the Hot Spot Zones folder on the Data tab of the Explorer window and selecting Export from the context menu.. You can include population statistics in the focus or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113.

9.2.10.7.5

Displaying a Coverage Prediction Report

Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage predictions Properties dialogue. The coverage prediction report is displayed in a table. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 58. Atoll bases the report on the area covered by the focus zone and hot spot zones; if no focus zone is defined, Atoll will use the computation zone. Using a focus zone enables you to create a report without the border effect. In other words, the results of a coverage prediction are delimited by the computation zone; results close to the border are influenced by fact that no calculations have been made outside the computation zone. Basing a report on a focus zone that is smaller than the computation zone eliminates the border effect. By using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot zone must be defined before you display a report; it is not necessary to define it before computing coverage. The focus or hot spot zone does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 852. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. The Open dialogue appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the focus zone if available or on the hot spot zones and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. to move it up or

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

853

Atoll User Manual 4. 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. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. a appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. 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 spot zone: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. 2. Display the report as explained above. 3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears. 4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the population map: "Population" (Population): The number of inhabitants covered. "Population" (% Population): The percentage of inhabitants covered. "Population" (Population [total]): The total number of inhabitants inside the zone. to move it up or

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 (revenuekm, number of customerkm, etc.). Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable Versus Non Integrable Data" on page 129.

9.2.10.7.6

Viewing Coverage Prediction Statistics

Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage prediction colours, interval steps, and shading as defined in the Display tab of the coverage predictions Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spot zones are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before computing coverage. For information on defining a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 852. To display the statistics on a coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction whose statistics you want to display. The context menu appears. 4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined by the focus zone (see Figure 9.452).

854

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Under Histogram Based on Covered Areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Detailed Results section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics Based on Study Conditions, you can view the mean and standard deviation of the coverage criteria calculated during the coverage calculations, if available.

Figure 9.452: Histogram of a coverage prediction by signal level

9.2.10.7.7

Comparing Coverage Predictions: Examples

Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison coverage in one of the following ways: Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both coverage 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 coverage predictions are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).

To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. 6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage between them. In this section, the following examples are explained: "Example 1: Studying the Effect of a New Base Station" on page 855. "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 857.

Example 1: Studying the Effect of a New Base Station

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how you can verify if a newly added base station improves coverage. A coverage prediction by P-CCPCH RSCP for the current network is made as described in "Making a Coverage Prediction by P-CCPCH RSCP" on page 844. The results are displayed in Figure 9.453. An area with poor coverage is visible on the right side of the figure.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

855

Atoll User Manual

Figure 9.453: Coverage prediction by P-CCPCH RSCP for existing network A new base station is added, either by creating the site and adding the transmitters, as explained in "Creating a TDSCDMA Base Station" on page 812, or by using a station template, as explained in "Placing a New Base Station Using a Station Template" on page 820. Once the new base station has been added, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original coverage prediction by P-CCPCH RSCP 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 9.454).

Figure 9.454: 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 prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be displayed. You can choose among: Intersection Union Difference

In order to see what changes adding a new base station made, you should choose Difference. 5. Click OK to create the comparison. The comparison in Figure 9.455, shows clearly the area covered only by the new base station.

856

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.455: Comparison of both coverage predictions by P-CCPCH RSCP

Example 2: Studying the Effect of a Change in Transmitter Tilt

If you have an area in a network that is poorly covered by current transmitters, you have several options for improving coverage. In this example, we will look at how modifying transmitter tilt can improve coverage. A coverage prediction by P-CCPCH best server for the current network is made as described in "Making a Coverage Prediction by P-CCPCH Best Server" on page 845. The results are displayed in Figure 9.456. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated with a red oval in the figure.

Figure 9.456: Coverage prediction by P-CCPCH best server for the existing network You can try modifying the tilt on the transmitter to improve the coverage. You can access the properties of the transmitter by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue. Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original coverage prediction by can be copied by selecting Duplicate from its context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see Figure 9.457).

Figure 9.457: Coverage prediction by P-CCPCH best server of the network after modifications

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

857

Atoll User Manual 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 prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be displayed. You can choose among: Intersection Union Difference

In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The increase in coverage, seen in only the second coverage prediction, will be immediately clear. 5. Click OK to create the comparison. The comparison in Figure 9.458, shows clearly the increase in coverage due at the change in antenna tilt.

Figure 9.458: Comparison of both coverage predictions by P-CCPCH best server

9.2.10.8

Signal Quality Coverage Predictions

In TD-SCDMA, the quality of the signal and the size of the area that can be covered are influenced by the network load. As the network load increases, the area a cell can effectively cover decreases. For this reason, the network load must be defined in order to calculate signal quality coverage predictions. If you have traffic maps, you can do a Monte Carlo simulation to model power control and evaluate the network load for a generated user distribution. You can base a coverage prediction on simulation results by committing the results of a simulation to cell properties. If you do not have traffic maps, you can enter these values manually in the Cells and Cell Parameters per Timeslot tables. Atoll calculates the network load using the UL load factor and DL traffic power defined for each timeslot of each cell. In this section, the signal quality coverage predictions will be calculated using UL load factor and DL traffic power parameters defined at the timeslot level for each cell. For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined timeslot, service, mobility type, and terminal. Before making a prediction, you will have to set the UL load factor and DL traffic power and the parameters that define the services and users. These are explained in the following sections: "Setting the UL Load Factor and the DL Traffic Power" on page 859. "Service and User Modelling" on page 859.

Several different types of signal quality coverage predictions, based either on EbNt, CI, or traffic channel quality, are explained in this section. The following quality coverage predictions are explained: "Making a Pilot Signal Quality Prediction" on page 863. "Making a DwPCH Signal Quality Prediction" on page 864. "Studying Downlink and Uplink Traffic Channel Coverage" on page 865. "Studying Downlink and Uplink Service Areas" on page 867. "Studying Effective Service Area" on page 869. "Studying Service Area (EbNt) For MBMS" on page 871.

Making the following noise coverage prediction is explained: "Studying Downlink Total Noise" on page 872.

858

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks The following coverage predictions are available for determining and studying interference: To study the interference between cells in the case of asymmetric and different timeslot configurations used for different cells, see "Studying Cell to Cell Interference" on page 873. To study the interference on UpPCH when the UpPCH is shifted to a traffic timeslot, see "Studying UpPCH Interference" on page 874.

Making another type of coverage prediction, the baton handover coverage prediction, is also explained: "Making a Baton Handover Coverage Prediction" on page 876.

You can define the minimum RSCP threshold for your network in order to limit the calculation range and optimise the calculation time. For all the calculations, Atoll only considers the pixels where the P-CCPCH RSCP exceeds the minimum RSCP threshold. Defining the minimum RSCP threshold for the network is explained in the following section: "Defining the Minimum P-CCPCH RSCP Threshold" on page 862.

9.2.10.8.1

Setting the UL Load Factor and the DL Traffic Power

If you are setting the UL load factor and the DL traffic power for a single transmitter, you can set these parameters on the timeslot properties dialogue available from the Cells tab of the transmitters Properties dialogue. However, you can set the UL load factor and the DL traffic power for all the timeslots of all cells using the Cell Parameters per Timeslot table. To set the UL load factor and the DL traffic power using the Cell Parameters per Timeslot table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Timeslots Table from the context menu. The Cell Parameters per Timeslot table appears. 4. Enter the following values: 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 Description" on page 816.

9.2.10.8.2

Service and User Modelling

Before you model services, you must have R99 radio bearers defined in your Atoll document. The following R99 radio bearer parameters are used in predictions: Max TCH Power (dBm) Uplink and Downlink TCH RSCP Thresholds (dBm) per mobility Uplink and Downlink TCH Eb/Nt Thresholds (dB) or Uplink and Downlink TCH C/I Thresholds (dB) per mobility The type of bearer.

For more information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 960. In this section, the following are explained: "Modelling Services" on page 859. "Creating a Mobility Types" on page 860. "Modelling Terminals" on page 861.

Modelling Services
Services are the various services available to subscribers. These services can be either circuit-switched or packetswitched services. This section explains how to create a service. However, only the following parameters are used in predictions: R99 radio bearer parameters Body loss HSDPA application throughput parameters

Before you model services, you must have defined R99 radio bearers. For more information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 960. To create or modify a service: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. Note: You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.

5. You can edit the fields on the General tab to define the new service. Some fields depend on the Type of service you choose. You can change the following parameters:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

859

Atoll User Manual Name: Atoll proposes a name for the new service, but you can change the name to something more descriptive. R99 Radio Bearer: Select an R99 radio bearer from the list. If you want to edit the settings of the selected R99 radio bearer, click the Browse button ( ) to open the bearers Properties dialogue. Type: Select a service type. You can choose between Circuit (R99), Packet (R99) and Packet (HSDPA). For packet services that can use HSDPA channels, select Packet (HSDPA). You have the following options: A-DPCH Activity Factor: The uplink and downlink A-DPCH activity factors (for services that support HSDPA) are used to estimate the average power on A-DPCH channels. Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate is the average requested HS-PDSCH rate which guarantees a minimum average downlink rate during an HSDPA call. It is used twice in a simulation: once during user distribution generation in order to calculate the number of HSDPA users attempting a connection and then once during power control as a quality target to be compared to the real obtained average throughput. 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.

For packet services that can only use R99 channels, select Packet (R99). You have the following options: Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for each user during Monte-Carlo simulations. This parameter is used when working with sector traffic maps and user density traffic maps.

For circuit services, select Circuit (R99). You have the following options: Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for each user during Monte-Carlo simulations. - Preferred Carrier: You can select one of the available carriers or all carriers. The specified carrier is considered in simulations when connecting a mobile user to a transmitter. If the transmitter uses the preferred carrier of the service, Atoll selects it. Otherwise, it chooses another one, based on the DCA (Dynamic Channel Allocation) method selected when creating the simulation. If no preferred carrier is specified in the service properties, Atoll will consider the carrier selection mode of the selected DCA method. Similarly, coverage predictions that are calculated for "All" carriers are calculated for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll preforms the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters. Priority: Enter a priority for this service. "0" is the lowest priority. Body Loss: Enter the 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. -

6. If you selected Circuit (R99) as the Type in step 5., continue to step 7. If you selected either Packet (R99) or Packet (HSDPA) as the Type in step 5., an additional tab, the Packet tab, appears. Parameters available in the Packet tab are used to determine the probability of activity for each user during Monte-Carlo simulations. These parameters are used when working with user profile traffic maps only. Click the Packet tab. In the Packet tab, 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. Under Session, you can set: 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 (ms): Enter the average time between two packet calls in milliseconds in the uplink and downlink. Min. Size (Kbytes): Enter the minimum size of a packet call in kilobytes in the uplink and downlink. Max Size (Kbytes): Enter the maximum size of a packet call in kilobytes in the uplink and downlink. Average Time Between Two Packets (ms): Enter the average time between two packets in milliseconds in the uplink and downlink. Size (Bytes): Enter the packet size in bytes in the uplink and downlink.

Under Packet Calls, you can set: -

Under Packet, you can set: -

7. Click OK to save your changes and close the dialogue.

Creating a Mobility Types

Radio propagation conditions as well as connection properties and criteria vary with the speed the user is travelling. A mobile user travelling at a high speed and a pedestrian will not necessarily be connected to the same transmitters and both users will not experience the same service characteristics. EcI0 requirements and EbNt or C/I targets per radio bearer and per link (up and down) are largely dependent on mobile speed. The following parameters are used in predictions: P-CCPCH RSCP T_Add (RSCP P-CCPCH Threshold) P-CCPCH RSCP T_Drop

860

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks DwPCH RSCP Threshold UpPCH RSCP Threshold P-CCPCH EbNt Threshold or P-CCPCH CI Threshold DwPCH CI Threshold HS-SCCH EcNt Threshold (DL) HS-SICH EcNt Threshold (UL) Note: You can select whether the P-CCPCH thresholds you define are Eb/Nt or C/I thresholds by selecting the corresponding option in the Global Parameters tab of the Transmitters folders properties dialogue. For more information, see "The Global Transmitter Parameters" on page 953.

To create or modify a mobility type: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the Mobility Types folder. The context menu appears. 4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears. Note: You can modify the properties of an existing mobility type by right-clicking the mobility type in the Mobility Types folder and selecting Properties from the context menu.

5. On the General tab, you can enter or modify the following parameters in the Mobility Types New Element Properties dialogue: Name: Enter or modify the descriptive name for the mobility type. Average Speed: Enter or modify an average speed for the mobility type. This field is for information only; the average speed is not used in any calculation. Under Baton Handover Parameters, you can set the minimum required pilot signal levels from transmitters for entering and exiting the list of potential servers. - 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. 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. 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. 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. 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 Reception Analysis (EbNt) or P-CCPCH Reception Analysis (CI) 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 Reception Analysis (CI) coverage prediction.

6. On the MBMS tab, you can enter the Eb/Nt vs. Throughput graph in the Eb/Nt = f(Throughput) field. Clicking the Graph button opens a dialogue in which you can view and edit the Eb/Nt vs. Throughput graph. This tab is only available if the optional MBMS feature has been activated. Activating this feature requires data structure modifications (for more information, see the Administrator Manual). 7. Click OK.

Modelling 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. The following parameters are used in predictions: Reception equipment Number of carriers supported Maximum terminal power UpPCH power Gain and losses Noise figure JD factor Rho factor HSDPA capability, UE category, and HS-SICH power.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

861

Atoll User Manual To create or modify a terminal: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select New from the context menu. The Terminals New Element Properties dialogue appears. Note: You can modify the properties of an existing terminal by right-clicking the terminal in the Terminal folder and selecting Properties from the context menu.

5. On the General tab, you can modify the following parameters: Name: You can change the name of the terminal. Reception Equipment: Select a type of reception equipment from the list. For more information on reception equipment, see "Receiver Equipment" on page 962. No. of Carriers Supported: Select the number of carriers that the terminal can support. Under Power, you can set the minimum and maximum transmission power limits and the UpPCH power for the UpPTS timeslot. - Min. Power: Set the minimum transmission power. The minimum and maximum transmission powers make up the dynamic range for uplink power control. - Max Power: Set the maximum transmission power. - UpPCH Power: The transmission power for the UpPTS timeslot (or the TS1 uplink timeslot in case of UpPCH shifting). Under Interference, you can set the parameters that influence interference: - Noise Figure: Set the terminal noise figure. - JD Factor: Enter a joint detection (JD) factor. Joint detection is used to model interference cancellation at the user terminal. JD is modelled by a coefficient from 0 to 1; this factor is considered in calculating downlink interference. If JD is not supported, enter "0." - 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. Gain: Set the antenna gain. Losses: Set the reception losses. HSDPA Supported: Select the HSDPA Supported check box if the terminal is able to use HSDPA channels. For an HSDPA-capable terminal, you can set the following parameters: - UE Category: The HSDPA user equipment category. HSDPA user equipment capabilities are standardised into 15 different categories according to 3GPP specifications. For more information on HSDPA UE categories, see "Creating or Modifying HSDPA User Equipment Categories" on page 963. - 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 HS-SICH 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.

6. Click OK.

9.2.10.8.3

Defining the Minimum P-CCPCH RSCP Threshold

To define the minimum P-CCPCH RSCP threshold: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Predictions tab. 5. Under Calculation Limitation, enter a Min. Pilot RSCP Threshold. 6. Click OK.

9.2.10.8.4

Making Quality Coverage Predictions

In Atoll, you can make several predictions to study the quality. In this section, the following quality predictions are explained: "Making a Pilot Signal Quality Prediction" on page 863. "Making a DwPCH Signal Quality Prediction" on page 864. "Studying Downlink and Uplink Traffic Channel Coverage" on page 865. "Studying Downlink and Uplink Service Areas" on page 867. "Studying Effective Service Area" on page 869.

862

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Making a Pilot Signal Quality Prediction

A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is received sufficiently well. Atoll calculates the best pilot quality received on each pixel. Then, depending on the prediction definition, it compares this value either to the P-CCPCH EbNt or CI threshold defined for the selected mobility type. The pixel is coloured if the condition is fulfilled (in other words, if the received pilot quality is better than the P-CCPCH EbNt or CI threshold). The total noise, Nt, includes the pilot power (P-CCPCH power). The processing gain used for the EbNt coverage prediction is the one defined on the Global Parameters tab of the Transmitters Properties dialogue. For more information on the global parameters, see "The Global Transmitter Parameters" on page 953. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make a pilot signal quality prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select P-CCPCH Reception Analysis (EbNt) or P-CCPCH Reception Analysis (CI) and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.459). 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 R99 or HSDPA 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 "All" to have all carriers taken into account. 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 "All," 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.

Figure 9.459: Condition settings for a P-CCPCH reception analysis (EbNt) coverage prediction 7. Click the Display tab. For a pilot signal quality prediction, the Display Type "Value Intervals" based on the Field "EbNt (dB)" or "CI (dB)" is selected by default. Each pixel is displayed in a colour corresponding to the pilot signal quality. For information on defining display properties, see "Display Properties of Objects" on page 32.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

863

Atoll User Manual 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.460).

Figure 9.460: P-CCPCH reception analysis (EbNt) coverage prediction

Making a DwPCH Signal Quality Prediction

Atoll calculates the best DwPCH signal quality received on each pixel. Then, depending on the prediction definition, it compares this value with the DwPCH CI threshold defined for the selected mobility type. The pixel is coloured if the condition is fulfilled (in other words, if the received DwPCH signal quality is better than the DwPCH CI threshold). The coverage prediction is limited by the DwPCH RSCP threshold of the selected mobility type. To make a DwPCH signal quality prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select DwPCH Reception Analysis (CI) and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.459). 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 R99 or HSDPA 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 "All" to have all carriers taken into account. 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 "All", 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.

864

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.461: Condition settings for a DwPCH reception analysis (CI) coverage prediction 7. Click the Display tab. For a DwPCH signal quality prediction, the Display Type "Value Intervals" based on the Field "CI (dB)" is selected by default. Each pixel is displayed in a colour corresponding to the DwPCH signal quality. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.460).

Figure 9.462: DwPCH reception analysis (CI) coverage prediction

Studying Downlink and Uplink Traffic Channel Coverage

Atoll calculates the received traffic channel power on the uplink or on the downlink taking into consideration the effect of any smart antenna equipment assigned to transmitters, and the smart antenna simulation results stored for the selected timeslot. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make an effective service area prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select one of the following coverage predictions and click OK: Coverage by Downlink TCH RSCP Coverage by Uplink TCH RSCP

The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

865

Atoll User Manual the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.463). 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. 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 "All" to have all carriers taken into account. 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 "All," 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.

Figure 9.463: Condition settings for a downlink RSCP TCH coverage prediction 7. Click the Display tab. For a downlink or uplink traffic channel coverage area prediction, the Display Type "Value Intervals" based on the Field "DL TCH RSCP" or "UL TCH RSCP" is selected by default. The Field you choose determines which information the TCH prediction makes available. Each pixel is displayed in a colour corresponding to the DL or UL TCH RSCP level. For information on defining display properties, see "Display Properties of Objects" on page 32. You can also set parameters to display the following results: 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.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.464 and Figure 9.465).

866

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.464: Coverage prediction by downlink TCH RSCP

Figure 9.465: Coverage prediction by uplink TCH RSCP

Studying Downlink and Uplink Service Areas

Atoll calculates the traffic channel quality, as defined by EbNt or CI, on the uplink or on the downlink considering the effect of any smart antenna equipment assigned to transmitters, and the smart antenna simulation results stored for the selected timeslot. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make a prediction on downlink or uplink service area (EbNt or CI): 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select one of the following coverage predictions and click OK: Service Area (EbNt) Downlink Service Area (CI) Downlink Service Area (EbNt) Uplink Service Area (CI) Uplink

The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.466). 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. For the uplink service area coverage prediction, Atoll calculates the EbNt or CI using the maximum power defined for the selected terminal.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

867

Atoll User Manual 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 "All" to have all carriers taken into account. 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 "All," 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.

Figure 9.466: Condition settings for a downlink service area (EbNt) coverage prediction 7. Click the Display tab. For a service area prediction, the Display Type "Value Intervals" based on the Field "Max EbNt (dB)" or "Max CI (dB)" is selected by default. The Field you choose determines which information the service area downlink or uplink coverage prediction makes available. Each pixel is displayed in a colour corresponding to traffic channel quality. For information on defining display properties, see "Display Properties of Objects" on page 32. You can also set parameters to display the following results: 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 Condition tab, select "All" as the Mobility Type. The parameters on the Display tab are automatically set.

8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.467 and Figure 9.468).

868

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.467: Downlink service area (EbNt) coverage prediction

Figure 9.468: Uplink service area (EbNt) coverage prediction

Studying Effective Service Area

The aim of this coverage prediction is to identify the areas where there might be coverage problems for a service either on the downlink or on the uplink. Atoll calculates the traffic channel quality, as defined by EbNt or CI, on the uplink and on the downlink taken into consideration the effect of any smart antenna equipment assigned to transmitters, and the smart antenna simulation results stored for the selected timeslot. The effective service area is the intersection zone between the uplink and downlink service areas. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make an effective service area prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Effective Service Area (EbNt) or Effective Service Area (CI) and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.469). 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. 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

869

Atoll User Manual 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 "All" to have all carriers taken into account. 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 "All," 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.

Figure 9.469: Condition settings for an effective service area (EbNt) coverage prediction 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.470).

870

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.470: Effective service area (EbNt) coverage prediction

Studying Service Area (EbNt) For MBMS

This coverage prediction is only available if the optional MBMS feature has been activated. Activating this feature requires data structure modifications (for more information, see the Administrator Manual). MBMS, Multimedia Broadcast and Multicast Service, offers a solution for broadcasting television channels over SCCPCH channels in TD-SCDMA. SCCPCH (FACH) does not perform power control in order to cover the entire cell area. Atoll calculates the MBMS channel quality (as defined by EbNt) using the MBMS power defined for an MBMS SCCPCH channel and timelslot. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make a coverage prediction on MBMS service area (Eb/Nt) : 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Service Area (Eb/Nt) MBMS and click OK. The coverage prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab. 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 MBMS Eb/Nt coverage prediction is calculated for an MBMS service. Mobility: The mobility type to be considered in the coverage prediction. The EbNt vs. Throughput graph defined for the mobility is used in the coverage prediction. Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account. 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 "All," 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 MBMS service area coverage prediction can be performed for timeslots allocated to the MBMS SCCPCH channels. MBMS Channel: You must also select an MBMS Channel. 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.

7. Click the Display tab. For the MBMS service area (Eb/Nt) coverage prediction, the Display Type "Value Intervals" based on the Field "EbNt (dB)" is selected by default. Each pixel is displayed in a colour corresponding to the MBMS channel quality. For information on defining display properties, see "Display Properties of Objects" on page 32.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

871

Atoll User Manual 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

9.2.10.8.5

Studying Downlink Total Noise

This coverage prediction enables you to study the downlink total noise. In the downlink total noise prediction, Atoll calculates and displays the areas where the downlink total noise exceeds a set threshold. The downlink total noise is based on the cumulate effect of all downlink powers, including P-CCPCH. To make a downlink total noise prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Downlink Total Noise and click OK. The Downlink Total Noise Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.471). 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 R99 or HSDPA 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 "All" to have all carriers taken into account. 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 "All", 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.

Figure 9.471: Condition settings for a downlink total noise coverage prediction 7. Click the Display tab. Select "Value intervals" as the Display Type and one of the following options as Field: Min. Noise Level Average Noise Level Max Noise Level

For information on defining display properties, see "Display Properties of Objects" on page 32.

872

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.472).

Figure 9.472: Downlink total noise coverage prediction

9.2.10.8.6

Studying Interference
Coverage predictions are available that allow you to analyse the interference on different timeslots. The cell-to-cell interference prediction allows you to study the effect of different timeslot configurations allocated to different cells. Different timeslot configurations have different switching points between uplink and downlink parts of the subframe. Different switching points can cause interference between the two links, up and down. If all the cells have the same timeslot configuration assigned, there will be no inter-cell interference. Another coverage prediction is also available that allows you to study the interference on the UpPCH, if it is shifted to TS1 instead of being transmitted on the UpPTS. The following coverage predictions are explained in this section: "Studying Cell to Cell Interference" on page 873. "Studying UpPCH Interference" on page 874.

Studying Cell to Cell Interference

If different cells have different timeslot configurations assigned to them, the difference of switching point between the uplink and the downlink parts of the subframe may cause interference between the two links, up and down, i.e., on the same timeslot, a cell receiving data in the uplink is interfered by nearby cells transmitting in the downlink. The Cell to Cell Interference Zones coverage prediction displays the level of interference received by a cell. The coverage prediction sums the interfering signals in the downlink received by the victim cell in the uplink over the selected timeslot. Interference is calculated using the total transmitted power of the timeslot. To make a cell-to-cell interference zones coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Cell to Cell Interference Zones and click OK. The Cell to Cell Interference Zones Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.473). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set: Forsk 2010 Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The R99 or HSDPA 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. Unauthorized reproduction or distribution of this document is prohibited

873

Atoll User Manual Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account. 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 "All," 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 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.

Figure 9.473: Condition settings for a cell to cell interference zones coverage prediction Click the Display tab. For a cell-to-cell coverage prediction, the Display Type "Value Intervals" and the Field "Max Interference Level" are selected by default. For information on defining display properties, see "Display Properties of Objects" on page 32. 7. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window.

Studying UpPCH Interference

UpPCH is used for uplink synchronisation (SYNC_UL). This channel is usually carried by the UpPTS timeslot. However, if the interference on UpPTS is high, there is a risk of uplink synchronisation failure, i.e., the SYNC_UL might not be detected. Unsynchronised DwPTS or TS0 timeslots of other cells might cause interference on UpPTS. Lack of synchronisation between the DwPTS or TS0 and UpPTS occurs in wide and flat areas where there are no obstacles to wave propagation. For cells located in such areas, it is possible to shift the UpPCH channel from the UpPTS to any other uplink timeslot which might be less interfered. This is called UpPCH shifting. Without shifting, the UpPCH, or UpPTS, starts at the 96th chip after the DwPCH on DwPTS. The UpPCH can be shifted to TS1, TS2, or TS3. However, in Atoll, the UpPCH can only be shifted to TS1 on the uplink. It can be shifted by selecting the corresponding timeslot configuration at cell level. If some cells in a network use UpPCH shifting, you can use this coverage prediction to study the interference generated by traffic on other cells, in other words, the mobiles connected to the TS1 uplink timeslot of other cells, on the shifted UpPCH of these cells. Atoll calculates and displays the areas where the interference on the TS1 uplink timeslot, which is used for the UpPCH, exceeds a set threshold. To make an UpPCH interference zones prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select UpPCH Interference Zones and click OK. The UpPCH Interference Zones Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining

874

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.474). 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. Service: The R99 or HSDPA service to be considered in the coverage prediction. Mobility: The mobility type to be considered in the coverage prediction. The terminal, service, and mobility type are not used for the calculation of interference. The gains and losses defined for these parameters are used to calculate the P-CCPCH coverage of the cells that are using UpPCH shifting. Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account. 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 "All," 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 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.

Figure 9.474: Condition settings for an UpPCH interference zones coverage prediction 7. Click the Display tab. Select "Value intervals" as the Display Type and one of the following options from the Field list: Min. noise level Average noise level Max noise level

For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.475).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

875

Atoll User Manual

Figure 9.475: UpPCH interference zones coverage prediction

9.2.10.8.7

Making a Baton Handover Coverage Prediction

In the baton handover coverage prediction, Atoll calculates and displays the zones where a baton handover can be made. For a handover to be possible, there must be a potential serving transmitter, and the service chosen by the user must be available. The serving cell is first determined for each pixel. The serving cell is the one whose P-CCPCH RSCP at a pixel is above the P-CCPCH RSCP T_Add and is the highest among all the cells that satisfy the T_Add criterion. Then, all the cells whose P-CCPCH RSCP are higher than the P-CCPCH RSCP T_Drop are added to a preliminary handover set. Next, from among the cells listed in the preliminary handover set using the P-CCPCH RSCP T_Drop, only the cells 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. The number of potential neighbours per pixel displayed on the map is calculated from this set. The P-CCPCH RSCP T_Comp is set per cell. To make a baton handover coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Baton Handover Zones and click OK. The prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.476). 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 R99 or HSDPA 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. P-CCPCH RSCP T_Add, and PCCPCH 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 "All" to have all carriers taken into account. 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 "All," 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 baton handover 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.

876

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.476: Condition settings for a baton handover zones coverage prediction 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.477).

Figure 9.477: Baton handover zones coverage prediction

9.2.10.9

HSDPA Coverage Prediction

The HSDPA coverage prediction allows you to study HSDPA-related parameters. The parameters used as input for the HSDPA coverage prediction are the HSDPA power, and the total transmitted power for each timeslot. For information about the cell and timeslot parameters, see "Cell Description" on page 816. For information on the formulas used to calculate different throughputs, see the Technical Reference Guide. To make an HSDPA coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select HSDPA Coverage and click OK. The HSDPA Coverage Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

877

Atoll User Manual the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.478). 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 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 "All" to have all carriers taken into account. 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 "All," 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 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. 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.

Figure 9.478: Condition settings for an HSDPA coverage prediction 7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. If you have selected "All" timeslots in the Condition 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: Min. HS-PDSCH RSCP Average HS-PDSCH RSCP Max HS-PDSCH RSCP Min. HS-PDSCH EcNt Average HS-PDSCH EcNt Max HS-PDSCH EcNt

The HS-PDSCH EcNt relative to the EcNt threshold: Select one of the following in the Field list:

The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays the RLC peak rate that the selected HSDPA bearer can provide. The RLC peak rate is a characteristic of the HSDPA bearer. The MAC rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the MAC rate from the transport block size of the selected HSDPA bearer.

If you have selected a particular timeslot in the Condition tab, you can set the following parameters: The uplink and downlink A-DPCH qualities: 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.

878

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 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 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 Ec/Nt: Atoll determines the HS-SCCH Ec/Nt per pixel. The coverage is limited by the HSSCCH Ec/Nt threshold defined for the selected mobility type. 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 HS-SICH Ec/Nt better than the minimum required HS-SICH Ec/Nt. The coverage is limited by the HSSICH 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. 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.

The HS-SICH power, reception level, or quality: Select one of the following in the Field list: -

The HS-PDSCH reception level or quality: Select one of the following in the Field list: -

For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window.

9.2.10.10

Printing and Exporting Coverage Prediction Results

Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. 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 65. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 46. 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 49.

9.2.11

Planning Frequencies
TD-SCDMA networks can work in single-carrier as well as multi-carrier modes. In single-carrier mode, each transmitter has only one cell (carrier), which is considered a stand-alone carrier. In multi-carrier mode, each transmitter can have up to six carriers. In this case, a transmitter would have one master carrier and several slave carriers. The master carrier is used for P-CCPCH broadcast, scrambling code broadcast, and handover management, whereas the slave carriers are only used for carrying traffic. The multi-carrier mode is called N-Frequency Mode in Atoll. You can set the type of carrier for each cell of a transmitter manually, or you can let Atoll automatically allocate carrier types to cells on transmitters that support the N-frequency mode. Allocating frequencies to the cells of an N-frequency compatible transmitter means assigning a carrier type to each cell of that transmitter. A transmitter that is N-frequency mode compatible can have one master carrier and a number of slave carriers. Transmitters that are not N-frequency mode compatible have stand-alone carriers. 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 transmitters in the Explorer window. For information on creating a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 852. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 69. In this section, the following are explained: "Setting up N-Frequency Mode" on page 880. "Allocating Frequencies Automatically" on page 880. "Checking Automatic Allocation Results" on page 880. "Allocating Carrier Types per Transmitter" on page 881. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

879

Atoll User Manual "Checking the Consistency of the Frequency Allocation Plan" on page 881.

9.2.11.1

Setting up N-Frequency Mode

In Atoll, you can define whether transmitters are compatible with the N-frequency mode or not. To set up N-frequency mode: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table from the context menu. The Transmitters table appears. 4. In the Transmitters table, select the N-Frequency Mode check box for transmitters that are compatible with the N-frequency mode and will be taken into account in the automatic frequency allocation. For more information on transmitter properties, see "Transmitter Description" on page 813. 5. Click the Close button ( ) to close the table.

For more information on automatic frequency allocation, see "Allocating Frequencies Automatically" on page 880.

9.2.11.2

Allocating Frequencies Automatically

Atoll can automatically allocate master and slave carriers to N-frequency mode compatible transmitters in a TD-SCDMA network. Atoll allocates carriers to transmitters according to the distance between transmitters and their orientation (azimuths). Two automatic allocation features are available: one for the allocation of all the carriers in co-N-frequency and diff-N-frequency modes, and another for the allocation of master carriers. To automatically allocate all carriers: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > N-Frequency Mode > Automatic Allocation of All Carriers from the context menu. The Automatic Carrier Allocation dialogue appears. 4. Select the carrier allocation strategy: Co-N-Frequency Allocation: The same carriers are allocated to cells of N-frequency mode compatible cosite 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.

5. Click Run. Atoll allocates carriers to N-frequency mode compatible transmitters. Under Results, Atoll lists the transmitters to which it has allocated carriers in the Transmitters column, the carriers allocated to cells of each transmitter in the Carriers column, and the carrier number of the transmitters master carrier in the Master Carrier column. Carrier numbers available for allocation are read from the definition of the frequency band assigned to each Nfrequency mode compatible transmitter. Carrier numbers allocated to inactive cells are considered frozen, and are not used for allocation to active cells. The number of allocated carriers corresponds to the number of active cells in each N-frequency mode compatible transmitter. 6. Click Commit to apply the allocation to the transmitters listed in the Transmitters column. 7. Click Close to close the Automatic Carrier Allocation dialogue. To automatically allocate master carriers: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > N-Frequency Mode > Automatic Allocation of Master Carriers from the context menu. The Automatic Master Carrier Allocation dialogue appears. 4. Select the Delete Existing Allocation check box if you want Atoll to delete the existing master carrier allocation before allocating. 5. Click Run. Atoll allocates master carriers to N-frequency mode compatible transmitters. Under Results, Atoll lists the transmitters to which it has allocated master carriers in the Transmitters column and the carrier number of the transmitters master carrier in the Master Carrier column. 6. Click Commit to apply the allocation to the transmitters listed in the Transmitters column. 7. Click Close to close the Automatic Master Carrier Allocation dialogue.

9.2.11.3

Checking Automatic Allocation Results

You can verify the results of automatic frequency allocation in the following ways: "Displaying Frequency Allocation on the Map" on page 881. "Displaying the Coverage of the Master Carrier" on page 881. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

880

Chapter 9: TD-SCDMA Networks

9.2.11.3.1

Displaying Frequency Allocation on the Map

You can view the master carrier allocation directly on the map. Atoll can display the master carrier number for every Nfrequency compatible transmitter. To display the master carrier number on the map: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. 4. Click the Display tab. 5. Select "Discrete Values" as Display Type and "Cells: Carrier Type" as Field. 6. Select "Cells: Carrier Type" as Label. 7. Click OK. The transmitters are coloured according to the carrier type, and the master carrier number is displayed on the map with each transmitter.

9.2.11.3.2

Displaying the Coverage of the Master Carrier

By combining the display characteristics of a coverage prediction with the carrier type display options, Atoll can display the coverage areas of a transmitters master carrier. To display the coverage of the master carrier of a transmitter: 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 845.

9.2.11.4

Allocating Carrier Types per Transmitter

Although you can let Atoll allocate frequencies and carrier types automatically, you can adjust the overall allocation of carriers by allocating carrier types to transmitters using the Cells tab of the Transmitter Properties dialogue. To allocate TD-SCDMA carrier types using the Cells tab of the transmitters Properties dialogue: 1. On the map, right-click the transmitter whose carrier types you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Select the carrier type for each cell of the transmitter from the Carrier Type list. 5. Click OK.

9.2.11.5

Checking the Consistency of the Frequency Allocation Plan

You can perform an audit of the current frequency allocation plan. To perform an audit of the allocated frequency plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > N-Frequency Mode > Audit from the context menu. The N-Frequency Mode Audit dialogue appears. 4. The audit checks the following points: For Master 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. 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.

For Stand-alone Carriers: -

For Slave Carriers: -

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

881

Atoll User Manual 5. Click Run. 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.

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 dialogue.

9.2.12

Planning Neighbours
You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you set. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbours only to the cells within the computation zone. The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo tab in the Explorer window is selected. Usually, you will allocate neighbours globally during the beginning of a radio planning project. Afterwards, you will allocate neighbours to base stations or transmitters as you add them. You can use automatic allocation on all cells in the document, or you can define a group of cells either by using a focus zone or by grouping transmitters in the Explorer window. For information on creating a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 852. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 69. Atoll supports the following neighbour types in a TD-SCDMA network: Intra-technology Neighbours: Intra-technology neighbours are two TD-SCDMA cells defined as neighbours. Inter-technology Neighbours: Inter-technology neighbours are cells defined as neighbours that use a technology other than TD-SCDMA.

In this section, the following are explained: "Defining Exceptional Pairs" on page 882 "Configuring Importance Factors for Neighbours" on page 883 "Allocating Neighbours Automatically" on page 883 "Checking Automatic Allocation Results" on page 885 "Importing Neighbours" on page 887 "Allocating and Deleting Neighbours per Cell" on page 887 "Calculating the Importance of Existing Neighbours" on page 890 "Checking the Consistency of the Neighbour Plan" on page 891 "Exporting Neighbours" on page 892.

9.2.12.1

Defining Exceptional Pairs

In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs may be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Right-click the cell for which you want to define neighbour constraints. The context menu appears. 5. Select Properties from the context menu. The cells Properties dialogue appears. 6. Click the Intra-technology Neighbours tab. 7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( a. Select the cell from the list in the Neighbours column. b. In the Status column, select one of the following: Forced: The selected cell will always be a neighbour of the reference cell. ):

882

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Forbidden: The selected cell will never be a neighbour of the reference cell.

8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. Note: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table by right-clicking the Transmitters folder and selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.

9.2.12.2

Configuring Importance Factors for Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. Select the Intra-technology Neighbours tab. On the Intra-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: Set the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell. The Adjacency Factor will be used if you select the Force adjacent cells as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 883. Co-site Factor: Set the minimum and maximum importance of a possible neighbour cell being located on the same site as reference cell. The Co-site Factor will be used if you select the Force co-site cells as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 883.

5. Click OK.

9.2.12.3

Allocating Neighbours Automatically

Atoll can automatically allocate neighbours in a TD-SCDMA network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. For N-frequency mode compatible transmitters, neighbours are only stored for the master carriers. The slave carriers have the same neighbours as their master carrier. Neighbours are not allocated for standalone carriers (non-N-frequency mode compatible). To automatically allocate TD-SCDMA neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Neighbours tab. You can set the following parameters: Max Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour. Max No. of Neighbours: Set the maximum number of intra-technology neighbours that can be allocated to a cell. This value can be either set here for all cells, or specified for each cell in the Cells table. Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. P-CCPCH RSCP T_Add: Enter the P-CCPCH RSCP T_Add, which defines the minimum P-CCPCH RSCP required for the serving cell. If there is more than one cell whose P-CCPCH RSCP is higher than the P-CCPCH RSCP T_Add, the cell with the highest P-CCPCH RSCP is kept as the serving cell. P-CCPCH RSCP T_Drop: Enter the P-CCPCH RSCP T_Drop, which defines the minimum P-CCPCH RSCP required for cells to enter a preliminary handover set. All the cells whose P-CCPCH RSCP is higher than the P-CCPCH RSCP T_Drop are added to the set. P-CCPCH RSCP T_Comp: Enter the P-CCPCH RSCP T_Comp, which defines the handover set limit. From among the cells listed in the preliminary handover set using the P-CCPCH RSCP T_Drop, only the cells 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 desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

883

Atoll User Manual Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations. % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must overlap the reference cells coverage area. -

5. Select the desired calculation parameters: Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located on the same site as the reference cell to be automatically considered as neighbours. Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell is the best server. Force symmetry: Select the Force symmetry check box if you want neighbour relationships to be reciprocal. In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list of any cell is full, the reference cell will not be added as a neighbour and that possible neighbour cell will be removed from the list of neighbours of the reference cell. Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 882. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.

6. Click Calculate. Atoll begins the process of allocating neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance as calculated with the options selected in "Configuring Importance Factors for Neighbours" on page 883 Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the reference cell, as identified in the Cell column. Co-site Adjacency Symmetry Coverage Existing

Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell is best server or second best server.

7. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

8. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.

884

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Notes: A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint on the forbidden neighbour will be ignored because the neighbour already exists. When the options Force exceptional pairs and Force symmetry are selected, Atoll considers the constraints between exceptional pairs in both directions in order to respect symmetry. On the other hand, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event Viewer. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Exporting a User Configuration" on page 79.

Allocating Neighbours to a New Base Station

When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects the coverage area of the cells of the new base station. To allocate neighbours to a new base station: 1. On the Data tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects" on page 69. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 883.

Allocating Neighbours to a New Transmitter

When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter. To allocate neighbours to a new transmitter: 1. Click the Data tab of the Explorer window. 2. In the Transmitters folder, right-click the new transmitter. The context menu appears. 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 883.

9.2.12.4

Checking Automatic Allocation Results

You can verify the results of automatic neighbour allocation in the following ways: "Displaying Frequency Allocation on the Map" on page 881. "Displaying the Coverage of the Master Carrier" on page 881.

9.2.12.4.1

Displaying Neighbour Relations on the Map

You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

2. Select Display Options from the context menu. The Visual Management dialogue appears. 3. Under Intra-technology Neighbours, select the Display Links check box. 4. Click the Browse button ( ) beside the Display Links check box.

5. The Intra-technology Neighbour Display dialogue appears. 6. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours table, or according to the neighbour carrier. Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

885

Atoll User Manual their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

Tip:

You can display the number of handoff attempts for each cell-neighbour pair first creating a new field of Type "Integer" in the Intra-Technology Neighbours table for the number of handoff attempts. Once you have imported or entered the values in the new column, you can select this field from the Field list along with "Value Intervals" as the Display Type. For information on adding a new field to a table, see "Adding a Field to an Object Types Data Table" on page 54.

Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you can display or hide neighbour link display types individually. For information on changing display properties, see "Display Properties of Objects" on page 32. 7. Select the Add to Legend check box to add the displayed neighbour links to the legend. 8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each neighbour link. 9. Click OK to save your settings. 10. Under Advanced, select which neighbour links to display: Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations where the selected cell is the reference cell and where the neighbour relation is not symmetric. Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations where the selected cell is neighbour and where the neighbour relation is not symmetric. Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the selected cell and the neighbour.

11. Click OK to save your settings. 12. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 14. Click the Visual Management button ( ) in the Radio toolbar.

15. Click a transmitter on the map to display the neighbour relations. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). Atolldisplays the following information (see Figure 9.479) for the selected cell: The symmetric neighbour relations of the selected (reference) cell are indicated by a line. The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see Site1_2(0)) in Figure 9.479.). The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see Site9_3(0)) in Figure 9.479.).

In Figure 9.479, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is coloured as the reference transmitter as it is neighbour of Site9_3(0) here.

Figure 9.479: Neighbours of Site 22_3(0) - Display According to the Neighbour

886

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Note:

You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

9.2.12.4.2

Displaying the Coverage of Each Neighbour of a Cell

By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cells neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a coverage by P-CCPCH best server, with the Display Type set to "Discrete Values" and the Field set to Transmitter. For information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 845. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

3. Select Display Options from the context menu. The Neighbour Display dialogue appears. 4. Under Intra-technology Neighbours, select the Display Coverage Areas check box. 5. Click the Browse button ( ) beside the Display Coverage Areas check box.

6. The Intra-technology Neighbour Display dialogue appears. 7. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neighbours with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology Neighbours table. Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.

8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each coverage area. 9. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 11. Click the Visual Management button ( ) in the Radio toolbar.

12. Click a transmitter on the map to display the coverage of each neighbour. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). 13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( Radio toolbar. ) in the

9.2.12.5

Importing Neighbours
You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Data tab of the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 63.

9.2.12.6

Allocating and Deleting Neighbours per Cell

Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of the Transmitter Properties dialogue. This section explains the following: "Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 888. "Allocating or Deleting Neighbours Using the Neighbours Table" on page 888. "Allocating or Deleting Neighbours on the Map" on page 889.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

887

Atoll User Manual

Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete TD-SCDMA neighbours using the Cells tab of the transmitters Properties dialogue: 1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. On the Cells tab, there is a column for each cell. 4. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cells Properties dialogue appears. 5. Click the Intra-technology Neighbours tab. 6. If desired, you can enter the Max Number of Neighbours. 7. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table when you have finished creating the new exceptional pair. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." 8. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 9. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 10. To delete a neighbour: a. Click the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 11. Click OK.

Allocating or Deleting Neighbours Using the Neighbours Table

To allocate or delete TD-SCDMA neighbours using the Cells tab of the Transmitter Properties dialogue: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. 4. To allocate a neighbour: a. In the row marked with the new row icon ( ), select a reference cell in the Cell column.

b. Select the neighbour in the Neighbour column. c. Click another cell of the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." 5. To create a symmetric neighbour relation: a. Select the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 6. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu.

888

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 7. To take into consideration all exceptionnal pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either some forced neighbours or some forbidden neighbours using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu.

8. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 9. To delete several symmetric neighbour relations: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. 10. To delete a neighbour: a. Click the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour.

Allocating or Deleting Neighbours on the Map

You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 885. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters to the intra-technology neighbours list. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitters from the intra-technology neighbours. To add an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the intra-technology neighbour list of the reference transmitter. To remove an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the intra-technology neighbours list of the reference transmitter. To add an inward neighbour relation: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the intra-technology neighbours list of the reference transmitter.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

889

Atoll User Manual

Notes: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

9.2.12.7

Calculating the Importance of Existing Neighbours

After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Select the Neighbours tab. 5. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 883): Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference cells when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.

6. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. - P-CCPCH RSCP T_Add: Enter the P-CCPCH RSCP T_Add, which defines the minimum P-CCPCH RSCP required for the serving cell. If there is more than one cell whose P-CCPCH RSCP is higher than the P-CCPCH RSCP T_Add, the cell with the highest P-CCPCH RSCP is kept as the serving cell. - P-CCPCH RSCP T_Drop: Enter the P-CCPCH RSCP T_Drop, which defines the minimum P-CCPCH RSCP required for cells to enter a preliminary handover set. All the cells whose P-CCPCH RSCP is higher than the P-CCPCH RSCP T_Drop are added to the set. - P-CCPCH RSCP T_Comp: Enter the P-CCPCH RSCP T_Comp, which defines the handover set limit. From among the cells listed in the preliminary handover set using the P-CCPCH RSCP T_Drop, only the cells 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 desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage. -

7. Click OK to save your modifications and close the Coverage Conditions dialogue. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. 8. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table on each tab. The table contains the following information: Cell: The name of the reference cell. Neighbour: The neighbour of the reference cell. Importance (%): The importance as calculated with the options selected in "Configuring Importance Factors for Neighbours" on page 883 Cause: The reason Atoll has allocated value in the Importance column. Co-site Adjacency Symmetry Coverage

Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square kilometres.

890

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell is best server or second best server. Distance: The distance in kilometres between the reference cell and the neighbour.

The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

9.2.12.8

Checking the Consistency of the Neighbour Plan

You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Intra-technology Neighbours tab. 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list) and set the value in the Default Max Number text box. Lists > Max Number: Select the Lists > Max Number check box if you want to verify which cells have more than the maximum number of neighbours allowed and set the value in the Default Max Number text box. Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours > check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average number of neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: xX; x number of cells out of a total of X have no neighbours (or empty neighbours list). Syntax: |CELL|

Full Lists (default max number = Y): xX; x number of cells out of a total of X have Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > max number (default max number = Y): xX; x number of cells out of a total of X have more than Y number of neighbours listed in their respective neighbours lists. Syntax: Note: |CELL| |NUMBER| |MAX NUMBER|

If the field Maximum number of intra-technology neighbours in the Cells table is empty, the above two checks take into account the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non-symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

891

Atoll User Manual

9.2.12.9

Exporting Neighbours
The neighbour data for an Atoll document is stored in a series of tables. You can export the neighbours data to use it in another application or in another Atoll document. To export neighbour data: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours and then select the neighbour table containing the data you want to export from the context menu: Neighbours: This table contains the data for the intra-technology neighbours in the current Atoll document. Exceptional Pairs of Intra-technology Neighbours: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document.

4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files" on page 61.

9.2.13

Planning Scrambling Codes

In TD-SCDMA, 128 scrambling codes (or P-CCPCH midamble codes) of 16-bit lengths are available, numbered from 0 to 127. Although TD-SCDMA scrambling codes are displayed in decimal format by default, they can also be displayed and calculated in hexadecimal format, in other words using the numbers 0 to 9 and the letters A to F. Atoll facilitates the management of scrambling codes by letting you create groups of scrambling codes and domains, where each domain is a defined set of groups. You can also assign scrambling codes manually or automatically to any cell in the network. Once allocation is complete, you can audit the scrambling codes, view scrambling code reuse on the map, and analyse the distribution of scrambling codes. Downlink synchronisation, SYNC_DL, codes are assigned to cells in order to distinguish nearby cells, and for synchronization purposes. There are 32 different SYNC_DL codes of 64 bit lengths defined for the whole system in downlink. According to 3GPP specifications, the 127 possible scrambling codes can be broken down into 32 groups, each containing 4 codes. Because the term "group" in Atoll refers to user-defined sets of scrambling codes, these groups of 4 codes each are referred to as "clusters" in Atoll. Each cluster of scrambling codes is related to a SYNC_DL code used by a base station. For N-frequency mode compatible transmitters, scrambling codes are only allocated and stored for master carriers. The slave carriers have the same scrambling codes as their master carrier. The procedure of planning scrambling codes for a TD-SCDMA project is: Preparing for scrambling code allocation "Defining the Scrambling Code Format" on page 892. "Creating Scrambling Code Domains and Groups" on page 893. "Defining Exceptional Pairs for Scrambling Code Allocation" on page 893. "Defining Scrambling Code Relativity Clusters" on page 893. "Automatically Allocating Scrambling Codes to TD-SCDMA Cells" on page 894. "Allocating Scrambling Codes to TD-SCDMA Cells Manually" on page 896.

Allocating scrambling codes

"Checking the Consistency of the Scrambling Code Plan" on page 897. Displaying the allocation of scrambling codes "Using the Search Tool to Display Scrambling Code Allocation" on page 897. "Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 898. "Grouping Transmitters by Scrambling Code" on page 898. "Displaying the Scrambling Code Allocation Histogram" on page 899. "Studying Scrambling Code Interference" on page 899.

9.2.13.1

Defining the Scrambling Code Format

Scrambling codes may be displayed in decimal or hexadecimal format. The selected format is used to display scrambling codes in dialogues and tables such as in the Domains and Groups tables, the Cells table, and the Scrambling Code Allocation dialogue. The decimal format is the default format in Atoll. The accepted decimal values are from 0 to 127. The decimal format is also used, even if you have chosen the hexadecimal format, to store scrambling codes in the database and to display scrambling code distribution or the results of a scrambling code audit. The hexadecimal format uses the numbers 0 to 9 and the letters A to F for its base characters. In Atoll, hexadecimal values are indicated by a lower-case "h" following the value. For example, the hexadecimal value "3Fh" is "63" as a decimal value. You can convert a hexadecimal value to a decimal value with the following equation, where X, Y, and Z are decimal values within the hexadecimal index ranges: X 16 + Y 16 + Z
2

892

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks For example, the hexadecimal value "3Fh" would be calculated as shown below: 0 16 + 3 16 + 15 = 63 To define the scrambling code format for an Atoll document: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Scrambling Codes > Format from the context menu and select either Decimal or Hexadecimal.
2

9.2.13.2

Creating Scrambling Code Domains and Groups

Atoll facilitates the management of scrambling codes by letting you create domains, each containing groups of scrambling codes. The procedure for managing scrambling codes in a TD-SCDMA document consists of the following steps: 1. Creating a scrambling code domain, as explained in this section. 2. Creating groups, each containing a range of scrambling codes, and assigning them to a domain, as explained in this section. 3. Assigning a scrambling code domain to a cell or cells. If there is no scrambling code domain, Atoll will consider all 128 possible scrambling codes when assigning codes. To create a scrambling code domain: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Scrambling Codes > Domains. The Domains table appears. 4. In the row marked with the New Row icon ( ), enter a Name for the new domain.

5. Click another cell of the table to create the new domain and add a new blank row to the table. 6. Double-click the domain to which you want to add a group. The domains Properties dialogue appears. 7. Under Groups, enter the following information for each group you want to create. Name: Enter a name for the new scrambling code group. Min.: Enter the lowest available scrambling code in this groups range. The minimum and maximum scrambling codes must be entered in the format, decimal or hexadecimal, set for the Atoll document. For information on setting the scrambling code format, see "Defining the Scrambling Code Format" on page 892. Max: Enter the highest available scrambling code in this groups range. Step: Enter the separation interval between each scrambling code. 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".

8. Click another cell of the table to create the new group and add a new blank row to the table.

9.2.13.3

Defining Exceptional Pairs for Scrambling Code Allocation

You can also define pairs of cells which cannot have the same scrambling code. These pairs are referred to as exceptional pairs. Exceptional pairs are used along with other constraints, such as neighbours, reuse distance, and domains, in allocating scrambling codes. To create a pair of cells that cannot have the same scrambling code: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Scrambling Codes > Exceptional Pairs. The Exceptional Separation Constraints table appears. For information on working with data tables, see "Working with Data Tables" on page 53. 4. 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. 5. Click another cell of the table to create the new exceptional pair and add a new blank row to the table.

9.2.13.4

Defining Scrambling Code Relativity Clusters

All the scrambling codes are not fully mutually orthogonal. Some may have a relatively high correlation and may interfere each other. The principal aim of scrambling code planning is to allocate scrambling codes to cells in such a manner so as to avoid any confusion in the detection of these scrambling codes by the user equipment. In other words, geographically adjacent cells should be allocated highly orthogonal scrambling codes in order to avoid any error in scrambling code detection.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

893

Atoll User Manual Scrambling codes with relatively high correlation (less orthogonality) can be grouped into clusters, called Relativity Clusters. Nearby cells, or Close Neighbours, are then allocated scrambling codes from different relativity clusters in order to avoid interference between scrambling codes. Close neighbours are first order neighbours whose importance is higher than a certain value and are located within a certain distance from the studied cell. To define scrambling code relativity clusters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Scrambling Codes > Relativity Clusters. The Relativity Clusters table appears. 4. In the row marked with the New Row icon ( ), enter a Name for the new relativity cluster.

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.

9.2.13.5

Allocating Scrambling Codes

In an Atoll TD-SCDMA document, you allocate scrambling codes to cells by creating domains, with each domain containing one or more groups of scrambling codes. This combination of groups and domains defines which scrambling codes can be used by the cell. For information on scrambling code domains and groups, see "Creating Scrambling Code Domains and Groups" on page 893. You can also define pairs of cells which cannot have the same scrambling code. These pairs are referred to as exceptional pairs. For information on exceptional pairs, see "Defining Exceptional Pairs for Scrambling Code Allocation" on page 893. Atoll can automatically assign scrambling codes to the cells of a TD-SCDMA network according to set parameters. For example, it takes into account the definition of groups and domains of scrambling codes, the selected scrambling code allocation strategy (clustered, distributed per cell, distributed per site, and one SYNC_DL per site), minimum code reuse distance, and any constraints imposed by neighbours. In this section, the following methods of allocating scrambling codes are described: "Defining Automatic Allocation Constraint Violation Costs" on page 894 "Automatically Allocating Scrambling Codes to TD-SCDMA Cells" on page 894. "Allocating Scrambling Codes to TD-SCDMA Cells Manually" on page 896.

Defining Automatic Allocation Constraint Violation Costs

You can define the costs of the different types of constraints used in the automatic scrambling code allocation algorithm. To define the different constraint violation costs: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Scrambling Codes > Constraint Costs. The Constraint Violation Costs dialogue appears. In this dialogue you can define the following costs of constraint violations for the automatic allocation process (the cost is a value from 0 and 1): 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 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 879.

894

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Distributed per Site: This strategy allocates a group of adjacent clusters to each base station in the network, then, one cluster to each transmitter of the base station, according to its azimuth, and finally one code of the cluster to each cell of each transmitter. The number of adjacent clusters per group depends on the number of transmitters per base station you have in your network; this information is required to start allocation based on this strategy. When all the groups of adjacent clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the groups of adjacent clusters at another base station.

To automatically allocate scrambling codes: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Scrambling Codes > Automatic Allocation. The Scrambling Codes and SYNC_DL Codes dialogue appears. 4. Set the following parameters in the Scrambling Codes and SYNC_DL Codes dialogue: 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 "Planning Neighbours" on page 882. Note: 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 952. 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 dialogue 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 893. From the Strategy list, you can select an automatic allocation strategy: Clustered Distributed per Cell One SYNC_DL Code per Site Distributed per Site

Note:

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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

895

Atoll User Manual 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.

5. Click Run. Atoll begins the process of allocating scrambling codes. If you have selected the Distributed per Site allocation strategy, a Distributed per Site Allocation Parameters dialogue appears. a. In the Distributed per Site Allocation Parameters dialogue, enter the Max Number of Transmitters per Site. b. Select the Neighbours in Other SYNC_DL or Secondary Neighbours in Other SYNC_DL check boxes in the Additional Constraints section, if you want the automatic allocation to consider constraints related to first order and second order neighbours. c. Click OK. Once Atoll has finished allocating scrambling codes, the codes are visible under Results. Atoll only displays newly allocated scrambling codes. The Results table contains the following information. Site: The name of the base station. Cell: The name of the cell. Code: The scrambling code allocated to the cell. SYNC_DL: The SYNC_DL code allocated to the cell. Note: Atoll allocates the same scrambling code to each carrier of a transmitter.

6. Click Commit. The scrambling codes are stored in the cell properties. Note: 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 "Exporting a User Configuration" on page 79.

Tips:

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 Cells > Scrambling Codes > Automatic Allocation from the transmitter groups context menu.

Allocating Scrambling Codes to TD-SCDMA Cells Manually

When you allocate scrambling codes to a large number of cells, it is easiest to let Atoll allocate scrambling codes automatically, as described in "Automatically Allocating Scrambling Codes to TD-SCDMA Cells" on page 894. However, if you want to add a scrambling code to one cell or to modify the scrambling code of a cell, you can do it by accessing the properties of the cell. After allocation, you can use the audit tool to check the reuse scrambling code distances between cells and the compatibility of the domains of the cells for each base station. To allocate a scrambling code to a TD-SCDMA cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a scrambling code. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Select the Cells tab. 4. Enter a Scrambling Code in the cells column. 5. Click OK.

896

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

9.2.13.6

Checking the Consistency of the Scrambling Code Plan

Once you have completed allocating scrambling codes, you can verify whether the allocated scrambling codes respect the specified constraints by performing an audit of the plan. The scrambling code audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Scrambling Codes > Audit. The Code and SYNC_DL Audit dialogue appears. 4. In the Code and SYNC_DL Audit dialogue, select the allocation criteria that you want to check: 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 Neighbours: Atoll will check that no cell has the same scrambling code as any of its neighbours or any of the neighbours of its neighbours. Third Order Neighbours: Atoll will check that no cell has the same scrambling code as any of its neighbours or any of the neighbours of its neighbours or any of the neighbours of its second order neighbours. The report will list the cells and the neighbours that do not meet 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 dialogue. Cell pairs that do not respect the reuse distance condition are listed in increasing order of the distance between them. 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.

9.2.13.7

Displaying the Allocation of Scrambling Codes

Once you have completed allocating scrambling codes, you can verify several aspects of scrambling code allocation. You have several options for displaying scrambling codes: "Using the Search Tool to Display Scrambling Code Allocation" on page 897. "Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 898. "Grouping Transmitters by Scrambling Code" on page 898. "Displaying the Scrambling Code Allocation Histogram" on page 899. "Studying Scrambling Code Interference" on page 899.

Using the Search Tool to Display Scrambling Code Allocation

In Atoll, you can search for scrambling codes and scrambling code groups using the Search Tool. Results are displayed in the map window in red. If you have already calculated and displayed a coverage prediction by transmitter based on the best server P-CCPCH, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Scrambling codes and scrambling code groups and any potential problems will then be clearly visible. To find scrambling codes or scrambling code groups using the Search Tool: 1. Create, calculate, and display a coverage prediction by P-CCPCH best server. For information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 845. 2. Click View > Search Tool. The Search Tool window appears. 3. You can search either for a specific scrambling code or for a scrambling code group:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

897

Atoll User Manual To search for a scrambling code: a. Select Scrambling Code. b. Enter a scrambling code in the text box. To search for a scrambling code group: a. Select SC Group. b. Select a scrambling code group from the list. 4. Select the carrier you want to search on from the For the Carrier list, or select "(All)" to search for the scrambling code or scrambling code group in all carriers. 5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match the search criteria are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.

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. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. You can display the following information per transmitter: 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 tooltip: Scrambling code: Select "Cells: Scrambling Code" from the Label or Tip Text Field Definition dialogue. Scrambling code domain: Select "Cells: Scrambling Code Domain" from the Label or Tip Text Field Definition dialogue.

5. Click OK. For information on display options, see "Display Properties of Objects" on page 32.

Grouping Transmitters by Scrambling Code

You can group transmitters on the Data tab of the Explorer window by their scrambling code or scrambling code domain. To group transmitters by scrambling code: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: Scrambling Code Domain Scrambling Code

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. 8. 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 will be grouped. . The selected parameter is removed from the list of parameters on which the transmitters

9. 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 b. Select a parameter and click to move it up to the desired position. to move it down to the desired position.

10. Click OK to save your changes and close the Group dialogue.

898

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Note:

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. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Scrambling Codes > Code Distribution. The Distribution Histograms dialogue 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 Detailed Results list.

Studying Scrambling Code Interference

You can make a scrambling code interference zones coverage prediction to view areas covered by cells using the same scrambling code. The coverage prediction displays areas where transmitters other than the best server, whose received signal level is within the Pollution Margin set in the coverage prediction properties, interfere the best server signal. The interfered pixels are coloured according to the interfered scrambling code. To make a scrambling code interference zone coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Scrambling Code Interference Zones and click OK. The prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 9.480). 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 R99 or HSDPA 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: You can select the carrier to be studied, or select "All" to have all carriers taken into account. 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 "All," 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 scrambling code interference 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. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

899

Atoll User Manual

Figure 9.480: Condition settings for a scrambling code interference zones coverage prediction 7. Click the Display tab. For a coverage prediction on overlapping zones, 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 "Display Properties of Objects" on page 32. 8. Click OK to save your settings. 9. Click the Calculate button ( ) in the Radio toolbar to calculate the scrambling code interference zone coverage prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 9.481).

Figure 9.481: Condition settings for a scrambling code interference zones coverage prediction 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 Search Tool. For more information on using the Search Tool for scrambling code interference analysis, see "Using the Search Tool to Display Scrambling Code Allocation" on page 897.

9.3

Studying Network Capacity

A TD-SCDMA network automatically regulates power on both uplink and downlink with the objective of minimising interference and maximising network capacity. In the case of HSDPA, fast link adaptation (in other words, the selection of an HSDPA bearer) is performed in the downlink. Atoll can simulate these network regulation mechanisms, thereby enabling you to study the capacity of the TD-SCDMA network. In Atoll, a simulation is based on a realistic distribution of R99 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 required power of the mobile, the total DL power and the UL load per timeslot. Simulations are calculated in an iterative fashion. When several simulations are performed at a 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.

900

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 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: "TD-SCDMA Network Capacity" on page 901. "Defining Multi-service Traffic Data" on page 905. "Creating a Traffic Map" on page 905. "Calculating and Displaying Traffic Simulations" on page 914. "Making Coverage Predictions Using Simulation Results" on page 928.

9.3.1

TD-SCDMA Network Capacity

The capacity of a TD-SCDMA cell can be defined as the number of resource units available on the uplink and downlink. There can be a maximum of 16 users (16 OVSF codes) per timeslot. This means that each timeslot counts for 16 resource units. There are 6 timeslots in a TD-SCDMA subframe, which can be used in uplink or downlink. There are different combinations of uplink and downlink timeslots possible, which are referred to as timeslot configurations. Each cell can have a different timeslot configuration assigned to it, which gives the number of uplink and downlink timeslots. The following table lists the capacity of a cell for different possible timeslot configurations:

Timeslot Configuration
UDDDDD UUDDDD UUUDDD UUUUDD UUUUUD UpUDDDD UpUUDDD

Resource Units in Uplink

16 32 48 64 80 16 32

Resource Units in Downlink

80 64 48 32 16 64 48

Assuming ideal dynamic channel allocation (DCA), all the resource units within a subframe, i.e., 6 x 16 = 96, can be allocated and used. TS0 is not used for traffic. TS1 is not used for traffic either in case of UpPCH shifting. 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: "Calculating Available Network Capacity" on page 901. "Calculating Required Network Capacity" on page 902.

9.3.1.1

Calculating Available Network Capacity

You can calculate the available capacity of your TD-SCDMA network in Atoll using the Network Capacity Estimation dialogue. To calculate the available network capacity: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Calculations > Network Capacity from the context menu. The Network Capacity Estimation dialogue appears. The dialogue the numbers of uplink and downlink resource units in for each cell. The last row in this dialogue displays the total uplink and downlink resource units. The uplink and downlink Resource Units Overhead defined for each timeslot per cell is considered when calculating the number of available resource units. 4. Click Close to close the dialogue.

Displaying the Available Network Capacity on the Map

You can create a coverage prediction by P-CCPCH best server in order to display the available network capacity, i.e., the number of available resource units in uplink or downlink.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

901

Atoll User Manual To display the available cell and network capacity on the map: 1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best Server" on page 845, with the following display parameters: In step 7., set the Display Type "Value intervals" based on the Field "Available DL Resource Units" or "Available DL Resource Units" according to what you would like to display. Each coverage zone will then be displayed according to the number of available resource units for the carrier used for the coverage prediction.

Figure 9.482: Available network capacity coverage prediction (Display tab) Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.483).

Figure 9.483: Available network capacity coverage prediction

9.3.1.2

Calculating Required Network Capacity

You can calculate the number of required resource units according to a given traffic demand, compare it with the network capacity (see "Calculating Available Network Capacity" on page 901), and analyse how many resource units each cell requires using the Dimensioning dialogue. The dimensioning tool takes traffic data from the selected traffic maps as input before calculating the number of required resources. To calculate the required network capacity: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Calculations > Network Dimensioning from the context menu. The Dimensioning dialogue appears. On the Source Traffic tab, select: Global Scaling Factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of users (for environment and user profile traffic maps) or the rates per users (for live traffic maps per sector).

902

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 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 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 dialogue 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 dialogue. 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 (re)calculate a coverage by P-CCPCH best server, and run the dimensioning calculations based on the new coverage prediction.

Displaying the Required Network Capacity on the Map

You can create a coverage by P-CCPCH best server in order to display the required network capacity, i.e., the number of required resource units in uplink or downlink, of your TD-SCDMA network on the map. The number of required resource units is an output of network dimensioning stored in the Cells table. For more information, see "Calculating Required Network Capacity" on page 902. To display the required cell and network capacity on the map: 1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best Server" on page 845, with the following display parameters: In step 7., set the Display Type "Value intervals" based on the Field "Cells: Required DL Resource Units" or "Cells: Required UL Resource Units" according to what you would like to display. Each coverage zone will then be displayed according to the number of required resource units for the cell (carrier used for the coverage prediction).

Figure 9.484: Required network capacity coverage prediction (Display tab) Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.485).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

903

Atoll User Manual

Figure 9.485: Required network capacity coverage prediction

Displaying Usage of Resource Units on the Map

You can create a coverage by P-CCPCH best server in order to display the usage of resource units, i.e., the percentage of available resource units which are effectively used by the traffic in uplink or downlink, of your TD-SCDMA network on the map. To display the usage of resource units on the map: 1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best Server" on page 845, with the following display parameters: In step 7., set the Display Type "Value intervals" based on the Field "Required DL Resource Units (%)" or "Required UL Resource Units (%)" according to what you would like to display. Each coverage zone will then be displayed according to the percentage of available resource units that are used in each cell (carrier used for the coverage prediction).

Figure 9.486: Resource unit usage coverage prediction (Display tab) Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 9.487).

904

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.487: Resource unit usage coverage prediction A high percentage of cell usage can indicates dimensioning problems.

9.3.2

Defining Multi-service Traffic Data

The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment. The following services and users are modelled in Atoll in order to create simulations: R99 radio bearers: Bearer services are used by the network to carry 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 960. 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 services. For information on modelling end-user services, see "Modelling Services" on page 859. Mobility types: In TD-SCDMA, information about receiver mobility is important to accurately model the channel characteristics: a mobile used by a speed driver or 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 "Creating a Mobility Types" on page 860. 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 861.

9.3.3

Creating a Traffic Map

The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for TD-SCDMA projects. Sector traffic map User profile traffic map User density traffic map (number of users per km2)

These maps can be used for 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 . For more information, see "Creating a Sector Traffic Map" on page 906. User profile traffic maps can be used if you have marketing-based traffic data. User profile traffic maps, where each vector (polygon, line, or point) describes subscriber densities (or numbers of subscribers for points) with user profiles and mobility types, and user profile environment based traffic maps, where each pixel has an assigned environment class. For more information, see "Importing a User Profile Traffic Map" on page 909, "Importing a User Profile Environment Based Traffic Map" on page 910 and "Creating a User Profile Environment Based Traffic Map" on page 910. User density traffic maps (number of users per km2) can be used if you have population-based traffic data, or 2G network statistics.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

905

Atoll User Manual Each pixel has a user density assigned. For more information, see "Importing a User Density Traffic Map" on page 911, "Creating a User Density Traffic Map" on page 912, see "Converting 2G Network Traffic" on page 913 and "Exporting Cumulated Traffic" on page 913.

9.3.3.1

Creating a Sector Traffic Map

The section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands 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. A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 845. To create a sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector Traffic Map. 5. Select the type of traffic information you want to input. You can choose between Throughputs in Uplink and Downlink, Total Number of Users (All Activity Statuses) or Number of Users per Activity Status. 6. Click the Create button. The Sector Traffic Map dialogue appears. Note: 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 another Atoll document.

7. Select a coverage prediction by P-CCPCH best server from the list of available coverage predictions. 8. Enter the data required in the Map per Sector dialogue: If you selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and downlink for each sector and for each listed service. If you selected Total Number of Users (All Activity Statuses), enter the number of connected users for each sector and for each listed service. If you selected Number of Users per Activity Status, enter the number of inactive users, the number of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each service. Note: You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 63.

9. Click OK. The Sector Traffic Map Properties dialogue appears. 10. Select the Traffic tab. Enter the following: a. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. b. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. c. Under Clutter Distribution, for each clutter class, enter: A weight to spread the traffic over the vector. The percentage of indoor users. An additional loss will be counted for indoor users during Monte Carlo simulations.

11. 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 the sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 5. Select the Traffic tab. 6. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 7. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100.

906

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 8. Under Clutter Distribution, for each clutter class, enter a weight to spread the traffic over the clutter classes and the percentage of indoor users. 9. Click OK. Atoll saves the traffic map with its modifed values. You can update the information, throughput demands, and the number of users, on the map afterwards. You can update Live traffic per sector maps if you add or remove a base station. You must first recalculate the coverage prediction by PCCPCH best server. For more information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 845. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map that you want to update. The context menu appears. 4. Select Update from the context menu. The Sector Traffic Map dialogue appears. Select the updated coverage prediction by P-CCPCH best server 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. 5. Click OK. The Sector Traffic Map Properties dialogue appears. 6. Click OK. The traffic map is updated on the basis of the selected coverage prediction by P-CCPCH best server. 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 913.

9.3.3.2

Creating a User Profile Traffic Map

The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There can also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments. A user profile models the behaviour of different subscriber categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for circuit-switched calls) or uplink and downlink volume (for packet-switched calls). Environment classes are used to describe the distribution of subscribers on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km). The sections "Importing a User Profile Traffic Map" on page 909, "Importing a User Profile Environment Based Traffic Map" on page 910 and "Creating a User Profile Environment Based Traffic Map" on page 910 describe how to use traffic data from the marketing department in Atoll to model traffic. In this section, the following are explained: "Modelling User Profiles" on page 907. "Modelling Environments" on page 908.

Modelling User Profiles

You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user may be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. Note: 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.

5. You can modify the following parameters: Service: Select a service from the list. For information on services, see "Modelling Services" on page 859. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 861. CallsHour: For circuit-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 circuit-switched services, one call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

907

Atoll User Manual For packet-switched services, the CallsHour value is defined as the number of sessions per hour. A session is like a call in that it is defined as the period of time between when a user starts using a service and when he stops using a service. In packet-switched services, however, he may not use the service continually. For example, with a 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 may be downloading web pages and other times he may not be using the application or he may be browsing local files, but the session is still considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time. Note: In order for all the services defined for a user profile to be taken into account during traffic scenario elaboration, the sum of activity probabilities must be lower than 1.

Duration: For circuit-switched services, enter the average duration of a call in seconds. For packet-switched services, this field is left blank. UL Volume: For packet-switched services, enter the average uplink volume per session in kilobytes. DL Volume: For packet-switched services, enter the average downlink volume per session in kilobytes.

Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers for each clutter class. In a Monte Carlo simulation, an additional loss will be added to the indoor users path loss. To create or modify a TD-SCDMA environment: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the Environments folder. The context menu appears. 4. Select New from the context menu. The Environments New Element Properties dialogue appears. Note: You can modify the properties of an existing environment by right-clicking the environment in the Environments folder and selecting Properties from the context menu.

5. Click the General tab. 6. Enter a Name for the new TD-SCDMA environment. 7. In the row marked with the New Row icon ( ), set the following parameters for each user profilemobility combination that this TD-SCDMA environment will describe: User: Select a user profile. Mobility: Select a mobility type. Density (Subscriberskm2): Enter a density in terms of subscribers per square kilometre for the combination of user profile and mobility type.

8. Click the Clutter Weighting tab. 9. For each clutter class, enter a weight that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

For example: An area of 10 km with a subscriber density of 100km. Therefore, in this area, there are 1000 subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in the Building clutter class. 10. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss will be added to the indoor users path loss.

908

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

9.3.3.2.1

Importing a User Profile Traffic Map

User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscriberskm, or polygons with a number of subscriberskm) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Densities from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 910.

7. Select the file to import. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab (see Figure 9.488). Under Traffic Fields, you can specify the user profiles to be considered, their mobility type (kmh), and their density. If the file you are importing has this data, you can define the traffic characteristics by identifying the corresponding fields in the file. If the file you are importing does not have data describing the user profile, mobility, or density, you can assign values. When you assign values, they apply to the entire map.

Figure 9.488: Traffic map properties dialogue Traffic tab Define each of the following: User Profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the TD-SCDMA Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the TD-SCDMA Parameters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

909

Atoll User Manual

Important: The name of the imported user profile or mobility type must match the corresponding name in the TD-SCDMA Parameters folder of the Data tab. If the names do not match, Atoll will display a warning and will not import the file. 12. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

13. If you want, you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss will be added to the indoor users path loss. 14. Click OK to finish importing the traffic map.

9.3.3.2.2

Importing a User Profile Environment Based Traffic Map

Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 910.

7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, JPEG 2000, BIL, IST, BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Description tab. In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the Code column. 12. For each Code, select the environment it corresponds to from the Name column. The environments available are those available in the Environments folder, under TD-SCDMA Parameters on the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 908. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 32.

9.3.3.2.3

Creating a User Profile Environment Based Traffic Map

Atoll enables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 9.489).

910

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Draw Polygon Delete Polygon Figure 9.489: Environment Map Editor toolbar 7. Select the environment class from the list of available environment classes. 8. Click the Draw Polygon button ( 9. Click the Delete Polygon button ( ) to draw the polygon on the map for the selected environment class. ) and click the polygon to delete the environment class polygon on the map.

10. Click the Close button to close the Environment Map Editor toolbar and end editing.

9.3.3.2.4

Displaying Statistics on a User Profile Environment Traffic Map

You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears. The Statistics window lists the surface (Si in km) and the percentage of surface (% of i) for each environment Si class "i" within the focus zone. The percentage of surface is given by: % of i = ------------- 100 Sk

You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.

9.3.3.3

Creating User Density Traffic Maps (No. Users/km2)

User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. This can be either the density of users per activity status or the density of users including all activity statuses. In this section, the following ways of creating a user density traffic map are explained: "Importing a User Density Traffic Map" on page 911 "Creating a User Density Traffic Map" on page 912.

User density traffic maps may be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. for more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 913.

9.3.3.3.1

Importing a User Density Traffic Map

The user density traffic map defines the density of users per pixel. For a traffic density of X users per km, Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic maps properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (No. Users/km2). 5. Select the type of traffic information you input: All Activity Statuses: Select All Activity Statuses if the map you are importing provides a density of users with any activity status.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

911

Atoll User Manual Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.

6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 910.

7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP, PlaNET, TIF, JPEG 2000, ISTAR, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab. 12. Select whether the users are active in the UplinkDownlink, only in the Downlink, or only in the Uplink. 13. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. 14. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 15. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users. An additional loss will be counted for indoor users during the Monte Carlo simulations. You do not have to define a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel. 17. Click OK. Atoll creates the traffic map in the Traffic folder.

9.3.3.3.2

Creating a User Density Traffic Map

Atollenables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (Number of users per km2). 5. Select the type of traffic information you input. You can choose between: All Activity Statuses: Select All Activity Statuses if the map you are importing provides a density of users with any activity status. Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.

6. Click the Create button. The traffic maps property dialogue appears. 7. Select the Traffic tab. 8. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. 9. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 10. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 11. Under Clutter Distribution, enter for each clutter class the percentage of indoor users. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for user density traffic maps because the traffic is provided in terms of user density per pixel. 12. Click OK. Atoll creates the traffic map in the Traffic folder.

912

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 13. Right-click the traffic map. The context menu appears. 14. Select Edit from the context menu. 15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit contours, see "Editing Polygons, Lines, and Points" on page 46. Atoll creates an item called Density values in the User Density Map folder. 16. Right-click the item. The context menu appears. 17. Select Open Table from the context menu. 18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn. 19. Right-click the item. The context menu appears. 20. Select Edit from the context menu to end editing.

9.3.3.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. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map from which you want to create user density traffic maps. The context menu appears. 4. Select Create density maps from the context menu. Atoll creates as many user density traffic maps as the number of services present in the sector traffic map. The user density map files use the resolution of the coverage prediction used for the sector traffic map and are embedded in the document.

9.3.3.4

Converting 2G Network Traffic

Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as user density traffic maps into your TD-SCDMA document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 913, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 911. To import a 2G traffic map into a TD-SCDMA document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 254. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 913. 3. Import the traffic exported in step 2 to your TD-SCDMA document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 911.

9.3.3.5

Exporting Cumulated Traffic

Atoll allows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user density. The cumulated traffic is exported in 32-bit BIL, ArcView Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: The Entire Project Area: This option allows you to export the cumulated traffic of the entire project. The Computation Zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible.

7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

913

Atoll User Manual

Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains at "0" and no data will be exported. 8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic data to be exported. Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal. Service: Select the service that will be exported, or select "All circuit services" to export traffic using any circuit service, or select "All 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 All Activity Statuses to export all users without any filter by activity status. Uplink: Select Uplink to export mobiles active in the uplink only. Downlink: Select Downlink to export mobiles active in the downlink only. Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity. Inactive: Select Inactive to export only inactive mobiles.

9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the cumulated traffic. 10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.

9.3.4

Exporting a Traffic Map

To export a traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save. If you are exporting a raster traffic map, you have to define: The Export Region: Entire Project Area: Saves the entire traffic map. Only Pending Changes: Saves only the modifications made to the map. Computation Zone: Saves only the part of the traffic map inside the computation zone.

An export Resolution.

9.3.5

Calculating and Displaying Traffic Simulations

Once you have modelled the network services and users and have created traffic maps, you can create simulations. The simulation process consists of two steps: 1. Obtaining a realistic user distribution: Atoll generates a user distribution using a Monte Carlo algorithm; this user distribution is based on the traffic database and traffic maps and is weighted by a Poisson distribution between simulations of a same group. Each user is assigned a service, a mobility type, and an activity status by random trial, according to a probability law that uses the traffic database. The user activity status is an important output of the random trial and has direct consequences on the next step of the simulation and on the network interferences. A user may be either active or inactive. Both active and inactive users consume radio resources and create interference. Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the shadowing effect. Finally, another random trial determines user positions in their respective traffic zone (according to the clutter weighting and the indoor ratio per clutter class). 2. Modelling dynamic channel allocation and power control: 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 914.

9.3.5.1

The Monte Carlo Simulation Algorithm

The dynamic channel allocation (DCA) simulates the way a TD-SCDMA network allocates resource units to users accessing different services. The power control algorithm (see Figure 9.490) simulates the way a TD-SCDMA network regulates itself by using uplink and downlink power controls in order to minimize interference and maximize capacity. HSDPA users are linked to the A-DPCH radio bearer (an R99 radio bearer). Therefore, the network uses uplink and downlink power control on A-DPCH, and then performs fast link adaptation on downlink in order to select an HSDPA radio bearer. Atoll

914

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks simulates the network regulation mechanisms for each user distribution. During each iteration of the algorithm, all the mobiles (R99 and HSDPA) selected during the user distribution generation attempt to connect one by one to the networks transmitters. The process is repeated until the network is balanced, i.e., until the convergence criteria (on UL and DL) are satisfied.

Figure 9.490: Schematic view of simulation algorithm As shown in Figure 9.490, the simulation algorithm is divided in two parts. All users are evaluated by the R99 part of the algorithm. HSDPA users, unless they have been rejected during the R99 part of the algorithm, are then evaluated by the HSDPA part of the algorithm.

Description of the R99 Part of the Simulation

The R99 part of the algorithm simulates power control, congestion and radio resource control performed for R99 bearers for both R99 and HSDPA users. Atoll considers each user in the order in which the users are generated, and determines his best server. Atoll then selects the cell and the timeslot to be allocated to each user as follows: 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. Load: The least loaded cell or timeslot is selected. 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 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.

Available RUs: The cell or timeslot with the most available resource units is selected.

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. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

915

Atoll User Manual 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.

Sequential: Cells and timeslots are selected in a sequential order. -

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: DL DL: Cell A and cell B both transmitting in downlink. UL UL: Cell A and cell B both receiving in uplink. DL UL: Cell A receiving in uplink and cell B transmitting in downlink. UL DL: Cell A transmitting in downlink and cell B receiving in uplink.

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: The signal quality is not sufficient: 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" 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"

Even if constraints above are respected, the network (cell and timeslot) may be saturated:

Description of the HSDPA Part of the Simulation

In the HSDPA part, Atoll processes all HSDPA bearer users. The HSDPA part of the algorithm simulates fast link adaptation, the scheduling of HSDPA users, and radio resource control on downlink. Two fast link adaptations are done, one before mobile scheduling and one after. HSDPA bearer selection is based on look-up tables available in the HSDPA Bearer Selection tab of the reception equipment properties. The HSDPA and HS-SCCH powers of a cell are evaluated before calculating HS-PDSCH EcNt. The 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 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 HSDPA power and the HS-SCCH power), calculates the HS-PDSCH EcNt and, from that, the HSDPA bearer defined for the terminal reception equipment and the user mobility). Similarly, the terminal power per HS-SICH in the uplink can be either fixed or dynamically allocated in order to attain the HS-SICH EcNt threshold. Before mobile scheduling, each user is processed as if he is the only user in the cell. This means that Atoll determines the HSDPA bearer for each HSDPA user by considering the entire HSDPA power available of the cell. During scheduling, cell radio resources are shared between HSDPA users by the scheduler. The scheduler simultaneously manages the maximum number of users within each cell and ranks them according to the selected scheduling technique: 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 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.

916

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

9.3.5.2

Creating Simulations
In Atoll, simulations enable you to model TD-SCDMA network regulation mechanisms in order to minimise interference and maximise capacity. You can create one simulation or a group of simulations that will be performed in sequence. To create a simulation or a group of simulations: 1. Click the Data tab in the Explorer window. 2. Right-click the TD-SCDMA Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name and Comments for this simulation or group of simulations. 5. Under Execution on the General tab, you can set the following parameters: Number of Simulations: Enter the number of simulations to be carried out. All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. Information to retain: You can select the level of detail that will be available in the output: Only the Average Simulation and Statistics: None of the individual simulations are displayed or available in the group. Only an average of all simulations and statistics is available. Some calculation and display options available for coverage predictions are not available when the option "Only the average simulation and statistics" is selected. No Information About Mobiles: All the simulations are listed and can be displayed. For each of them, a properties window containing simulation output, divided among four tabs Statistics, Sites, Cells, and Initial Conditions is available. Standard Information About Mobiles: All the simulations are listed and can be displayed. The properties window 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.

Note:

Tip:

When you are working on very large radio-planning projects, you can reduce memory consumption by selecting Only the Average Simulation and Statistics under Information to retain.

6. Under Cell Load Constraints on the General tab, you can set the constraints that Atoll must respect during the simulation: 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 load factor, click the button ( ) beside the box and select Global Threshold. Then, enter a maximum uplink load factor. If you want to use the maximum uplink load factor defined for each timeslot in a 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 load in the Max DL Load box. Max DL Load (% Pmax): If you want to enter a global value for the maximum downlink load as a percentage of the maximum power, click the button ( ) beside the box and select Global Threshold. Then, enter a maximum downlink load as a percentage of the maximum power. If you want to use the maximum downlink load defined for each timeslot in a cell, click the button ( ) beside the box and select Defined per Cell.

7. On the TD-SCDMA tab of the dialogue, 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 "Types of Smart Antenna Modelling" on page 955. 8. Under DCA Strategies, select the strategy to be used for selecting carriers and timeslots during the simulations. There are four different strategies available: Load: The least loaded cell or timeslot is selected. Available RUs: The cell or timeslot with the most available resource units is selected. 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. Sequential: Cells and timeslots are selected in a sequential order.

For more information about the DCA strategies, see "The Monte Carlo Simulation Algorithm" on page 914. 9. Select the Calculate Interference Between Mobiles check box and enter a maximum distance to consider between interfering mobiles in the Max Distance field. 10. On the Source Traffic tab, enter the following:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

917

Atoll User Manual Global Scaling Factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates or users (for sector traffic maps). Select Traffic Maps to Be Used: Select the traffic maps you want to use for the simulation. You can select traffic maps of any type. However, if you have several different types of traffic maps and want to make a simulation 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 "Creating a Traffic Map" on page 905. 11. Click the Advanced tab. 12. Under Generator Initialisation, enter an integer as the generator initialisation value. If you enter "0", the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value.

Tip:

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.

13. Under Convergence, enter the following parameters: Max No. of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the uplink that must be reached between two iterations. DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the downlink that must be reached between two iterations.

14. 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 "The Global Transmitter Parameters" on page 953. 15. Once you have defined the simulation, you can run it immediately or you can save it to run it later: Run: Click Run to save the defined simulation and run it immediately OK: Click OK to save the defined simulation without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. You can now use the completed simulations for specific TD-SCDMA and HSDPA coverage predictions (see "Making Coverage Predictions Using Simulation Results" on page 928).

9.3.5.3

Displaying the Traffic Distribution on the Map

Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to service, activity status, or pilot signal strength. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 33. In this section are the following examples of traffic distribution: "Displaying the Traffic Distribution by Activity Status" on page 918. "Displaying the Traffic Distribution by Connection Status" on page 919. "Displaying the Traffic Distribution by Service" on page 919.

Tip:

You can make the traffic distribution easier to see by hiding geo data and predictions. For information, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.

9.3.5.3.1

Displaying the Traffic Distribution by Activity Status

In this example, the traffic distribution is displayed by the activity status. To display the traffic distribution by the activity status: 1. Click the Data tab in the Explorer window. 2. Right-click the TD-SCDMA Simulations folder. The context menu appears. 3. Select Properties from the context menu. The TD-SCDMA Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "DL Activity" or "UL Activity" as the Field. 5. Click OK. The traffic distribution is now displayed by downlink or uplink activity status (see Figure 9.491).

918

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Figure 9.491: Displaying the traffic distribution by downlink activity status

9.3.5.3.2

Displaying the Traffic Distribution by Connection Status

In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Click the Data tab in the Explorer window. 2. Right-click the TD-SCDMA Simulations folder. The context menu appears. 3. Select Properties from the context menu. The TD-SCDMA Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "Connection Status" as the Field. 5. Click OK. The traffic distribution is now displayed by connection status (see Figure 9.492).

Figure 9.492: Displaying the traffic distribution by connection status

9.3.5.3.3

Displaying the Traffic Distribution by Service

In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Click the Data tab in the Explorer window. 2. Right-click the TD-SCDMA Simulations folder. The context menu appears. 3. Select Properties from the context menu. The TD-SCDMA Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 9.493).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

919

Atoll User Manual

Figure 9.493: Displaying the traffic distribution by service

9.3.5.4

Displaying the User Best Server on the Map

Atoll enables you to display on the map the best serving transmitter for each user generated by a simulation. To display the best server for a user: On the map, click and hold the icon of the user whose best server you want to display. The users best server is connected to the user with a line of the same colour as the serving transmitter. The best server is indicated with the number "1". Figure 9.494 shows a user with its best server.

Figure 9.494: The best server of a user

9.3.5.5

Displaying the Results of a Single Simulation

After you have created a simulation, as explained in "Creating Simulations" on page 917, you can display the results. To access the results of a single simulation: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( you want to access. ) to expand the TD-SCDMA Parameters folder. ) to expand the folder of the simulation group containing the simulation whose results

4. Right-click the simulation. The context menu appears. 5. Select Properties from the context menu. A simulation properties dialogue appears. One tab gives statistics of the results of the simulation. Other tabs in the simulation properties dialogue contain simulation results as identified by the tab title. A final tab lists the initial conditions of the simulation. The Statistics tab: The Statistics tab contains the following two sections: Request: Under Request, you will find data on the connection requests: Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet finished. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the UL and DL rates that all users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL rates) is given. The number of iterations that were run in order to converge.

Results: Under Results, you will find data on the connection results: -

920

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks The number and the percentage of non-connected users is given along with the reason for rejection. These figures include rejected and delayed users. These figures are determined at the end of the simulation and depend on the network design. The number and percentage of R99 bearer users connected to a cell, the number of users per activity status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm. These data are also given per service. The total number and the percentage of connected users with an HSDPA bearer, the number of users per activity status, and the DL total rate that they generate.

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 Rate (kbps): The instantaneous HSDPA rate 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: 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. 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. DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic 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 exceed the user-defined Max DL Load. P Cell = Used i DL UL Load

PTimeslot
Used i UL

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. F Cell = Avg ( F Timeslot )
i

UL Load

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. F Cell
DL Load

= Avg ( F Timeslot )
i DL
i

DL Load

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 over the total number of users in the cell. UL Total Requested Rate (kbps): The sum of all the uplink throughputs requested by the mobiles attempting to connect to a carrier. DL Total Requested Rate (kbps): The sum of all the downlink throughputs requested by mobiles attempting to connect to a carrier. UL Total Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the uplink. DL Total Obtained Rate (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 over 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: Forsk 2010 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. Other CCH power (dBm): The power of other common channels per timeslot. Gain (dBi): The gain as defined in the antenna properties for that transmitter. Unauthorized reproduction or distribution of this document is prohibited

921

Atoll User Manual 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. DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot. 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 dialogue. 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). Resource Units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a maximum of 16 resource units. 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 HSPDSCH 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.

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: 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: The activity status on the downlink assigned during the first random trial, during the generation of the user distribution. UL Activity: 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 Rate (kbps): For an R99 user, the uplink total requested rate corresponds to the uplink nominal rate of the R99 bearer associated to the service. For an HSDPA user, the uplink total requested rate corresponds to the nominal rate of ADPCH-UL64 R99 bearer. DL Total Requested Rate (kbps): For an R99 user, the downlink total requested rate corresponds to the downlink nominal rate of the R99 bearer associated to the service. For an HSDPA user, the downlink total requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate that the selected HSDPA radio bearer can provide. UL Total Obtained Rate (kbps): For an R99 user, the total obtained rate is the same as the total requested rate if he is connected. If the user was rejected, the total obtained rate is zero. For an HSDPA user connected to an HSDPA bearer, the uplink total obtained rate equals the total requested rate. If the HSDPA user is delayed (he is only connected to an R99 radio bearer), the uplink total obtained rate corresponds to the uplink nominal rate 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 rate is zero. DL Total Obtained Rate (kbps): For an R99 user, the total obtained rate is the same as the total requested rate if he is connected. If the user was rejected, the total obtained rate is zero.

922

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks For an HSDPA user connected to an HSDPA bearer, the downlink total obtained rate corresponds to the instantaneous rate; this is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio 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 rate corresponds to the downlink nominal rate 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 rate is zero. 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 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 917, 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 rate. 1st, 2nd, 3rd TS Obtained HSDPA Power (dBm): This is the HSDPA power required to provide the HSDPA bearer user with the downlink obtained rate. 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: Note: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 917, you select "Detailed information about mobiles" under Information to Retain.

Name: The name assigned to the mobile. Value at Receiver (dB): The value of the shadowing margin at the receiver. Clutter: The clutter class on which the mobile is located. Path To: The name of the potential transmitter. Value (dB): The shadowing value for the potential link in the corresponding Path To column. These values depend on the model standard deviation per clutter type on which the receiver is located and are randomly distributed on a gaussian curve.

The Initial Conditions tab: The Initial Conditions tab contains the following information: The global transmitter parameters: The spreading width The quality threshold type The method used to calculate Nt The method used to calculate Nt for HSDPA. The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink convergence thresholds The simulation constraints such as maximum DL load and the maximum UL load factor The name of the traffic maps used

The input parameters specified when creating the simulation:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

923

Atoll User Manual The parameters defined per clutter class, such as the uplink and downlink orthogonality factors, indoor loss, spreading angle, and the various standard deviations (Model, P-CCPCH EbNt or CI, DL EbNt or CI, and UL EbNt or CI).

The parameters related to the clutter classes, including the default values.

9.3.5.6

Displaying the Average Results of a Group of Simulations

After you have created a group of simulations, as explained in "Creating Simulations" on page 917, you can display the average results of the group. If you want to display the results of a single simulation of a group, see "Displaying the Results of a Single Simulation" on page 920. To access the averaged results of a group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the group of simulations whose results you want to access. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. The Statistics tab: The Statistics tab contains the following two sections: Request: Under Request, you will find data on the connection requests: Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet finished. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the UL and DL rates that all users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL rates) is given. The number of iterations that were run in order to converge. The number and the percentage of non-connected users is given along with the reason for rejection. These figures include rejected and delayed users. These figures are determined at the end of the simulation and depend on the network design. The number and percentage of R99 bearer users connected to a cell, the number of users per activity status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm. These data are also given per service. The total number and the percentage of connected users with an HSDPA bearer, the number of users per activity status, and the DL total rate that they generate.

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 contain the following average and standard deviation information, respectively, 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 Rate (kbps): The instantaneous HSDPA rate 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 (Average) and Cells (Standard Deviation) tabs: The Cells (Average) and Cells (Standard Deviation) tabs contain the following average and standard deviation information, respectively, per site, transmitter, and carrier: 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. 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. DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic 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 exceed the user-defined Max DL Load. 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. Number of DL Radio Links: The number of downlink radio links corresponds to the number of user-transmitter links on the same carrier. This data indicates the number of users connected to the cell on the downlink.

924

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Number of UL Radio Links: The number of uplink radio links corresponds to the number of user-transmitter links on the same carrier. 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 over the total number of users in the cell. UL Requested Rate (kbps): The traffic demand in terms of throughput in the uplink. UL Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the uplink. DL Requested Rate (kbps): The traffic demand in terms of throughput in the downlink. DL Obtained Rate (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 available 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 available 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 over the total number of users of that service in the cell.

The Timeslots (Average) and Timeslots (Standard Deviation) tabs: The Timeslots (Average) and Timeslots (Standard Deviation) tabs contain the following average and standard deviation information, respectively, per site, transmitter, carrier, and timeslot: 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. Other CCH power (dBm): The power of other common channels per 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. DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot. 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 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 dialogue. 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 when the simulation is defined, 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). Resource Units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a maximum of 16 resource units. 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 fixed by the user when the HS-PDSCH power is allocated statically, or 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.

The Initial Conditions tab: The Initial Conditions tab contains the following information: The global transmitter parameters: The spreading width The quality threshold type The method used to calculate Nt The method used to calculate Nt for HSDPA. The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink convergence thresholds The simulation constraints such as maximum DL load and the maximum UL load factor The name of the traffic maps used The parameters defined per clutter class, such as the uplink and downlink orthogonality factors, indoor loss, spreading angle, and the various standard deviations (Model, P-CCPCH EbNt or CI, DL EbNt or CI, and UL EbNt or CI). Unauthorized reproduction or distribution of this document is prohibited

The input parameters specified when creating the group of simulations:

Forsk 2010

925

Atoll User Manual The parameters related to the clutter classes, including the default values.

9.3.5.7

Updating Cell and Timeslot Values With Simulation Results

After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 917, you can update values for each cell with the results calculated during the simulation. The following values are updated: Cell: Required resource units in uplink and downlink Number of HSDPA users. DL traffic power UL load factor Available HSDPA power Angular distribution of UL and DL loads

Timeslot:

To update cell and timeslot values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

c. Right-click the group of simulations whose results you want to access. d. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. To display the results for a single simulation: a. Click the Data tab in the Explorer window. b. Click the Expand button ( c. Click the Expand button ( sults you want to access. ) to expand the TD-SCDMA Parameters folder. ) to expand the folder of the simulation group containing the simulation whose re-

d. Select Properties from the context menu. A simulation properties dialogue appears. 2. Click the Cells tab. 3. On the Cells tab, click the Commit Results button. The cell and timeslot values will be updated with the simulation or the average simulation results.

9.3.5.8

Adding New Simulations to an Atoll Document

When you have created a simulation or group of simulations, you can re-examine the same conditions by adding new simulations to the Atoll document. In Atoll, you can add new simulations in the following ways: Adding to a group: When you add one or more simulations to an existing group of simulations, Atoll reuses the input (radio, traffic, and simulation parameters) used to generate the group of simulations. It then generates a new user distribution and performs the power control simulation. To add a simulation to a group of simulations, see "Adding a Simulation to a Group of Simulations" on page 927. Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution (users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shadowing error distribution between simulations is different. Traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, EbNt or CI thresholds, etc.) may be taken into account or not. Finally, radio data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the power control (or rate/power control) simulation. To replay a group of simulations, see "Replaying a Simulation or Group of Simulations" on page 927. Using the Generator Initialisation Number: When you create groups of simulations using the same generator initialisation number (which must be an integer other than 0), Atoll generates the same user and shadowing error distributions (user with a service, a mobility, an activity status, and a shadowing error) in all groups using the same number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers allowed, EbNt or CI thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during the power control simulation. By creating and calculating one group of simulations, making a change to the network and then creating and calculating a new group of simulations using the same generator initialisation number, you can see the difference your parameter changes make.

926

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks To create a new simulation to a group of simulations using the generator initialisation number, see "Adding a Simulation to a Group of Simulations" on page 927. Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation parameters as those used to generate the group of simulations. You can then modify the simulation parameters before calculating the group. To duplicate a group of simulations, see "Duplicating a Group of Simulations" on page 928.

Adding a Simulation to a Group of Simulations

To add a simulation to an existing group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Simulations folder.

3. Right-click the group of simulations to which you want to add a simulation. The context menu appears. 4. Select New from the context menu. The properties dialogue of the group of simulations appears. Note: When adding a simulation to an existing group of simulations, the parameters originally used to calculate the group of simulations are used for the new simulations. Consequently, few parameters can be changed for the added simulation.

5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations. 6. Under Execution on the General tab, you can set the following parameters: Number of Simulations: Enter the number of simulations to added to this group of simulations.

7. Click OK. Atoll immediately begins the simulation.

Replaying a Simulation or Group of Simulations

To replay an existing simulation or group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Simulations folder.

3. Right-click the group of simulations you want to replay. The context menu appears. 4. Select Replay from the context menu. The properties dialogue of the group of simulations appears. Note: When replaying an existing group of simulations, some parameters originally used to calculate the group of simulations are reused for the replayed group. Consequently, few parameters can be changed for the replayed group.

5. In the General tab of the dialogue, you can set the following parameters: Select the level of detail as explained in "Creating Simulations" on page 917 that will be available in the output from the Information to retain list. Under Cell Load Constraints, you can set the constraints as explained in "Creating Simulations" on page 917 that Atoll must respect during the simulation.

6. In the Source Traffic tab of the dialogue, select the Refresh Traffic Parameters check box if you want to take into account traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) in the replayed simulation. 7. In the Advanced tab, you can set the following parameters: Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. 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. 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 "The Global Transmitter Parameters" on page 953.

8. In the TD-SCDMA tab, you can set the following parameters: Angular Step: The angle in degrees used to build the geometrical distributions of uplink and downlink loads. The angular step in used with grid of beams, statistical, and adaptive beam modelling. For more information on the different smart antenna models, see "Types of Smart Antenna Modelling" on page 955. Carrier Selection and Timeslot Selection: The DCA strategies to be used for selecting carriers and timeslots during the simulations. For more information about the DCA strategies, see "The Monte Carlo Simulation Algorithm" on page 914. Calculate Interference Between Mobiles: Select the check box and enter a maximum distance to be considered between interfering mobiles in the Max Distance field.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

927

Atoll User Manual 9. Click OK. Atoll immediately begins the simulation.

Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number
To create a new simulation or group of simulations using the generator initialisation number: 1. Click the Data tab in the Explorer window. 2. Right-click the TD-SCDMA Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. Click the Advanced tab. 5. Under Generator Initialisation, enter an integer as the generator initialisation value. The integer must be the same generator initialisation number as used in the group of simulations with the user and shadowing error distributions you want to use in this simulation or group of simulations. If you enter "0", the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. 6. For information on setting other parameters, see "Creating Simulations" on page 917.

Tip:

You can create a new group of simulations with the same parameters as the original group of simulations by duplicating an existing one as explained in "Duplicating a Group of Simulations" on page 928.

Duplicating a Group of Simulations

To duplicate an existing group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Simulations folder.

3. Right-click the group of simulations you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The properties dialogue for the duplicated group of simulations appears. You can change the parameters for the duplicated group of simulations as explained in "Creating Simulations" on page 917.

9.3.5.9

Estimating a Traffic Increase

When you create a simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against a higher traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates or users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations by: Creating a new simulation or group of simulations as described in "Creating Simulations" on page 917. Duplicating an existing simulation or group of simulations as described in "Adding New Simulations to an Atoll Document" on page 926.

2. Click the Source Traffic tab of the properties dialogue. 3. Enter a Global Scaling Factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the ratesusers (for sector traffic maps).

9.3.6

Making Coverage Predictions Using Simulation Results

When no simulations are available, Atoll uses the UL load factor, the DL traffic power, and the available HSDPA power defined per timeslot, and the number of HSDPA users defined per cell to make coverage predictions. For information on cell properties, see "Cell Description" on page 816; for information on modifying cell properties, see "Creating or Modifying a Cell" on page 820. Once you have made simulations, Atoll can use this information instead of the user-defined parameters in the cell properties to make coverage predictions where each pixel is considered as a probe user with a terminal, mobility, user profile, and service. To base a coverage prediction on a simulation or group of simulations, store the results of a simulation or the average results of a group of simulations in the Cells and Cell Parameters per Timeslot tables as explained in: "Updating Cell and Timeslot Values With Simulation Results" on page 926.

To be able to base a coverage prediction on a simulation or group of simulations, the simulation must have converged. The coverage predictions that can use simulation results are: Coverage predictions on P-CCPCH EbNt or CI, or on a service EbNt or CI:

928

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks P-CCPCH Reception Analysis (EbNt) or P-CCPCH Reception Analysis (CI): For information on making a P-CCPCH reception analysis, see "Making a Pilot Signal Quality Prediction" on page 863. DwPCH Reception Analysis (CI): For information on making a DwPCH reception analysis, see "Making a DwPCH Signal Quality Prediction" on page 864. Service Area (EbNt) Downlink or Service Area (CI) Downlink: For information on making a coverage prediction the downlink service area, see "Studying Downlink and Uplink Service Areas" on page 867. Service Area (CI) Uplink: For information on making a coverage prediction the uplink service area, see "Studying Downlink and Uplink Service Areas" on page 867. Effective Service Area (EbNt) or Effective Service Area (CI): For information on making a coverage analysis for the effective service area, see "Studying Effective Service Area" on page 869. Downlink Total Noise: For information on making a downlink total noise coverage prediction, see "Studying Downlink Total Noise" on page 872. 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 873. UpPCH Interference Zones: For information on making a coverage analysis for UpPCH interference in case of UpPCH shifting, see "Studying UpPCH Interference" on page 874. Baton Handover: For information on making a baton handover coverage prediction, see "Making a Baton Handover Coverage Prediction" on page 876. HSDPA Coverage Prediction: For information on making an HSDPA coverage prediction, see "HSDPA Coverage Prediction" on page 877.

Coverage predictions on noise and interference: -

A coverage prediction for baton handover analysis: -

An HSDPA coverage prediction to analyse HS-PDSCH quality and HSDPA data rate: -

9.4

Verifying Network Capacity

An important step in the process of creating a TD-SCDMA network is verifying the capacity of the network. This is done using measurements of the P-CCPCH RSCP in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: "Importing a Drive Test Data Path" on page 929 "Displaying Drive Test Data" on page 931 "Defining the Display of a Drive Test Data Path" on page 932 "Network Verification" on page 932 "Exporting a Drive Test Data Path" on page 936 "Extracting CW Measurements from Drive Test Data" on page 936 "Printing and Exporting the Drive Test Data Window" on page 937.

9.4.1

Importing a Drive Test Data Path

In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: The position of drive test data points: When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells): In TD-SCDMA networks, a cell is identified by its scrambling code. Therefore, you must indicate during the import process which columns contain the cells scrambling code and the scrambling code format (decimal or hexadecimal) used in the file. Because a scrambling code can belong to several groups, you can also indicate the group from which the scrambling code has been selected.

You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test data files of the same format, you can create an import configuration. The import configuration contains information that defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the data structure each time you import a new drive test data file. To import one or several drive test data files: 1. Click the Data tab in the Explorer window. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. You can import one or several files. Select the file or files you want to open. 5. Click Open. The Import of Measurement Files dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

929

Atoll User Manual

Note:

Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue.

6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Configuration, select an import configuration from the Configuration list. b. Continue with step 10. Notes: When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. In case several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.

7. Click the General tab. On the General tab, you can set the following parameters: Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document. 8. Click the Setup tab (see Figure 9.495).

Figure 9.495: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click Setup to link file columns and internal Atoll fields. The Drive Test Data Configuration dialogue appears. c. 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.

930

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Note:

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. In the SC 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 SC Group Identifier box empty. e. In the SC Identifier box, enter a string that must be 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. f. From the Scramb. Code Format list, select the scrambling code format, either "Decimal" or "Hexadecimal."

g. Click OK to close the Drive Test Data Configuration dialogue. Important: If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Configuration dialogue, Atoll should recognize all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>". If a column is marked with "<Ignore>", it will not be imported. The data in the file must be structured so that the columns identifying the scrambling code group and the scrambling code are placed before the data columns for each cell. Otherwise Atoll will not be able to properly import the file.

9. If you want to save the definition of the data structure so that you can use it again, you can save it as an import configuration: a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a special 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, "*.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. Notes: 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 button ( ) in front of the file in the Setup part to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Setup 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.

9.4.2

Displaying Drive Test Data

When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see information about the active set at that location. To display information about a single drive test data point: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want active set information. Atoll displays an arrow pointing towards the serving cells (see Figure 9.497 on page 935), with a number identifying the server as numbered in the

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

931

Atoll User Manual drive test data. If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display Type" on page 33.

9.4.3

Defining the Display of a Drive Test Data Path

You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to manage permanent labels on the map, tooltips and the legend. In other words, the display of measurement path are managed in the same way as sites, transmitters, etc. To display the Display tab of a drive test data paths Properties dialogue: 1. Click the Data tab in the Explorer window. 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: a text or integer attribute (discrete value) a numerical value (value interval).

In addition, you can display points by more than one criterion at a time using the Multiple Shadings option in the Display Type list. When you select Multiple Shadings from the Display Type list, a dialogue opens in which you can define the following display for each single point of the measurement path: a symbol according to any attribute a symbol colour according to any attribute a symbol size according to any attribute

You can, for example, display a signal level in a certain colour, choose a symbol type for Transmitter 1 (a circle, triangle, cross, etc.) and a symbol size according to the altitude. Notes: 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 Multiple Shadings if the Fast Display check box has been selected. You can sort drive test data paths in alphabetical order on the Data tab of the Explorer window by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can export the display settings of a drive test data path in a configuration file to make them available for future use. You can export the display settings or import display settings by clicking the Actions button on the Display tab of the drive test data paths Properties dialogue and selecting Export or Import from the menu.

9.4.4

Network Verification
The imported drive test data is used to verify the TD-SCDMA network. To improve the relevance of the data, Atoll allows you to filter out incompatible or inaccurate measurement points. You can then use the data for coverage predictions, either by comparing the imported measurements with previously calculated coverage predictions, or by creating new coverage predictions using the imported drive test data. In this section, the following are explained: "Filtering Incompatible Points Along Drive Test Data Paths" on page 932 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 934 "Analysing Data Variations Along the Path" on page 935.

9.4.4.1

Filtering Incompatible Points Along Drive Test Data Paths

When using a drive test data path, some measured points may present values that are too far outside of the median values to be useful. As well, drive test data paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points:

932

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 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 Drive Test Data Filter dialogue 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. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder.

The context menu appears. 3. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 4. Click More. The Filter dialogue appears. 5. Click the Filter tab: a. Select a Field from the list. b. Under Values to Include, you will find all the values represented in the selected field. Select the check boxes next to the values you want to include in the filter. Click Clear All to clear all check boxes. 6. Click the Advanced tab: a. In the Column row, select the name of the column to be filtered on from the list. Select as many columns as you want (see Figure 9.496).

Figure 9.496: The Filter dialogue - Advanced tab b. Underneath each column name, enter the criterion on which the column will be filtered as explained in the following table:

Formula
=X <> X <X >X <=X >=X *X*

Data are kept in the table only if

value equal to X (X may be a number or characters) value not equal to X (X may be a number or characters) numerical value is less than X numerical value is greater than X numerical value is less than or equal to X numerical value is greater than or equal to X text objects which contain X

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

933

Atoll User Manual

Formula
*X X*

Data are kept in the table only if

text objects which end with X text objects which start with X

7. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering" on page 75. 8. Click OK to apply the filter and close the dialogue. Note: The Refresh Geo Data option available in the context menu of Drive Test Data paths enables you to update heights (DTM, clutter heights, DTM + clutter) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones.

9.4.4.2

Displaying Statistics Over a Drive Test Data Path

Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific Drive Test Data path: 1. Click the Data tab in the Explorer window. 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 dialogue 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.3

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. Click the Data tab in the Explorer window. 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 dialogue appears. 5. Select a transmitter from the On the Transmitter list. 6. Click the For the Fields list. The list opens. 7. Select the check box beside the field you want to extract for the selected transmitter. Note: Atoll can display the best server. 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 path data table for the selected transmitters and with the selected values.

934

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

9.4.4.4

Analysing Data Variations Along the Path

In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point. To analyse data variations using the Drive Test Data window. 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 9.497).

Figure 9.497: The Drive Test Data window 5. Click Display at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 9.498).

Figure 9.498: Drive test data display parameters 6. In the Display Parameters dialogue: Select the check box next to any field you want to display in the Drive Test Data window. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue. Note: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

935

Atoll User Manual The selected fields are displayed in the Drive Test Data window. 7. You can display the data in the drive test path in two ways: Click the values in the Drive Test Data window. Click the points on the drive test path in the map window.

The drive test data path appears in the map window as an arrow pointing towards the serving cell, with a number identifying the best server (see Figure 9.497 on page 935). If the transmitter display type is "Automatic," both the number and the arrow are displayed in the same colour as the transmitter. For information on changing the display type to "Automatic," see "Defining the Display Type" on page 33. 8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the secondary Y-axis from the right-hand list on the top of the Drive Test Data window. The selected values are displayed in the colours defined for this variable in the Display Parameters dialogue. 9. You can change the zoom level of the Drive Test Data window display in the following ways: Zoom in or out: i. Right-click the Drive Test Data window.

ii. Select Zoom In or Zoom Out from the context menu. Select the data to zoom in on: i. Right-click the Drive Test Data window on one end of the range of data you want to zoom in on.

ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data window on the other end of the range of data you want to zoom in on. iv. Select Last Zoom Point from the context menu. The Drive Test Data window zooms in on the data between the first zoom point and the last zoom point. 10. Click the data in the Drive Test Data window to display the selected point in the map window. Atoll will recentre the map window on the selected point if it is not presently visible.

Tip:

If you open the table for the drive test data you are displaying in the Drive Test Data window, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data window (see Figure 9.497 on page 935).

9.4.5

Exporting a Drive Test Data Path

You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.

9.4.6

Extracting CW Measurements from Drive Test Data

You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears. 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the Transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the For the Fields list. 6. Under CW Measurement Creation Parameters: a. Enter the Min. Number of Points to Extract per Measurement Path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured Signal Levels. CW measurements are created with drive test data points where the signal levels are within this specified range.

936

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.

9.4.7

Printing and Exporting the Drive Test Data Window

You can print or export the contents of the Drive Test Data window, using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 9.497 on page 935). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 935. 6. Right-click the Drive Test Data window. The context menu appears. To export the Drive Test Data window: a. Select Copy from the context menu. b. Open the document into which you want to paste the contents of the Drive Test Data window. c. Paste the contents of the Drive Test Data window into the new document. To print the Drive Test Data window: a. Select Print from the context menu. The Print dialogue appears. b. Click OK to print the contents of the Drive Test Data window.

9.5

Co-planning TD-SCDMA Networks with Other Networks

Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a TD-SCDMA and a GSM network for the same area in Atoll, and then work with Atolls co-planning features to study the mutual impacts of the two networks. Important: Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other networks Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In this section, the following are explained: "Switching to Co-planning Mode" on page 937. "Working with Coverage Predictions in a Co-Planning Project" on page 939. "Performing Inter-Technology Neighbour Allocation" on page 942. "Creating a TD-SCDMA Sector From a Sector in the Other Network" on page 952. "Ending Co-planning Mode" on page 952.

9.5.1

Switching to Co-planning Mode

Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a TD-SCDMA Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, the TD-SCDMA document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Important: Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

937

Atoll User Manual To switch to co-planning mode: 1. Open the main document. Select File > Open or File > New > From an Existing Database.

2. Link the other document with the open main document. a. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document. b. Select File > Link With. The Link With dialogue appears. c. Select the document to be linked. d. Click Open. The selected document is opened in the same Atoll session as the main document and the two documents are linked. The Explorer window of the main document now contains a folder named Transmitters in [linked document], where [linked document] is the name of the linked document and another folder named Predictions in [linked document]. Note: By default, only the Transmitters and Predictions folders of the linked document appear in the main document. If you want the Sites folder of the linked document to appear in the main document as well, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.

As soon as a link is created between the two documents, Atoll switches to co-planning mode and Atolls co-planning features are now available. When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll syncronises the display for the following: Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.

Displaying Both Networks in the Same Atoll Document

After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 937, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the Explorer window of the linked document to the Explorer window of the main document (e.g., you can display GSM sites and measurement paths in a TD-SCDMA document). To display sites from the linked document in the main document: 1. Click the linked documents map window. The linked documents map window becomes active and the Explorer window shows the contents of the linked document. 2. Click the Data tab of the Explorer window. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In > [main document] from the context menu, where [main document] is the name of the main document. 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 rightclicking 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 82. You

938

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks can also set the tool tips to enable you to distinguish the objects and data displayed on the map. For more information on tool tips, see "Defining the Object Type Tip Text" on page 36. In order to more easily view differences between the networks, you can also change the order of the folders or items in the Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers Using the Explorer" on page 28. Figure 9.499 shows an example of TD-SCDMA transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in a tool tip.

Figure 9.499: GSM and TD-SCDMA Transmitters displayed on the map

9.5.2

Working with Coverage Predictions in a Co-Planning Project

Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: "Updating Coverage Predictions" on page 939 "Analysing Coverage Predictions" on page 940.

9.5.2.1

Updating Coverage Predictions

You can access the properties of the coverage predictions in the linked Predictions folder in the main documents Explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button ( ) 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 Coverage Predictions" on page 185. If you want, you can make Atoll recalculate all path loss matrices, including valid ones, before calculating unlocked coverage predictions in the main and linked Predictions folders. To force Atoll to recalculate all path loss matrices before calculating coverage predictions: Click the Force Calculate button ( ) in the toolbar.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

939

Atoll User Manual 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. Note: 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

Analysing Coverage Predictions

In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tooltips to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which studies to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following are explained: "Co-Planning Coverage Analysis Process" on page 940 "Displaying the Legend Window" on page 941 "Comparing Coverage Prediction Results Using Tooltips" on page 941 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 941 "Studying Differences Between Coverage Areas" on page 942.

9.5.2.2.1

Co-Planning Coverage Analysis Process

The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. Note: In a co-planning environment, many sites share the same antennas, using one mast for both technologies. When transmitter, remote antenna, or repeater antennas have the same co-ordinates and the same value set for the SHAREDMAST field in both coplanning documents, Atoll assumes that the antennas are shared. Atoll then automatically synchronises changes made to shared antenna parameters in one coplanning document in the other document. The shared antenna parameters include the site location (X and Y coordinates), the antenna's position relative to the site (Dx, Dy), antenna height, azimuth and mechanical tilt. The SHAREDMAST field is not available by default and must be added in order for the synchronization mechanism to operate. For information on setting up shared antenna parameter synchronisation, see the Administrator Manual.

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 P-CCPCH Best Server (best server with 0 dB margin) coverage prediction and a Coverage by P-CCPCH RSCP coverage prediction in the main document. For more information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 845 and "Making a Coverage Prediction by PCCPCH RSCP" on page 844. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tool tip contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage predictions Properties dialogue. 4. Make the two new coverage predictions in the linked document accessible in the main document as described in "Displaying Both Networks in the Same Atoll Document" on page 938. 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 941 and "Studying Differences Between Coverage Areas" on page 942. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.

940

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

9.5.2.2.2

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

9.5.2.2.3

Comparing Coverage Prediction Results Using Tooltips

You can compare coverage predictions by by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltip. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Co-Planning Coverage Analysis Process" on page 940). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 9.450). The tooltip for the working document is on top and the tooltip for the linked document, with the linked document identified by name is on the bottom.

Figure 9.500: Comparing coverage prediction results using tooltips

9.5.2.2.4

Comparing Coverage Areas by Overlaying Coverage Predictions

You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is dislayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 32. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is dislayed on the map. 11. Right-click the coverage prediction. The context menu appears. 12. Select Properties from the context menu. The coverage prediction Properties dialogue 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 "Working with Layers Using the Explorer" on page 28.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

941

Atoll User Manual

9.5.2.2.5

Studying Differences Between Coverage Areas

You can compare coverage predictions to find differences in coverage areas. To compare coverage predictions: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Right-click the coverage prediction of the main document you want to compare. The context menu appears. 5. Select Compare With > [linked coverage prediction] from the context menu, where [linked coverage prediction] is the linked coverage prediction you want to compare with the coverage prediction of the main document. The Comparison Properties dialogue opens. 6. Select the display parameters of the comparison and add a comment if you want. 7. Click OK. The two coverage predictions are compared and a comparison coverage prediction is added to the main documents Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 855.

9.5.3

Performing Inter-Technology Neighbour Allocation

The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between a TD-SCDMA and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to TD-SCDMA cells. In this section, the following are explained: "Setting Inter-Technology Exceptional Pairs" on page 942 "Configuring Importance Factors for Inter-Technology Neighbours" on page 944 "Allocating Inter-Technology Neighbours Automatically" on page 944 "Displaying Inter-Technology Neighbours on the Map" on page 946 "Allocating and Deleting Inter-Technology Neighbours per Cell" on page 947 "Calculating the Importance of Existing Inter-technology Neighbours" on page 949 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 951.

In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Co-planning Mode" on page 937.

9.5.3.1

Setting Inter-Technology Exceptional Pairs

You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Exceptional Pairs from the context menu. The Exceptional Pairs of Inter-technology Neighbours table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. d. Atoll fills the Number and Distance (m) fields automatically. In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector). You can access a cells inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cells Properties dialogue: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears.

942

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 4. Double-click the row corresponding to the cell whose properties you want to access. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitters Properties dialogue.

Displaying Inter-Technology Exceptional Pairs on the Map

You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select which exceptional pair links to display: Outwards Non-Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Selecting this option displays an exceptional pair link for each transmitter/cell in the linked document that has an exceptional pair defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Forced Neighbours or Forbidden Neighbours from the menu. The exceptional pair of a cell will be displayed when you select a transmitter. 8. Click the Visual Management button ( ) in the Radio toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Visual Management button again. 9. Click a transmitter on the map to show its exceptional pair links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map.

Adding and Removing Inter-Technology Exceptional Pairs on the Map

You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-Technology Exceptional Pairs on the Map" on page 943. To add a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set an exceptional pair. Atoll adds both transmitters to the list of inter-technology exceptional pairs of the other transmitter. To remove a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes both transmitters from the list of inter-technology exceptional pairs of the other transmitter. To add an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set an exceptional pair. Atoll adds the reference transmitter to the list of inter-technology exceptional pairs of the other transmitter.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

943

Atoll User Manual To remove an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the reference transmitter from the list of inter-technology exceptional pairs of the other transmitter. To add an inwards forced or forbidden exceptional pair: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric exceptional pair relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation. If there is no existing exceptional pair relation between the two transmitters, first create a symmetric exceptional pair relation between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation.

To remove an inwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the transmitter from the inter-technology exceptional pairs list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

9.5.3.2

Configuring Importance Factors for Inter-Technology Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. Note: In a GSM project, you must select Neighbours > Configure Importance from the Transmitters folders context menu.

4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when performing automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Inter-Technology Neighbours Automatically" on page 944.

5. Click OK.

9.5.3.3

Allocating Inter-Technology Neighbours Automatically

Atoll can automatically determine handover relations between networks of different technologies, for example, TD-SCDMA and GSM. In this case, inter-technology handovers from TD-SCDMA to GSM may occur when the TD-SCDMA coverage is not continuous. The networks overall coverage is extended by a TD-SCDMA-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. Intertechnology neighbours are stored in the database. To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 5. Click the Inter-technology Neighbours tab. 6. Define the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. 7. Define the maximum number of inter-technology neighbours that can be allocated to a cell in the Max Number of Neighbours box. This value can be either set here for all the cells, or specified for each cell in the Cells table.

944

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 8. Clear the Use Overlapping Coverage check box in order to base the neighbour allocation on distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour allocation on coverage conditions. a. Click the Define button to change the coverage conditions for the cells in the main document. The TD-SCDMA Coverage Conditions dialogue appears. In the TD-SCDMA Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Margin: Enter the margin relative to the pilot signal level of the best server. 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 desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is an LTE document, the LTE Coverage Conditions dialogue appears. In the LTE Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. e. In the % Min. Covered Area box, enter the minimum percentage of the cells coverage area that the neighbours coverage area should also cover to be considered as a neighbour. 9. Under Calculation Options, define the following: CDMA Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers; Atoll will allocate neighbours to cells using the selected carriers. Force co-site as neighbours: Selecting the Force co-site as neighbours check box will include the co-site transmitters/cells in the neighbour list of the TD-SCDMA cell. The check box is automatically selected when the neighbour allocation is based on distance. Force exceptional pairs: Selecting the Force exceptional pairs check box will apply the inter-technology exceptional pair criteria on the neighbours list of the TD-SCDMA cell. Delete existing neighbours: Selecting the Delete existing neighbours check box will delete all existing neighbours in the neighbours list and perform a clean neighbour allocation. If the Delete existing neighbours check box is not selected, Atoll keeps the existing neighbours in the list.

10. Click the Calculate button to start calculations. 11. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the names of the neighbours, the number of neighbours of each cell, and the reason they are included in the neighbours list. The reasons include:

Reason
Exceptional Pair Co-site

Description
Neighbour relation is defined as an exceptional pair. The neighbour is located at the same site as the reference cell.

When
Force exceptional pairs is selected Force co-site as neighbours is selected

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

945

Atoll User Manual

Reason
Distance % of covered area and overlapping area Existing

Description
The neighbour is within the maximum distance from the reference cell. Neighbour relation that fulfils coverage conditions. The neighbour relation existed before running the automatic allocation.

When
Use Coverage Overlapping is not selected Use Coverage Overlapping is selected Reset is not selected

12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

13. Click the Commit button. The allocated neighbours are saved in the Intra-technology Neighbours tab of each cell. 14. Click Close.

9.5.3.4

Displaying Inter-Technology Neighbours on the Map

You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select the neighbour links to display: Outwards Non-Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Neighbours as the type of neighbour links to display. 8. Click the Visual Management button ( ) in the Radio toolbar. Neighbours are now displayed on the map. Neighbours and displayed until you click the Visual Management button again. 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.

946

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

9.5.3.5

Allocating and Deleting Inter-Technology Neighbours per Cell

Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Intertechnology Neighbours table. This section explains the following: "Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 947. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 948. "Allocating and Removing Inter-Technology Neighbours on the Map" on page 949.

Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Cells tab of the transmitters Properties dialogue: 1. On the main documents map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. 6. If desired, you can enter the Maximum Number of Neighbours. 7. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, and sets the Type to "manual." 8. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 9. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

947

Atoll User Manual 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 11. Click OK. In GSM, the inter-technology neighbours tab is available in each transmitters Properties dialogue.

Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table

To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Neighbours from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. To allocate an inter-technology neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Type to "manual." 7. To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 8. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. 9. To take all exceptionnal pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either forced neighbours or forbidden neighbours using the Exceptional Pairs of Inter-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu. ), select a reference cell in the Cell column.

10. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 11. To delete several symmetric neighbour relations: a. Click in the left margin of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. a. Right-click the Neighbours table. The context menu appears. b. Select Delete Link and Symmetric Relation from the context menu. 12. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector).

948

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks

Allocating and Removing Inter-Technology Neighbours on the Map

You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-Technology Neighbours on the Map" on page 946. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. T remove an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the list of inter-technology neighbours of the other transmitter. To add an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. There can be two cases: If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the inter-technology neighbours list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

9.5.3.6

Calculating the Importance of Existing Inter-technology Neighbours

After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone and in the selected folder. To calculate the importance of existing inter-technology neighbours: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. Note: In a GSM project, you must select Neighbours > Calculate Importance from the Transmitters folders context menu.

5. Select the Inter-technology Neighbours tab. 6. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

949

Atoll User Manual 7. Clear the Use Overlapping Coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour importance calculation on coverage conditions. 8. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for cells in the main document. The TD-SCDMA Coverage Conditions dialogue appears. In the TD-SCDMA Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Margin: Enter the margin relative to the pilot signal level of the best server. 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 desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is an LTE document, the LTE Coverage Conditions dialogue appears. In the LTE Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. 9. If you cleared the Use Overlapping Coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. Notes: You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

10. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 5. Cause: The reason Atoll has calculated the value in the Importance column. Co-site Symmetry Coverage

950

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Distance: The distance in kilometres between the reference cell and the neighbour.

11. Click Close. The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

9.5.3.7

Checking the Consistency of the Inter-technology Neighbour Plan

You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab. 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list) and set the value in the Default Max Number text box. Lists > Max Number: Select the Lists > Max Number check box if you want to verify which cells have more than the maximum number of neighbours allowed and set the value in the Default Max Number text box. Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average number of neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: xX; x number of cells out of a total of X have no neighbours (or empty neighbours list). Syntax: |CELL|

Full Lists (default max number = Y): xX; x number of cells out of a total of X have Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > max number (default max number = Y): xX; x number of cells out of a total of X have more than Y number of neighbours listed in their respective neighbours lists. Syntax: Note: |CELL| |NUMBER| |MAX NUMBER|

If the field Maximum number of inter-technology neighbours in the Cells table is empty, the above two checks take into account the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non-symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

951

Atoll User Manual

9.5.4

Creating a TD-SCDMA Sector From a Sector in the Other Network

You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main documents map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new TD-SCDMA transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 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.501: New sector Before and after applying the configuration Note: 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.

9.5.5

Ending Co-planning Mode

once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents. To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select File > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.

9.6

Advanced Configuration
In this section, the following advanced configuration options are explained: "Defining Inter-Carrier Interference" on page 953 "Defining Frequency Bands" on page 953 "The Global Transmitter Parameters" on page 953 "Smart Antenna Modelling" on page 955

952

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks "Defining HSDPA Radio Bearers" on page 961 "Creating Site Equipment" on page 961 "Receiver Equipment" on page 962 "Modelling Shadowing" on page 963 "Maximum System Range" on page 964.

9.6.1

Defining Inter-Carrier Interference

If you want Atoll to take into account the interference between two carriers, you must create a carrier pair with an interference reduction factor. Atoll takes the interference reduction factor into account on both the uplink and the downlink. To define the interference reduction factor between a pair of carriers: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Bands > Interference Reduction Factors from the context menu. The Inter-Carrier Interference Reduction Factor table appears. 4. For each carrier pair for which you want define inter-carrier interference: a. Enter the first carrier of the pair in the 1st Carrier column. b. Enter the second carrier of the pair in the 2nd Carrier column. c. Enter an interference reduction factor in the Reduction Factor (dB) column. When Atoll calculates interference, it subtracts the interference reduction factor from the calculated interference. An interference reduction factor of 0 dB means that the interference between the pair of carriers is the same as between cells using the same carrier 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.

9.6.2

Defining Frequency Bands

To define frequency bands: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Bands from the context menu. The Frequency Bands table appears. 4. In the table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each frequency band, enter: Name: Enter a name for the frequency, for example, "Band 2010." This name will appear in other dialogues when you select a frequency band. Average Frequency (MHz): Enter the average frequency. First Carrier: Enter the number of the first carrier in this frequency band. Last Carrier: Enter the number of the last carrier in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First Carrier field. Important: 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 Bandwidth (MHz): Enter the bandwidth of the frequency band, in MHz.

5. When you have finished adding frequency bands, click Close.

9.6.3

The Global Transmitter Parameters

On the Global Parameters tab of the Transmitters Properties dialogue, you can define network parameters that are used in TD-SCDMA power control simulations. Many parameters are used as default values for all transmitters. This section explains the options available on the Global Parameters tab of the Transmitters Properties dialogue, and explains how to access the tab: "The Options on the Global Parameters Tab" on page 953. "Modifying Global Transmitter Parameters" on page 955.

9.6.3.1

The Options on the Global Parameters Tab

The Global Parameters tab lists a number of parameters that are fixed for the TD-SCDMA technology and cannot be modified. Other parameters on this tab can be modified. The parameters that are fixed include:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

953

Atoll User Manual 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).

The parameters that can be modified include: 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. Atollautomatically converts the power values defined in the cell properties (i.e. DwPCH and other common channel powers) when changing 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 C(I+N). Note: 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 in the Global Parameters tab, 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. 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). Interferences: Under Interferences, 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.

Example: Processing Gain Calculation

The processing gain is the ratio between the chip rate transmitted on the air interface and the data rate of a service. The processing gains on the uplink and downlink are calculated from the uplink and downlink data rates defined in the properties of the service that you have set. The following example shows how the processing gains are calculated for different services. W G P = Processing Gain = ---R Where W is the chip rate for TD-SCDMA, and R is the data rate per timeslot of the service. The chip rate is calculated from the number of data chips per timeslot and the subframe duration: N Data Chips 704 W = -------------------------- = -------------- = 140800 bps 0.005 D Subframe
TS

954

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks Where N Data Chips is the number of data chips per timeslot (704), and D Subframe is the subframe duration (5 ms). Taking the service "Mobile Internet Access" for example, the service data rates per timeslot in uplink and downlink are calculated to be: R
DL TS

384000 64000 UL = ------------------- = 128000 bps and R = --------------- = 64000 bps 3 1

Where 3 and 1 are the number of downlink and uplink timeslots, respectively. The uplink and downlink processing gains are then calculated: GP
DL

140800 140800 UL = ------------------- = 1.1 = 0.414 dB and G P = ------------------- = 2.2 = 3.4242 dB 128000 64000

9.6.3.2

Modifying Global Transmitter Parameters

You can change global transmitter parameters on the Global Parameters tab of the Transmitters Properties dialogue. To change global transmitter parameters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Transmitters Properties dialogue appears. 4. Click the Global Parameters tab. 5. Modify the parameters described in "The Options on the Global Parameters Tab" on page 953. 6. Click OK.

9.6.4

Smart Antenna Modelling

A smart antenna refers to a system of antenna arrays with smart signal processing algorithms that are used to identify the direction of arrival (DOA) of the signal, and use it to calculate beam-forming vectors, to track and locate the antenna beam on the mobile. There are two main types of smart antennas, switched beam smart antennas and adaptive array smart antennas. Switched beam systems have several available fixed beam patterns. A decision is made as to which beam to access, at any given point in time, based upon the requirements of the system. Adaptive arrays allow the antenna to form a beam in any direction of interest while simultaneously nulling interfering signals from other directions. Adaptive beamforming smart antennas create a different antenna beam in the direction of each served mobile in real-time. Atoll TD-SCDMA includes various smart antenna modelling types. The types of smart antenna modelling are described in the following section: "Smart Antenna Equipment" on page 958.

The following section explains how to work with smart antenna equipment in Atoll: "Smart Antenna Equipment" on page 958.

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 914.

9.6.4.1

Types of Smart Antenna Modelling

The smart antenna modelling methods available in Atoll can be divided into two categories. The first category of models, which includes grid of beams (GOB), optimum beamformer, conventional beamformer, adaptive beam, and third-party modelling, requires 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 prediction studies. The second category, which includes the statistical modelling, 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. Atoll TD-SCDMA includes various smart antenna modelling types: "Grid of Beams (GOB) Modelling" on page 955. "Optimum Beamformer Modelling" on page 957. "Conventional Beamformer Modelling" on page 957. "Statistical Modelling" on page 957. "Adaptive Beam Modelling" on page 958. "Third-Party Smart Antenna Modelling" on page 958.

9.6.4.1.1

Grid of Beams (GOB) Modelling

In Atoll TD-SCDMA, a list of beams (antenna patterns) can be used to create grid of beams smart antenna equipment. A GOB in Atoll comprises a list of antenna patterns. Each antenna pattern usually has a different azimuth. All the antenna

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

955

Atoll User Manual patterns are stored in the Antennas table, and can be accessed individually from the Antennas folder. The lists of antennas forming the GOBs are accessible in the Antenna Lists dialogue from the Antennas folders context menu. 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. In downlink, all the 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. In uplink, the interfering signals received at the cell are attenuated according to the antenna pattern of the selected beam. Important: Although the number of beams in a GOB is not limited, calculation times with a large number of beams will be longer. The Atoll TD-SCDMA project template contains sample smart antenna equipment. You should create smart antenna equipment according to the specifications of your equipment supplier, or import them in Atoll, in order to use real data in calculations. The following sections explain how to create and import grids of beams: "Creating a Grid of Beams (GOB)" on page 956. "Adding Antennas to a Grid of Beams (GOB)" on page 956. "Importing a Grid of Beams (GOB)" on page 956. "The Grid of Beams (GOB) Import Format" on page 957.

Creating a Grid of Beams (GOB)

In Atoll, a grid of beams is a list of antennas. A list of antennas can include any number of antennas listed in the Antennas folder. To create an antenna list: 1. Click the Data tab in the Explorer window. 2. Right-click the Antennas folder. The context menu appears. 3. Select Antenna List > Open Table from the context menu. The Antenna Lists table appears. 4. Create a new antenna list in the row marked with the New Row icon ( ).

5. Click the Properties button. The New Antenna List Properties dialogue appears. 6. Select the antennas from the Antennas column to add to the antenna list in each new row. 7. Click OK to close the dialogue. 8. Click Close to close the Antenna Lists table. 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 dialogue.

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. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Antennas folder.

3. Right-click the antenna that you want to add to an antenna list. The context menu appears. 4. Select Add the Antenna to a List from the context menu. The Antenna Addition in a List dialogue appears. 5. Select the antenna list to which you want to add the antenna from the Antenna List. 6. Click OK to add the antenna to the list. You can also add all the antennas in the Antennas folder or a subfolder 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. Click the Data tab in the Explorer window. 2. Right-click the Antennas folder. The context menu appears. 3. Select Antenna List > Import Antennas from a List from the context menu. The Open dialogue appears. 4. Select an Index file to import. 5. Click Open to import the antenna list to Atoll. The Import of antennas from a list dialogue appears. 6. Enter a name for the new antenna list.

956

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 7. Click OK to import the antenna list. Atoll adds the antennas referred to in the index file to the Antennas folder, and adds the new antenna list to the Antenna Lists table.

The Grid of Beams (GOB) Import Format

Atoll supports standard, Planet-like antenna list format for export and import. An index file contains the list of files containing the horizontal antenna patterns and a file containing the vertical antenna pattern. The horizontal antenna pattern files have the following format:

NAME MAKE FREQUENCY H_WIDTH FRONT_TO_BACK GAIN HORIZONTAL DEGREEa

a.The last row is repeated for every degree value.

Name of the antenna Name of manufacturer Operating frequency (in MHz) Horizontal beamwidth (in degrees) Front to back gain ratio (in dB) Antenna gain (in dBi) Horizontal pattern range (in degrees) Attenuation

The vertical antenna pattern file has the following format: Name of the antenna. "<ALL>" can be used to indicate that the vertical pattern is the same for all the files containing the horizontal antenna patterns. Vertical beamwidth (in degrees) Vertical pattern range (in degrees) Attenuation

NAME V_WIDTH VERTICAL DEGREEa

a.The last row is repeated for every degree value.

The fields in bold are obligatory.

9.6.4.1.2

Optimum Beamformer Modelling

The optimum beamformer model works by forming beams in the downlink in the direction of the served mobiles, and cancelling uplink interference from mobiles by using the Minimum Mean Square Error adaptive algorithm. 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.

9.6.4.1.3

Conventional Beamformer Modelling

The conventional beamformer model works by forming beams in the direction of the served mobiles. 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 beams towards each served mobile by calculating the complex weights of the steering vector.

9.6.4.1.4

Statistical Modelling
The statistical modelling approach is designed to provide a fast and reliable coverage and capacity analysis without the need of accurate traffic inputs or Monte Carlo simulations. Statistical modelling is based on the cumulative distribution functions of CI gains for spreading angles. Spreading angles can be defined for each clutter class. For transmitters that have statistical smart antenna equipment assigned, all coverage predictions, including those carried out for traffic timeslots, are calculated using the main antenna. During the calculation of coverage predictions, Atoll reads the spreading angle for each pixel from the corresponding clutter class. Then, for each pixel and spreading angle, Atoll reads the CI gain to take into account in the prediction. The CI gain considered in the coverage prediction is determined using the probability threshold set. The CI gain used corresponds to the cumulative probability, i.e., 100% less the probability threshold entered. For example, for a probability

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

957

Atoll User Manual threshold of 80%, the cumulative probability is 20%. If an exact value of CI gain is not available for the calculated cumulative probability, Atoll performs linear interpolation between the two available values on either side. If no CI gain graph is available, the main antenna is used Monte Carlo simulations and coverage predictions. Two types of default smart antenna equipment using statistical modelling are available in Atoll, ULA4 and ULA8 for 4 and 8 antenna elements, respectively. In the sample equipment, antenna elements have been considered to be half a wavelength apart. The cumulative distribution functions (CDF) of the CI gains are the results of a number of simulations performed for two values of spreading angles (0 and 10) using the Optimum Combining algorithm which maximises the signal to noise and interference ratio (SNIR).

9.6.4.1.5

Adaptive Beam Modelling

The ideal adaptive beam model available in Atoll TD-SCDMA makes use of a selected beam (antenna) pattern. You can create adaptive beam smart antenna equipment and assign it an antenna pattern from the antennas available in the Antennas folder. During Monte Carlo simulations, Atoll orients the selected antenna pattern horizontally towards each mobile generated in order to maximise the received signal. In downlink, all the interfering signals received at each mobile are attenuated according to the antenna pattern of the adaptive beam. If the targeted and interfered users are in the same direction with respect to the beam directed towards the targeted user, the interference will be high. Otherwise, the interfering signals will be attenuated. In uplink, the interfering signals received at the cell are attenuated according to the antenna pattern of the adaptive beam. The results given by adaptive beam modelling correspond to those that would be obtained under ideal conditions. The targeted user will have maximum gain and all the interference will be successfully cancelled.

9.6.4.1.6

Third-Party Smart Antenna Modelling

If you have a third-party smart antenna model available, you can use it in Atoll TD-SCDMA using Atolls smart antenna API. Atolls smart antenna enables you to interface with any external smart antenna module with Atoll. Any external smart antenna models available are listed in the Smart Antenna Models folder of the Modules tab of the Explorer window. Atoll is fully capable of using the features of any external smart antenna model, MMSE-based (Minimum Mean Square Error), EBB-based (Eigen-Beam Beamforming), etc.

9.6.4.2

Smart Antenna Equipment

You can use several types of smart antenna equipment in your TD-SCDMA document based on different smart antenna modelling methods. To create new smart antenna equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Equipment > Smart Antenna Equipment from the context menu. The Smart Antenna Equipment table appears. 4. In the table, create one piece of smart antenna equipment per row. For information on using data tables, see "Working with Data Tables" on page 53. For each piece of smart antenna equipment, enter a Name and some Comments, if you want, and select an Smart Antenna Model. The available smart antenna models are Grid of Beams (GOB), Adaptive Beam, Optimum Beamformer, Conventional Beamformer, Statistical, and any 3rd party models that you might have installed. If you selected Grid of Beams (GOB), Adaptive Beam, Optimum Beamformer, Conventional Beamformer, or Statistical as the Smart Antenna Model, continue with step 5. If you selected any 3rd party model as the Smart Antenna Model, continue with step 9. 5. Click the Properties button. The smart antenna properties dialogue appears. 6. On the General tab of this dialogue, you can modify the Name, Smart Antenna Model, and Comments. 7. Under Smart Antenna Model, click the Parameters button. A dialogue opens with the parameters specific to the selected smart antenna model. If you selected Grid of Beams (GOB) as Smart Antenna Model, the Grid of Beams (GOB) Modelling dialogue appears. a. Select a DL grid of beams, the grid of beams to be used in downlink from the list of grid of beams listed in the Antennas Lists table. For more information on creating grids of beams, see "Grid of Beams (GOB) Modelling" on page 955. b. Select a UL grid of beams, the grid of beams to be used in uplink. If you do not select a UL grid of beams, Atoll uses the main antenna for uplink calculations. c. Under Patterns, you can view the grid of beams separately or combined in the Grid of Beams Properties dialogue. i. Click the Separate button to display the antenna patterns of all the beams separately in the Grid of Beams Properties dialogue.

ii. Click the Combined button to display the combined patterns of all the beams in the Grid of Beams Properties dialogue.

958

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks iii. Click OK to close the Grid of Beams Properties dialogue. Notes: If you opened the smart antenna properties dialogue by clicking the Browse ( ) button on

the Transmitter tab of a transmitters properties dialogue, these patterns will also include the main antenna pattern, if any. 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.

d. Click OK to close the Grid of Beams (GOB) Modelling dialogue. If you selected Statistic as Smart Antenna Model, the Statistic Modelling dialogue appears: a. Select a Probability Threshold (%) used to read the CI gain graphs. For more information on the probability threshold and CI gains, see "Statistical Modelling" on page 957. b. Define a Spreading Angle () per column. c. Click the Browse ( ) button corresponding to the CI Gain Graph for each column. The CI Gain Graph dialogue appears. The CI Gain Graph provides the cumulative probability of each CI value. d. Click OK to close the CI Gain Graph dialogue. e. Click OK to close the Statistical Modelling dialogue. If you selected Adaptive Beam as Smart Antenna Model, the Adaptive Beam Modelling dialogue appears: a. Select a DL adaptive beam, the adaptive beam to be used in downlink from the list of adaptive beams listed in the Antennas Lists table. b. Select a UL adaptive beam, the adaptive beam to be used in uplink. If you do not select a UL adaptive beam, Atoll uses the main antenna for uplink calculations. c. Under Patterns, you can view the adaptive beam pattern separately or combined in the Adaptive Beam Properties dialogue. i. Click the Separate button to display the antenna patterns of all the beams separately in the Adaptive Beam Properties dialogue.

ii. Click the Combined button to display the combined patterns of all the beams in the Adaptive Beam Properties dialogue. iii. Click OK to close the Adaptive Beam Properties dialogue. Notes: If you opened the smart antenna properties dialogue by clicking the Browse ( ) button on

the Transmitter tab of a transmitters properties dialogue, these patterns will also include the main antenna pattern, if any. 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.

d. Click OK to close the Adaptive Beam Modelling dialogue. If you selected Optimum Beamformer as the Smart Antenna Model, the Optimum Beamformer Properties dialogue appears: a. On the General tab, you can modify the name of the smart antenna model. b. On the Properties tab, enter the Number of Elements in the smart antenna array and select a Single Element Pattern to be used in downlink as well as uplink. c. Click OK to close the Optimum Beamformer Properties dialogue. If you selected Conventional Beamformer as the Smart Antenna Model, the Conventional Beamformer Properties dialogue appears: a. On the General tab, you can modify the name of the smart antenna model. b. On the Properties tab, enter the Number of Elements in the smart antenna array and select a Single Element Pattern to be used in downlink as well as uplink. c. Click OK to close the Conventional Beamformer Properties dialogue. 8. Click OK to close the smart antenna properties dialogue. 9. Click Close to close the Smart Antenna Equipment table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

959

Atoll User Manual

Note:

Properties of external third-party smart antenna models may vary. You can access their properties from the Smart Antenna Models folder on the Modules tab of the Explorer window.

9.6.5

Radio Bearers
Bearer services are used by the network for carrying information. In this section, the following are explained: "Defining R99 Radio Bearers" on page 960 "Defining HSDPA Radio Bearers" on page 961

9.6.5.1

Defining R99 Radio Bearers

Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists all the available radio bearers. You can create new R99 radio bearers and modify existing ones by using the R99 Radio Bearer table. Only the following R99 radio bearer parameters are used in predictions: Max TCH power Uplink and downlink TCH RSCP thresholds per mobility Uplink and downlink TCH Eb/Nt thresholds or uplink and downlink TCH C/I thresholds per mobility The type of bearer. Note: You can select whether the TCH thresholds you define are Eb/Nt or C/I thresholds by selecting the corresponding option in the Global Parameters tab of the Transmitters folders properties dialogue. For more information, see "The Global Transmitter Parameters" on page 953.

To create or modify an R99 radio bearer: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select R99 Radio Bearer from the context menu. The R99 Radio Bearer table appears. 5. In the R99 Radio Bearer table, you can enter or modify the following fields: Name: You can modify the name of the bearer. If you are creating a new R99 radio bearer, enter a name in the row marked with the New Row icon ( ). Nominal Uplink Rate (Kbps): Enter or modify the nominal uplink rate in kilobytes per second. Nominal Downlink Rate (Kbps): Enter or modify the nominal downlink rate in kilobytes per second. Type: Select or modify the service type. There are four classes: Conversational, Streaming, Interactive, and Background. This field corresponds to the QoS (quality of service) class or traffic class that the bearer will belong to. 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. Note: 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 Transmitters Properties dialogue. These values have to be manually modified when the option is changed.

UL Processing Gain: Enter or modify the uplink processing gain. DL Processing Gain: Enter or modify the downlink processing gain. Number of Downlink TS: Enter the downlink resource unit consumption in terms of downlink timeslots. Number of Uplink TS: Enter the uplink resource unit consumption in terms of uplink timeslots.

6. When you have finished entering or modifying the R99 radio bearer parameters, double-click the row of the R99 radio bearer to open the bearers Properties dialogue. The Properties dialogue appears. 7. Click the General tab. The options on the General tab are the same as those already described in step 5. The uplink and downlink Spreading Factor is calculated automatically by Atoll according to 3GPP specifications. The coding factor is only used to evaluate the spreading factor, i.e. the number of OVSF codes required by the service. 8. Under Resource Units, click the Browse button ( ) to the right of the timeslot field to access the Resource Unit Consumption dialogue. In the Resource Unit Consumption dialogue, you can enter how many OVSF codes of each length can be 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 "TD-SCDMA Network Capacity" on page 901. For information on the dynamic channel allocation, see "The Monte Carlo Simulation Algorithm" on page 914.

960

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks DL: Enter or modify the number of downlink traffic timeslots for the service. UL: Enter or modify the number of uplink traffic timeslots for the service.

9. Click the Required Thresholds tab. On the Required Thresholds 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 and reception equipment; these parameters must be defined for each possible combination of mobility type and reception equipment. Using Transmission and Reception diversity results in a quality gain on received downlink and uplink EbNt or CI. In Atoll, this is modelled by reducing the downlink and uplink EbNt or CI requirements. Therefore, in addition to downlink and uplink EbNt or CI requirements, you can specify gains on received downlink and uplink EbNt or CI for each possible diversity configuration. Atoll considers them when transmission and reception diversity configurations are assigned to transmitters. Mobility: Select a mobility type from the list. Reception Equipment: Select a type of reception equipment from the list. You can create a new type of reception equipment by opening the Reception Equipment table. To open the Reception Equipment table, right-click the Terminals folder in the TD-SCDMA Parameters folder on the Data tab and select Reception Equipment from the context menu. Uplink TCH Eb/Nt Threshold (dB) or Uplink TCH C/I Threshold (dB): Enter or modify the uplink EbNt or C/I threshold. Uplink TCH RSCP Threshold (dBm): Enter or modify the uplink RSCP threshold for the traffic channel. Uplink 2RX Diversity Gain (dB): Enter or modify the two-receiver uplink diversity gain in dB. Uplink 4RX Diversity Gain (dB): Enter or modify the four-receiver uplink diversity gain in dB. Downlink TCH Eb/Nt Threshold (dB) or Downlink TCH C/I Threshold (dB): Enter or modify the downlink EbNt or C/I threshold. Downlink TCH RSCP Threshold (dBm): Enter or modify the downlink RSCP threshold for the traffic channel. Downlink Open Loop Diversity Gain (dB): Enter or modify the downlink open loop diversity gain in dB. Downlink Closed Loop Diversity Gain (dB): Enter or modify the downlink closed loop diversity gain in dB.

10. Click OK to save your changes and close the dialogue.

9.6.5.2

Defining HSDPA Radio Bearers

In each cell, the scheduler selects the HSDPA resource per UE and per TTI (Transmission Time Interval). This HSDPA resource is called a TFRC (Transport Format Resource Combination) and is the set of parameters such as the transport format, the modulation scheme, and the number of used HS-PDSCH channels. In Atoll, the TFRC are referred to as HSDPA radio bearers. During a simulation, and for the HSDPA coverage prediction, Atoll selects a suitable HSDPA radio bearer and uses its RLC peak rate. The HSDPA radio bearer selection is based on UE capabilities (maximum number of HS-PDSCH channels, transport block size, and whether the bearer uses 16 QAM modulation), cell capabilities (maximum number of HSPDSCH channels), and reported CQI. The HSDPA Radio Bearer table lists the available HSDPA radio bearers. You can create new HSDPA radio bearers and modify existing ones by using the HSDPA Radio Bearer table. To open the HSDPA Radio Bearer table: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select HSDPA Radio Bearers from the context menu. The HSDPA Radio Bearer table appears with the following information: Radio Bearer Index: The bearer index number. Transport Block Size (Bits): The transport block size in bits. Number of HS-PDSCH Channels Used per TS: The number of HS-PDSCH channels used per used timeslot. 16QAM Modulation Used: The check box is selected if the HSDPA radio bearer uses 16QAM modulation. If this option is not selected, Atoll assumes that QPSK modulation is used. RLC Peak Rate (bps): The RLC peak rate represents the peak rate without coding (redundancy, overhead, addressing, etc.). Number of Timeslots Used: The number of timeslots used by the HSDPA radio bearer. HSDPA UE Category: The HSDPA user equipment category that supports the HSDPA radio bearer. For more information on HSDPA UE categories, see "Creating or Modifying HSDPA User Equipment Categories" on page 963.

9.6.6

Creating Site Equipment

To create a new piece of TD-SCDMA site equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Sites folder. The context menu appears. 3. Select Equipment > Open Table from the context menu. The Site Equipment table appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

961

Atoll User Manual 4. In the Equipment table, each row describes a piece of equipment. For information on working with data tables, see "Working with Data Tables" on page 53. For the new piece of TD-SCDMA equipment you are creating, enter the following: 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. In case MCJD is not supported by equipment, enter 0 as value. ) to close the table.

5. Click the Close button (

9.6.7

Receiver Equipment
Mobile terminals have different categories, reception characteristics, and behaviour under different speeds. In Atoll these characteristics are modelled by reception equipment and HSDPA UE categories. In this section the following are explained: "Setting Receiver Height" on page 962. "Creating or Modifying Reception Equipment" on page 962. "Creating or Modifying HSDPA User Equipment Categories" on page 963.

9.6.7.1

Setting Receiver Height

When you make TD-SCDMA coverage predictions, you can define the height of the receiver. To define the height of the receiver: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Receiver tab. 5. Enter a receiver Height. This value will be used when calculating TD-SCDMA coverage predictions and point analyses. 6. Click OK.

9.6.7.2

Creating or Modifying Reception Equipment

In Atoll, reception equipment is used when you create a terminal. The graphs defined for each reception equipment entry are used for selecting R99 and HSDPA radio bearers. To create or modify reception equipment: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select Reception Equipment from the context menu. The Reception Equipment table appears. 5. Double-click the reception equipment type you want to modify. The reception equipment types Properties dialogue appears. Note: You can create a new reception equipment type by entering a name in the row marked with the New Row icon ( 6. Click the HSDPA Bearer Selection tab. 7. 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. The HSDPA bearer selection thresholds are used in simulations and in the HSDPA coverage prediction to model fast link adaptation (i.e., selection of the HSDPA bearer). The supplier RRM (radio resource management) strategy can be taken into account using the HSDPA bearer selection thresholds, for example: You can define several pieces of reception equipment with separate thresholds for each. You can reserve low bearer indexes for poor-performance reception equipment and higher bearer indexes for high-performance equipment. You can specify bearer selection thresholds for each mobility. You can reserve low bearer indexes for high speeds and higher bearer indexes for low speeds. ) and pressing ENTER.

962

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 9: TD-SCDMA Networks 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.

8. Click OK to close the reception equipment types Properties dialogue.

9.6.7.3

Creating or Modifying HSDPA User Equipment Categories

HSDPA user equipment capabilities are standardised into 15 different categories according to 3GPP specifications. To edit an HSDPA user equipment category: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select HSDPA User Equipment Categories from the context menu. The HSDPA User Equipment Categories table appears. 5. The HSDPA User Equipment Categories table has the following columns: Category: The number identifying 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. 16QAM Modulation Used: Select the check box if the category supports 16QAM modulation. If 16QAM modulation is not selected, QPSK is used. Max Number of HS-PDSCH TS per TTI: The maximum number of HS-PDSCH timeslots allowed within a TTI (transmission time interval).

9.6.8

Modelling Shadowing
Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value with a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be better and in 50% of the measured cases, the result will be worse. Atoll uses a model standard deviation with the defined cell edge coverage probability to model the effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. 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 TD-SCDMA projects, the model standard deviation is used to calculate shadowing margins on signal levels. You can also calculate shadowing margins on EbNt values. For information on setting the model standard deviation and the EbNt standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 121. Shadowing can be taken into consideration when Atoll calculates the signal level and EbNt for: A point analysis (see "Making a Point Analysis to Study the Profile" on page 834). A coverage prediction (see "Studying Signal Level Coverage" on page 835).

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" on page 963.

9.6.8.1

Displaying the Shadowing Margins

To display the shadowing margins and macro-diversity gain per clutter class: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialogue appears (see Figure 9.502). 4. You can set the following parameters: Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macro-diversity 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. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

963

Atoll User Manual 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

5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.

Figure 9.502: The Shadowing Margins dialogue

9.6.9

Maximum System Range

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. You can set the maximum range of your TD-SCDMA system through the Properties dialogue of the Predictions folder. To set the maximum range of the system: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the System tab. On the System tab, you can set the following parameters: Max Range: 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.

5. Click OK. 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 is the distance after which the uplink and downlink pilot timeslots could be unsynchronised. The maximum system range is 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: 75 s 3 10 m/s R System = ---------------------------------------------------- = 11250 m 2
8

964

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10
WiMAX BWA Networks

RF Planning & Optimisation Software

Atoll

Chapter 10: WiMAX BWA Networks

10

WiMAX BWA Networks

WiMAX (Wireless Interoperability for Microwave Access) refers to a group of broadband wireless access (BWA) standards which use OFDM (Orthogonal Frequency Division Multiplexing) and SOFDMA (Scalable Orthogonal Frequency Division Multiple Access) technologies. The WiMAX air interface is described in the IEEE 802.16d and the IEEE 802.16e standards. The 802.16d standard is the complete specification for fixed broadband wireless access networks using OFDM and the 802.16e specifications describe mobile broadband wireless access networks which use SOFDMA and support handovers and user terminal speeds of up to 100 km/hr. Atoll enables you to design IEEE 802.16d and IEEE 802.16e broadband wireless access networks. Two separate document templates, named WiMAX 802.16d and WiMAX 802.16e, are available for designing and planning these networks. Atoll can predict radio coverage, manage mobile and fixed subscriber data, and evaluate network capacity. Atoll WiMAX also supports smart antennas. Atoll enables you to model fixed and mobile users in WiMAX environments. The data input corresponding to fixed subscribers, which is an important requirement of fixed wireless access networks, is modelled using a subscriber database integrated into the module. 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 or subscriber data. Atoll uses these realistic user distributions as input for the simulations. Coverage predictions can be created to study the following parameters: The signal level received from cells The effective preamble signal level The effective downlink and uplink traffic signal levels The preamble and traffic carrier-to-interference-and-noise ratio The radio bearer coverage The channel throughput and cell capacity per pixel, and the aggregate throughput per cell

Coverage predictions that depend on the networks 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 EGPRS, CDMA2000 1xRTT 1xEV-DO, UMTS HSPA, and LTE networks can be planned in the same Atoll session.

Tip:

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 1166. This will help you get accustomed to the terminology used in Atoll.

10.1

Designing a WiMAX Network

Figure 10.503 depicts the process of creating and planning a WiMAX BWA network. The steps involved in planning a WiMAX network are described below. The numbers refer to Figure 10.503. 1. Open an existing radio-planning document or create a new one ( 1 ). You can open an existing Atoll document by selecting File > Open. Creating a new Atoll document is explained in Chapter 2: Starting an Atoll Project.

2. Configure the network by adding network elements and changing parameters ( 2 ). You can add and modify the following elements of base stations: "Creating or Modifying a Site" on page 975. "Creating or Modifying a Transmitter" on page 975. "Creating or Modifying a Cell" on page 976.

You can also add base stations using a base station template (see "Placing a New Base Station Using a Station Template" on page 976). 3. Carry out basic coverage predictions ( 3 ). "Making a Point Analysis to Study the Profile" on page 984. "Studying Signal Level Coverage" on page 985 and "Signal Level Coverage Predictions" on page 993.

4. Allocate neighbours ( 4 ). "Planning Neighbours" on page 1022.

5. Allocate frequencies ( 5 ). "Planning Frequencies" on page 1033.

6. Allocate preamble indexes ( 6 ).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

967

Atoll User Manual "Planning Preamble Indexes" on page 1037.

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 and subscriber lists ( 7a , 7b , and 7c ) (see "Studying Network Capacity" on page 1041). You can define cell load conditions manually either on the Cells tab of each transmitters Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 976) ( 7d ). 8. Make WiMAX-specific signal quality coverage predictions using the defined cell load conditions ( 8 ). "WiMAX Coverage Predictions" on page 1006.

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

7c 7b

7d

10

Figure 10.503: Planning a WiMAX BWA network - workflow

10.2

Planning and Optimising WiMAX Base Stations

As described in Chapter 2: Starting an Atoll Project, you can start an Atoll document from a template, with no base stations, or from a database with a set of base stations. As you work on your Atoll document, you will still need to create base stations and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such as the TMA, feeder cables, etc. In a WiMAX 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. 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.

968

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 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 studies that depend on network load, such as C/(I+N), WiMAX radio bearer, and throughput coverage predictions. In this section, the following are explained: "Creating a WiMAX Base Station" on page 969. "Creating a Group of Base Stations" on page 982. "Modifying Sites and Transmitters Directly on the Map" on page 983. "Display Tips for Base Stations" on page 983. "Creating a Multi-Band WiMAX Network" on page 983. "Setting the Working Area of an Atoll Document" on page 983. "Studying a Single Base Station" on page 984. "Studying Base Stations" on page 987. "Planning Neighbours" on page 1022. "Planning Frequencies" on page 1033. "Planning Preamble Indexes" on page 1037.

10.2.1

Creating a WiMAX Base Station

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

10.2.1.1

Definition of a Base Station

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

10.2.1.1.1

Site Description
The parameters of a site can be found in the sites Properties dialogue. The Properties dialogue has two tabs: The General tab (see Figure 10.504): 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.

Tip:

While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.

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 wish. If an altitude is specified here, Atoll will use this value for calculations. Comments: You can enter comments in this field if you wish.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

969

Atoll User Manual

Figure 10.504: New Site dialogue

10.2.1.1.2

Transmitter Description
The parameters of a transmitter can be found in the transmitters Properties dialogue. When you create a transmitter, the Properties dialogue has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Properties dialogue has three additional tabs: the Cells tab (see "Cell Description" on page 972), the Propagation tab (see Chapter 5: Managing Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 32). The General tab: Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names transmitters, see the Administrator Manual. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site on which the transmitter will be located. For information on the site Properties dialogue, see "Site Description" on page 969. You can click the New button to create a new site on which the transmitter will be located. Under Antenna Position, you can modify the position of the antennas (main and secondary): Relative to Site: Select Relative to Site if you want 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 Coordinates if you want to enter the coordinates of the antenna positions, and enter the x-axis and y-axis coordinates, X and Y, respectively.

970

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks The Transmitter tab (see Figure 10.505):

Figure 10.505: Transmitter dialogue - Transmitter tab Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder of the Data tab. Note: 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 Extra-Network (Interferer Only). No coverage for an Interferer Only transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simulations. This feature 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 1166.

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 using the Equipment Specifications dialogue which appears when you click the Equipment button. On the Equipment Specifications dialogue (see Figure 10.506), the equipment you select and the gains and losses you define are used to initialise total transmitter losses in the uplink and downlink: 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 147. 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 147. BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defining BTS Equipment" on page 148. Feeder Length: You can enter the feeder length at transmission and reception. Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value you enter must be positive.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

971

Atoll User Manual

Figure 10.506: The Equipment Specifications dialogue 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 Total Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total Losses at transmission and reception and the real Total Noise Figure at reception if you wish. 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. Power Combining Gain: The 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. The other fields, Azimuth, Mechanical Downtilt, and Additional Electrical Downtilt, display additional antenna parameters. The mechanical and additional electrical downtilts defined for the main antenna are also used for the calculations using the smart antenna equipment. Smart Antenna: Under Smart Antenna, the available 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 1152. 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 Systems" on page 1153. 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. For information on working with data tables, see "Working with Data Tables" on page 53. 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 cell (or permutation zones in WiMAX 802.16e) does not support AAS. If there is smart antenna equipment assigned to the transmitter and the cell (or permutation zones in WiMAX 802.16e) supports AAS, traffic data is transmitted and received using the smart antenna, whereas the preamble is transmitted using the main antenna.

10.2.1.1.3

Cell Description
In Atoll, a cell is defined as an RF channel, with all its characteristics, on a transmitter; the cell is the mechanism by which you can configure a multi-carrier WiMAX network.

972

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks When you create a transmitter, Atoll reminds you to create a cell for the transmitter. The following explains the parameters of a WiMAX cell. As you create a cell, Atoll calculates appropriate values for some fields based on the information you have entered. You can, if you wish, modify these values. The properties of a WiMAX cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned. The Cells tab has the following options: 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. BSID: The Base Station ID. Active: If this cell is to be active, you must select the Active check box. Layer: The number of the coverage layer to which the cell belongs. This value is automatically assigned when you create a new cell, but you can modify it afterwards. The layer is used during calculations to select the serving cell. For more information on the different cell layer selection options, see "The Global Transmitter Parameters" on page 1140. Frequency Band: The cells frequency band from the Frequency Band list. Channel Number: The number of the channel from the list of available channels. Channel Allocation Status: The status of the channel allocated to the cell: Not Allocated: The channel has not been allocated automatically or manually. The AFP considers that a Not Allocated channel can be modified. Allocated: The channel has been allocated automatically or manually. The AFP considers that an Allocated preamble index can be modified but it is not modified unless absolutely necessary. Locked: The channel has been allocated automatically or manually. The AFP considers that a Locked channel is not modifiable.

Min Reuse Distance: The minimum reuse distance after which the channel assigned to this cell can be assigned to another cell by the AFP. The reuse distance is also used by the automatic preamble index allocation in 802.16e. The cells preamble index can be allocated to another cell outside this reuse distance without any cost. 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 power of cell increases 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 power combination gain.

WiMAX Equipment: You can select the cells WiMAX equipment from the WiMAX Equipment list. For more information, see "Defining WiMAX Equipment" on page 1146. 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 1148. Max Number of Users: The maximum number of simultaneous users supported by the cell. 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. AMS & MU-MIMO Threshold (dB): For AMS, it is the preamble C/N threshold 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 using MU-MIMO. For more information on Adaptive MIMO switching, see "Multiple Input Multiple Output Systems" on page 1153. Traffic Load (DL) (%): The downlink traffic load percentage. By default, the downlink traffic load is set to 100%. 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 (UL) (%): The uplink traffic load percentage. By default, the uplink traffic load is set to 100%. 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. UL Noise Rise (dB): The uplink noise rise in dB. By default, the uplink noise rise is set to 0 dB. This is the global value of uplink noise rise including the inter-technology uplink noise rise. 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 AAS simulation results diagrams. AAS Simulation Results: 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

973

Atoll User Manual 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. 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. Inter-technology 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 the simulation. 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 1155. Inter-technology 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 interference-based calculations involving this cell. For more information on inter-technology interference, see "Modelling Inter-Technology Interference" on page 1155.

The following parameters are only available in WiMAX 802.16d documents. Diversity Support (DL): The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, or AMS) supported by the cell in downlink. You can not select more than one type of MIMO technique (STTD/MRC, SU-MIMO, or AMS) at a time. Diversity Support (UL): The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, AMS, or MU-MIMO) supported by the cell in uplink. You can not select more than one type of MIMO technique (STTD/MRC, SU-MIMO, MU-MIMO, or AMS) at a time. Specific calculations will be performed (gains will be applied) for terminals supporting AAS and MIMO. A cell that only supports None does not have any antenna diversity mechanism, and all terminal types can connect to this cell. A cell 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 cell that does not support None. The following parameters are only available in WiMAX 802.16e documents: 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 and sampling factor, and the DL:UL ratio, frame duration, and cyclic prefix defined in the global transmitter parameters. For more information on the global parameters, see "The Global Transmitter Parameters" on page 1140. Preamble Index: A preamble index for 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 IDCell (DL_PermBase for the first permutation zone of the frame) which is referred to as Cell PermBase in Atoll to avoid ambiguity with cell ID which is the name of a cell in Atoll. Segment Number: The segment number corresponding to the current preamble index. This value is determined automatically from the preamble index. 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 current preamble index has neither been allocated automatically nor manually. The automatic preamble index allocation algorithm considers that a Not Allocated preamble index is modifiable. - Allocated: The current preamble index has been allocated automatically or manually. The automatic preamble index allocation algorithm considers that an Allocated preamble index is modifiable but it is not modified by the algorithm unless absolutely necessary. - Locked: The current preamble index has been allocated automatically or manually. The automatic preamble index allocation algorithm considers that a Locked preamble index is not modifiable. - Segment Locked: The segment number corresponding to the current preamble index is locked. The automatic preamble index allocation algorithm considers that a Segment Locked preamble index may be modifiable, but can only be replaced with a preamble index corresponding to the current segment number of the cell. Frame Configuration: The cells frame configuration selected from the list. For more information on frame configurations, see "Defining Frame Configurations" on page 1143. 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 non-segmented part. You can set the value of segmentation usage manually or store a calculated value from simulation results. To see examples of how to setup cells with and without segmentation, and how to setup cells with PUSC, FUSC, and permutation zones of other subchannel allocation modes, see "Tips and Tricks" on page 1157. Max Number of Intra-technology Neighbours: The maximum number of neighbours from within the same Atoll document that the cell can have. Max Number of Inter-technology Neighbours: The maximum number of neighbours from other technology documents that the cell can have. Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neighbours by clicking the Browse button ( on page 1022. ). For information on defining neighbours, see "Planning Neighbours"

974

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Tip:

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.

10.2.1.2

Creating or Modifying a Base Station Element

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: "Creating or Modifying a Site" on page 975 "Creating or Modifying a Transmitter" on page 975 "Creating or Modifying a Cell" on page 976

10.2.1.2.1

Creating or Modifying a Site

You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 969, through the sites Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create or modify a site: 1. If you are creating a new site: a. Click the Data tab in the Explorer window. b. Right-click the Sites folder. The context menu appears. c. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 10.504 on page 970). 2. If you are modifying the properties of an existing site: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Sites folder.

c. Right-click the site you want to modify. The context menu appears. d. Select Properties from the context menu. The sites Properties dialogue appears. 3. Modify the parameters described in "Site Description" on page 969. 4. Click OK.

10.2.1.2.2

Creating or Modifying a Transmitter

You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 970, through the transmitters Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create or modify a transmitter: 1. If you are creating a new transmitter: a. Click the Data tab in the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 10.505). 2. If you are modifying the properties of an existing transmitter: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Transmitters folder.

c. Right-click the transmitter you want to modify. The context menu appears. d. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Modify the parameters described in "Transmitter Description" on page 970. 4. 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 976.

Tips: 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 right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

975

Atoll User Manual

10.2.1.2.3

Creating or Modifying a Cell

You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Description" on page 972, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Description" on page 972. 7. Click OK.

Tips: If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 59), or import data into the table (see "Importing Tables from Text Files" on page 63). If you want to add a cell to an existing transmitter on the map, you can add the cell by rightclicking the transmitter and selecting New Cell from the context menu.

10.2.1.3

Placing a New Base Station Using a Station Template

In Atoll, a base station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing base stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio toolbar, select a template from the list.

2. Click the New Transmitter or Station button (

) in the Radio toolbar.

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.

Tips:

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 38. 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.

You can also place a series of base stations using a station template. You do this by defining an area on the map where you want to place the base stations. Atoll calculates the placement of each base station according to the defined hexag-

976

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks onal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 977. To place a series of base stations within a defined area: 1. In the Radio toolbar, select a template from the list. 2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of base stations created from the same station template.

Note:

If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this template is not defined. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 977.

3. Draw a zone delimiting the area where you want to place the series of base stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as sites and transmitters are also created and placed into their respective folders. You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for example, another antenna to a transmitter.

Placing a Station on an Existing Site

When you place a new station using a station template as explained in "Placing a New Base Station Using a Station Template" on page 976, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place a base station on an existing site: 1. On the Data tab, clear the display check box beside the Hexagonal Design folder. 2. In the Radio toolbar, select a template from the list. 3. Click the New Transmitter or Station button ( ) in the Radio toolbar.

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.

10.2.1.4

Managing Station Templates

Atoll comes with WiMAX station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio toolbar (see Figure 10.507).

Figure 10.507: The Radio toolbar In this section, the following are explained: "Creating or Modifying a Station Template" on page 977 "Copying Data from One Station Template to Another" on page 980 "Modifying a Field in a Station Template" on page 980 "Deleting a Station Template" on page 981.

10.2.1.4.1

Creating or Modifying a Station Template

When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. As well, you can modify the properties of any station template. To create or modify a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. You can now create a new station template or modify an existing one: To create a new station template: Under Station Templates, select the station template that most closely resembles the station template you want to create and click Add. The Properties dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

977

Atoll User Manual To modify an existing station template: Under Station Templates, select the station template whose properties you want to modify and click Properties. The Properties dialogue appears.

4. Click the General tab of the Properties dialogue. In this tab (see Figure 10.508), you can modify the following: 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 the current network or to another network. Under Antennas, 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. Under Smart Antenna, you can select the smart antenna Equipment used by the transmitter, and under Number of MIMO Antennas, you can enter the number of antennas used for Transmission and for Reception for MIMO. Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

Figure 10.508: Station Template Properties dialogue General tab 5. Click the Transmitter tab. In this tab (see Figure 10.509), if the Active check box is selected, you can modify the following: Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station (BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 970. The information in the computed Total Losses in transmission and reception boxes is calculated from the information you entered in the Equipment Specifications dialogue (see Figure 10.506 on page 972). 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 modify the real Total Losses at transmission and reception if you wish. Any value you enter must be positive. The information in the computed BTS Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if you wish. Any value you enter must be positive.

978

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.509: Station Template Properties dialogue Transmitter tab 6. Click the WiMAX tab. In this tab (see Figure 10.510), you can modify the following: Under Powers, you can 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. You can assign channel and preamble index (WiMAX 802.16e) per cell per sector, by clicking the Cell Definition per Sector button. The Cell Definition per Sector dialogue appears. i. Select the Sector for which you want to define cell parameters, i.e., channel number and preamble index (WiMAX 802.16e).

ii. Enter the Number of Cell Layers that the selected sector will have. The number of rows in the grid below depends on the number of cell layers that you enter. iii. In the cell layer - channel/preamble index (WiMAX 802.16e) grid, assign a channel number and a preamble index (WiMAX 802.16e) to each cell. iv. Carry out the steps above to assign a channel number and preamble index to each sector. v. Click OK. Frequency Band, Channel Allocation Status, Preamble Index Status (WiMAX 802.16e), Min Reuse Distance, WiMAX Equipment, Scheduler, Max Number of Users, Frame Configuration (WiMAX 802.16e), Preamble C/N Threshold, AMS & MU-MIMO Threshold (WiMAX 802.16e), and the default MU-MIMO Capacity Gain (WiMAX 802.16e). Under Antenna Diversity in WiMAX 802.16d documents, you can select the Diversity Support in downlink and in uplink. You cannot select more than one type of MIMO technique (STTD/MRC, SU-MIMO, MU-MIMO, or AMS) at a time. You can also enter the AMS & MU-MIMO Threshold and the default MU-MIMO Capacity Gain. Under Default Loads, you can 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. You can also enter the DL Segmentation Usage in WiMAX 802.16e. Under Inter-technology Interference, you can set the DL Noise Rise and the UL Noise Rise. For more information on inter-technology interference, see "Modelling Inter-Technology Interference" on page 1155.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

979

Atoll User Manual

Figure 10.510: Station Template Properties dialogue WiMAX tab (WiMAX 802.16e) 7. Click the Neighbours tab. In this tab (see Figure 10.511), you can modify the following: Under Max Number of Neighbours in WiMAX 802.16e documents, you can set the maximum numbers of Intra-technology and Inter-technology neighbours.

Figure 10.511: Station Template Properties dialogue Neighbours tab (WiMAX 802.16e) 8. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Sites table, or if you have defined an additional field in the Station Template Properties dialogue. 9. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.

10.2.1.4.2

Copying Data from One Station Template to Another

You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Station Templates from the context menu. The Station Templates table appears. 4. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy from and paste them into the row corresponding to the station template you want to modify.

10.2.1.4.3

Modifying a Field in a Station Template

To modify a field in a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Select the template in the Available Templates list.

980

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 4. Click the Fields button. 5. In the dialogue that appears, you have the following options: Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Types Data Table" on page 54) for it to appear as an option in the station template properties. To add a new field: i. Click the Add button. The Field Definition dialogue appears.

ii. Enter a Name for the new field. iii. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/ Time, and Currency. If you choose text, you can also set the field Size (in characters), and create a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER after each one. iv. Enter, if desired, a Default value for the new field. v. Click OK to close the Field Definition dialogue and save your changes. Delete: To delete a user-defined field: i. Select the user-defined field you want to delete.

ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you close the dialogue. Properties: To modify the properties of a user-defined field: i. Select the user-defined field you want to modify.

ii. Click the Properties button. The Field Definition dialogue appears. iii. Modify any of the properties as desired. iv. Click OK to close the Field Definition dialogue and save your changes. 6. Click OK.

10.2.1.4.4

Deleting a Station Template

To delete a station template: 1. In the Radio toolbar, click the arrow to the right of the list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Under Station Templates, select the station template you want to delete and click Delete. The template is deleted. 4. Click OK.

10.2.1.5

Duplicates of an Existing Base Station

You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same site, transmitter, and cell parameter values as the original one. Duplicating a base station allows you to: Quickly create a new base station with the same settings as 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 base stations that have the same characteristics.

To duplicate an existing base station: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Sites folder.

3. Right-click the site you want to duplicate. The context menu appears. 4. From the context menu, select one of the following: Select Duplicate > 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. 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.

You can now place the new base station on the map using the mouse. 5. In the map window, move the pointer over the map to where you would like to place the new base station. The exact coordinates of the pointers current location are visible in the Status bar.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

981

Atoll User Manual

Figure 10.512: Placing a new base station

Tips:

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 38. If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact coordinates, allowing you to verify that the location is correct.

6. Click to place the duplicate base station. A new base station is placed on the map. The site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original base station, preceded by "Copy of." The site, transmitters, and cells of the duplicate base station have the same settings as those of the original base station. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate station. For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 969.

10.2.2

Creating a Group of Base Stations

You can create base stations individually as explained in "Creating a WiMAX Base Station" on page 969, or you can create one or several base stations by using station templates as explained in "Placing a New Base Station Using a Station Template" on page 976. However, if you have a large project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations. Note: 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 96.

You can import base station data in the following ways: Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. Important: The table you copy 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 59. 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" on page 61. For information on importing table data, see "Importing Tables from Text Files" on page 63. Note: You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio toolbar. For information, see "Placing a New Base Station Using a Station Template" on page 976.

982

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.2.3

Modifying Sites and Transmitters Directly on the Map

In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu on the Data tab of the Explorer window. However, in a complex radio-planning project, it can be difficult to find the data object in the Data tab, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. If there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: "Selecting One of Several Transmitters" on page 31 "Moving a Site Using the Mouse" on page 31 "Moving a Site to a Higher Location" on page 31 "Changing the Azimuth of the Antenna Using the Mouse" on page 31 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32.

10.2.4

Display Tips for Base Stations

Atoll allows to you to display information about base stations in a number of ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object types data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information in the label will make it harder to distinguish the information you are looking for. For information on defining the label, see "Defining the Object Type Label" on page 35. Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip 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 every field in that object types data table, including from fields that you add. For information on defining the tool tips, see "Defining the Object Type Tip Text" on page 36. 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 "Defining the Display Type" on page 33. 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 "Defining the Display Type" on page 33.

10.2.5

Creating a Multi-Band WiMAX Network

In Atoll, you can model a multi-band WiMAX network, for example, a network consisting of 3.3 GHz, 5.8 GHz, and 2.5 GHz cells, in one document. Creating a multi-band WiMAX network consists of the following steps: 1. Defining the frequency bands in the document (see "Defining Frequency Bands" on page 1139). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Managing Calculations in Atoll). 3. Assigning a frequency band to each cell and a relevant propagation model to each transmitter (see "Creating or Modifying a Cell" on page 976 and "Creating or Modifying a Transmitter" on page 975).

10.2.6

Setting the Working Area of an Atoll Document

When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the base stations that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of base stations covered by a coverage prediction, each with its own advantages: Filtering the desired base stations You can simplify the selection of base stations to be studied by using a filter. You can filter base stations according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 84. This enables you to keep only the base stations with the characteristics you want for your calculations. The filtering zone is taken into account whether or not it is visible.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

983

Atoll User Manual For information on filtering, see "Filtering Data" on page 74. Setting a computation zone Drawing a computation zone to encompass the base stations to be studied limits the number of base stations to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated calculations in order to see the effects of small changes in the base station configuration, the savings in time may be considerable. Limiting the number of base stations by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot zones. The computation zone defines the area where Atoll computes path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus zone or hot spot zones are the areas taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 992. You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.

10.2.7

Studying a Single Base Station

As you create a base station, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of base stations can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the base station you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of base stations once you have optimised the settings for each individual base station. Before studying a base station, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes propagation losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Any coverage prediction you make on a base station uses the propagation model to calculate its results. In this section, the following are explained: "Making a Point Analysis to Study the Profile" on page 984. "Studying Signal Level Coverage" on page 985.

10.2.7.1

Making a Point Analysis to Study the Profile

In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a user. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 990. You can make a point analysis to: study the reception in real time along a profile between a reference transmitter and a WiMAX user, study the interference along a profile between a reference transmitter and a user, and evaluate the signal levels coming from the surrounding transmitters at a given point (using existing path loss matrices).

To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Profile tab. The profile analysis appears in the Profile tab of the Point Analysis Tool window. 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, with a green line indicating the line of sight (LOS). Atoll displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional attenuations peaks. The total attenuation is displayed above the main peak.

984

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks The results of the analysis are displayed at the top of the Profile tab: The received signal strength from the selected transmitter for the cell with the highest preamble power The propagation model used The shadowing margin and the cell edge coverage probability used for calculating it The distance between the transmitter and the receiver.

You can change the following options at the top of the Profile tab: Transmitter: Select the transmitter from the list. Geographic Profile: Select the Geographic Profile check box if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses. Snap to Subscribers: Select the Snap to Subscribers check box if you want to study the profile between a subscriber and the transmitter. The receiver snaps to the nearest subscriber when you move it. Atoll displays the profile between the transmitter and the receiver with clutter heights, giving terminal and antenna gains and losses. An ellipsoid indicating the Fresnel zone is also displayed. The displayed profile is between the selected transmitter and the subscriber; not between the subscriber and its serving transmitter.

Note:

5. Right-click the Profile tab to choose one of the following commands from the context menu: Properties: Select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. You can: Change the X and Y coordinates to change the present position of the receiver. If Snap to Subscribers is selected on the Profile tab, define the Receiver Orientation: "To Selected Server" or "To Subscriber Server." - Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Select Signal Level, Path loss, or Total losses from the Result Type list. - You can select the Indoor Coverage check box to add indoor losses. Link Budget: Select Link Budget to display a dialogue with the link budget. Model Details: Select Model Details to display a text document with details on the displayed profile analysis. Model details are only available for the Standard Propagation Model. Displays data, including received signal, shadowing margin, cell edge coverage probability, propagation model used, and transmitter-receiver distance.

You can select a different transmitter.

Fresnel ellipsoid

Line of sight

Attenuation with diffraction

Figure 10.513: Point Analysis Tool - Profile tab 6. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.

10.2.7.2

Studying Signal Level Coverage

As you are building your radio-planning project, you might want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single base station. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. For a transmitter with more than one cell, the signal level is calculated for the cell with the highest preamble power. Note: You can use the same procedure to study the signal level coverage of several base stations by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 69.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

985

Atoll User Manual To study the signal level coverage of a single base station: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder and select Group By > Sites from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated.

Tip:

If you wish to study only sites by their status, at this step you could group them by status.

3. Select the propagation parameters to be used in the coverage prediction: a. Click the Expand button ( ) to expand the Transmitters folder. b. Right-click the group of transmitters you want to study. The context menu appears. c. Select Open Table from the context menu. A table appears with the properties of the selected group of transmitters. d. In the table, you can configure two propagation models: one for the main matrix, with a shorter radius and a higher resolution, and another for the extended matrix, with a longer radius and a lower resolution. By calculating two matrices you can reduce the time of calculation by using a lower resolution for the extended matrix and you can obtain more accurate results by using propagation models best suited for the main and extended matrices. e. In the Main Matrix column: f. Select a Propagation Model. Enter a Radius and Resolution.

If desired, in the Extended Matrix column: Select a Propagation Model. Enter a Radius and Resolution.

g. Close the table. 4. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. The Study Types dialogue lists the coverage prediction types available. They are divided into Standard Studies, supplied with Atoll, and Customised Studies. Unless you have already created some customised studies, the Customised Studies list will be empty. 5. Select Coverage by Signal Level and click OK. A study properties dialogue appears. 6. You can configure the following parameters in the Properties dialogue: General tab: You can change the assigned Name of the coverage prediction, the Resolution, and the storage Folder for the coverage prediction, and add some Comments. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient:

Size of the Coverage Prediction

City Centre City County State Country

Display Resolution
5m 20 m 50 m 100 m According to the size of the country

Note:

If you create a new coverage prediction from the context menu of either the Transmitters or Predictions folder, you can select the sites using the Group By, Sort, and Filter buttons under Configuration. Because you already selected the target sites, however, only the Filter button is available.

Condition tab: The coverage prediction parameters on the Condition tab allow you to define the signals that will be considered for each pixel (see Figure 10.514). At the top of the Condition tab, you can set the signal level range to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, a longer time for calculation.

986

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration. 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.

Figure 10.514: Condition settings for a coverage prediction by signal level Display tab: You can modify how the results of the coverage prediction will be displayed. Note: Under Display Type, select "Value Intervals." Under Field, select "Best signal level." You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 32. You can create a tooltip with information about the coverage prediction by clicking the Browse button ( ) beside the Tip Text box and selecting the fields you want to display in the tooltip. 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.

7. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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 on the Data tab. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button ( ) beside the coverage prediction in the Predictions ). ), Atoll only calculates unlocked coverage predictions (

10.2.8

Studying Base Stations

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects the rectangle containing the computation zone. Figure 10.515 gives an example of a computation zone. In Figure 10.515, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction. Site 130 is within the coverage zone but has no active transmitters. Therefore, it will not be taken into consideration either.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

987

Atoll User Manual

Figure 10.515: An example of a computation zone Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main propagation model with a shorter radius (displayed with a blue square in Figure 10.515) and a higher resolution and an extended propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower resolution path loss matrices outside the area covered by the main propagation model. In this section, the following are explained: "Path Loss Matrices" on page 988. "Assigning a Propagation Model" on page 990. "The Calculation Process" on page 992. "Creating a Computation Zone" on page 992. "Setting Transmitters or Cells as Active" on page 993. "Signal Level Coverage Predictions" on page 993. "Analysing a Coverage Prediction" on page 997. "WiMAX Coverage Predictions" on page 1006. "Printing and Exporting Coverage Prediction Results" on page 1022.

10.2.8.1

Path Loss Matrices

In addition to the distance between the transmitter and the received, path loss is caused by objects in the transmitterreceiver path. In Atoll, the path loss matrices must be calculated before predictions and simulations can be made.

Storing Path Loss Matrices

Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: One file per transmitter with the extension LOS for its main path loss matrix.

988

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.

To set the storage location of the path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss matrices and the location for the shared path loss matrices: Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are loading path loss matrices from a shared location, where you store your changes to shared path loss matrices. Click the button beside the 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. Note: Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private Directory.

Caution:

When you save the path loss files externally, the external files are updated as soon as calculations are performed. 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 path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual.

5. Click OK.

Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the following display options: Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.

The Available Results table lists the following information for each displayed path loss matrix: Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a Boolean field indicating whether or not the path loss matrix is valid. Origin of Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed.

5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 10.516) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

989

Atoll User Manual

Figure 10.516: Path loss matrices statistics

10.2.8.2

Assigning a Propagation Model

In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 991, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 991, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 990, this is the propagation model that will be used for all transmitters, except for those to which you have assigned a propagation model either individually or as part of a group. Important: 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. 3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 170, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following are explained: "Assigning a Propagation Model to All Transmitters" on page 990. "Assigning a Propagation Model to a Group of Transmitters" on page 991. "Assigning a Propagation Model to One Transmitter" on page 991.

For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.

Assigning a Propagation Model to All Transmitters

In Atoll, you can choose a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

6. If desired, under Extended Matrix: Select a Propagation Model Enter a Radius and Resolution.

7. Click OK. The selected propagation models will be used for all transmitters.

990

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Note:

Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 991 will override this entry.

Assigning a Propagation Model to a Group of Transmitters

Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. From the Group By submenu of the context menu, select the property by which you want to group the transmitters. The objects in the folder are grouped by that property. Note: You can group transmitters by several properties by using the Group By button on the Properties dialogue. For more information, see "Advanced Grouping" on page 70.

4. Click the Expand button ( ) to expand the Transmitters folder. 5. Right-click the group of transmitters to which you want to assign a main and extended propagation model. The context menu appears. 6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected group. For each transmitter, you can set the propagation model parameters in the following columns: Main Propagation Model Main Calculation Radius (m) Main Resolution (m) Extended Propagation Model Extended Calculation Radius (m) Extended Resolution (m)

7. To enter the same values in one column for all transmitters in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

Assigning a Propagation Model to One Transmitter

If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previously made globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main Matrix: Select a Propagation Model. Enter a Radius and Resolution.

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

8. Click OK. The selected propagation models will be used for the selected transmitter.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

991

Atoll User Manual

Note:

You can also define the propagation models for a transmitter by right-clicking it in the map window and selecting Properties from the context menu.

10.2.8.3

The Calculation Process

When you create a coverage prediction and click the Calculate button ( ), Atoll follows the following process: 1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button ( ). ) beside the coverage prediction 3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( in the Predictions folder. Notes: You can stop any calculations in progress by clicking the Stop Calculations button ( the toolbar. ) in

When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.

10.2.8.4

Creating a Computation Zone

To create a computation zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Computation Zone folder. The context menu appears. 4. Select Draw from the context menu. 5. Draw the computation zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. The computation zone is delimited by a red line. If you clear the computation zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a computation zone with one of the following methods: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and selecting Use as > Computation Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation Zone folder on the Geo tab and selecting Fit to Map Window from the context menu. Note: You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: Saving the computation zone in the user configuration: For information on exporting the computation zone in the user configuration, see "Exporting a User Configuration" on page 79. Exporting the computation zone: You can export the computation zone by rightclicking the Focus Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

992

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.2.8.5

Setting Transmitters or Cells as Active

When you make a coverage prediction, Atoll considers all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, before you define a coverage prediction, you must ensure that all the transmitters on the base stations you wish to study have been activated. In the Explorer window, active transmitters are indicated with a red icon ( ) in the Transmitters folder and with the defined colour on the map and inactive transmitters are indicated with an empty icon ( )in the Transmitters folder and on the map. In Atoll, you can also set the cell on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zones context menu. To set an individual transmitter as active: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter you want to activate. The context menu appears. 4. Select Active Transmitter from the context menu. The transmitter is now active. To set more than one transmitter as active using the Transmitters context menu: 1. Click the Data tab of the Explorer window. 2. Select the transmitters you want to set as active: To set all transmitters as active, right-click the Transmitters folder. The context menu appears. To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and right-click the group of transmitters you want to set as active. The context menu appears.

3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one transmitter as active using the Transmitters table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitters parameters in a row. 4. For each transmitter that you want to set as active, select the check box in the Active column. To set more than one cell as active using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cells parameters in a row. 4. For each cell that you want to set as active, select the check box in the Active column. To set transmitters as active using a zone: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder.

3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. Note: If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 41.

4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll. 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 Administrator Manual.

10.2.8.6

Signal Level Coverage Predictions

Atoll offers a series of standard coverage predictions based on the measured signal level at each pixel; other factors, such as interference, are not taken into consideration. Coverage predictions specific to WiMAX are covered in "WiMAX Coverage Predictions" on page 1006. 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 study (which will appear under the heading Customised Studies in the Study Types dialogue). You can also select Duplicate from the coverage predictions context menu to create a copy. By dupli-

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

993

Atoll User Manual cating an existing prediction that has the parameters you wish to study, you can create a new coverage prediction more quickly. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the 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 import 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 "Exporting a User Configuration" on page 79. The following standard coverage predictions are explained in this section: "Making a Coverage Prediction by Signal Level" on page 994 "Making a Coverage Prediction by Transmitter" on page 995 "Making a Coverage Prediction on Overlapping Zones" on page 996.

10.2.8.6.1

Making a Coverage Prediction by Signal Level

A coverage prediction by signal level allows you to predict coverage zones by the transmitter signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest preamble power. To make a coverage prediction by signal level: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 10.517). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" 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. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration. 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.

Figure 10.517: Condition settings for a coverage prediction by signal level 7. Click the Display tab. If you choose to display the results by best signal level, the coverage prediction results will be in the form of thresholds. If you choose to display the results by signal level, the coverage prediction results will be arranged according to transmitter. For information on adjusting the display, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 10.518).

994

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.518: Coverage prediction by signal level

10.2.8.6.2

Making a Coverage Prediction by Transmitter

A coverage prediction by transmitter allows the user to predict coverage zones by transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest preamble power. To make a coverage prediction by transmitter: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Transmitter and click OK. The Coverage by Transmitter Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 10.519). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" 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. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration. 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.

Figure 10.519: Condition settings for a coverage prediction by transmitter

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

995

Atoll User Manual 7. 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 "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 10.520).

Figure 10.520: Coverage prediction by transmitter

10.2.8.6.3

Making a Coverage Prediction on Overlapping Zones

Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction on overlapping zones on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest preamble power. To make a coverage prediction on overlapping zones: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Overlapping Zones and click OK. The Overlapping Zones Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 10.521). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" 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. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration. 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.

996

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.521: Condition settings for a coverage prediction on overlapping zones 7. Click the Display tab. For a coverage prediction on overlapping zones, the Display Type "Value Intervals" based on the Field "Number of Servers" is selected by default. Each overlapping zone will then be displayed in a colour corresponding to the number of servers received per pixel. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 10.522).

Figure 10.522: Coverage prediction on overlapping zones

10.2.8.7

Analysing a Coverage Prediction

Once you have performed a coverage prediction study, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 985). If several coverage predictions are visible on the map, it may be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which coverage predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following tools are explained: "Displaying the Legend Window" on page 998. "Displaying Coverage Prediction Results Using Tooltips" on page 998. "Using the Point Analysis Reception Tab" on page 998. "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 999. "Displaying a Coverage Prediction Report" on page 1000. "Viewing Coverage Prediction Statistics" on page 1001. "Comparing Coverage Predictions: Examples" on page 1002. Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

997

Atoll User Manual

10.2.8.7.1

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

10.2.8.7.2

Displaying Coverage Prediction Results Using Tooltips

You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tool tips. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 985). To get coverage prediction results in the form of tool tips: 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 tooltip appears with the information defined in the Display tab of the coverage prediction properties (see Figure 10.523).

Figure 10.523: Displaying coverage prediction results using tool tips

10.2.8.7.3

Using the Point Analysis Reception Tab

Once you have calculated the coverage prediction, you can use the Point Analysis tool. The Point Analysis window gives you information on reception for any point on the map. The Reception tab gives you information on the preamble, traffic, and pilot signal levels, C/(I+N), bearers, throughputs, etc. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. The analysis is based on: The preamble signal levels, used to determine the best server for the pixel. The best serving transmitter is determined according to the received preamble signal level from the cell with the highest preamble power. If more than one cell covers the pixel, the one with the lowest layer is selected as the serving (reference) cell. The preamble C/N or C/(I+N), used to determine the permutation zone assigned to each pixel (WiMAX 802.16e) and used to determine whether SU-MIMO or STTD/MRC is used for AMS, and whether MU-MIMO can be used in uplink or not. The downlink traffic signal levels, downlink traffic loads, segmentation usage (WiMAX 802.16e), AAS simulation results, and AAS usage, for determining the downlink traffic C/(I+N), bearer, and throughputs. The uplink signal levels, uplink noise rise, and AAS simulation results, for determining the uplink C/(I+N), bearer, and throughputs.

The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations. You can make a reception analysis to verify a coverage prediction. In this case, before you make the point analysis, ensure the coverage prediction you want to verify is displayed on the map. To make a reception analysis: 1. Click the Point Analysis button ( Figure 10.524). 2. Click the Reception tab. 3. At the top of the Reception tab, select "Cells Table" from Load Conditions. 4. If you are making a reception analysis to verify a coverage prediction, you can recreate the conditions of the coverage prediction: a. Select the same Terminal, Service, and Mobility studied in the coverage prediction. b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. Edit the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class. ) on the toolbar. The Point Analysis Tool window appears (see

c. Click OK to close the Properties dialogue.

998

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 5. Select the signal to be displayed from the Display list. 6. Move the pointer over the map to make a reception analysis for the current location of the pointer. 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 reference signal level. 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. Click the Point Analysis button ( Select the load conditions to use in this analysis from simulations or from the Cells table. ) on the toolbar again to end the point analysis. Select the parameters of the probe user to be studied.

The preamble reception from the best server (top-most bar) and all interfering cells. Solid bars indicate the signal levels above the preamble C/N thresholds.

The connection status (preamble, downlink and uplink) for the current point. : Service available : Service unavailable

Figure 10.524: Point Analysis Tool: Reception tab The bar graph displays the following information: The preamble, traffic, orr 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 portion of the bar which is not filled 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 right-hand frame opens a dialogue with additional information about the best server: Preamble: Azimuth and tilt of the receiver, total losses, received preamble power, preamble total noise (I+N), preamble C/(I+N). Downlink: Permutation zone, diversity mode, pilot and traffic received powers, traffic total noise (I+N), pilot and traffic C/(I+N), bearer, channel throughputs, and cell capacities. Uplink: Permutation zone, diversity mode, received power, transmission power, allocated bandwidth, total noise (I+N), C/(I+N), bearer, channel throughputs, cell capacities, and allocated bandwidth throughputs. To get all the above information in a single report: a. Right-click the Point Analysis window and select Report from the context menu. The Analysis Report dialogue appears.

10.2.8.7.4

Creating a Focus or Hot Spot Zone for a Coverage Prediction Report

The focus and hot spot zones define the area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spot zones in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones. To define a focus zone or hot spot zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. Select Draw from the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

999

Atoll User Manual 5. Draw the focus or hot spot zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the focus or hot spot zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot zone by right-clicking it and selecting Use as > Focus Zone or Use as > New Hot Spot from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot spot zones, you can import the name given to each zone as well. Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map Window from the context menu. Notes: You can save the focus zone or hot spot zones, so that you can use it in a different Atoll document, in the following ways: Saving the focus zone in the user configuration: For information on exporting the focus zone in the user configuration, see "Exporting a User Configuration" on page 79. - Exporting the focus zone or hot spot zones: You can export the focus zone or hot spot zones by right-clicking the Focus Zone or the Hot Spot Zones folder on the Data tab of the Explorer window and selecting Export from the context menu.. You can include population statistics in the focus or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. -

10.2.8.7.5

Displaying a Coverage Prediction Report

Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage predictions Properties dialogue. The coverage prediction report is displayed in a table. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 58. Atoll bases the report on the area covered by the focus zone and hot spot zones; if no focus zone is defined, Atoll will use the computation zone. Using a focus zone enables you to create a report without the border effect. In other words, the results of a coverage prediction are delimited by the computation zone; results close to the border are influenced by fact that no calculations have been made outside the computation zone. Basing a report on a focus zone that is smaller than the computation zone eliminates the border effect. By using a focus zone for the report, you can create a report for a specific number of base stations, instead of creating a report for every site that has been calculated. The focus zone or hot spot zone must be defined before you display a report; it is not necessary to define it before computing coverage. The focus or hot spot zone does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 999. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down. to move it up or

1000

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. The Open dialogue appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the focus zone if available or on the hot spot zones and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 4. 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. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. a appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. 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 spot zone: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. 2. Display the report as explained above. 3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears. 4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the population map: "Population" (Population): The number of inhabitants covered. "Population" (% Population): The percentage of inhabitants covered. "Population" (Population [total]): The total number of inhabitants inside the zone. to move it up or

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 customers/km, etc.). Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable Versus Non Integrable Data" on page 129.

10.2.8.7.6

Viewing Coverage Prediction Statistics

Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage study colours, interval steps, and shading as defined in the Display tab of the coverage predictions Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1001

Atoll User Manual Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone, you can display the statistics for a specific number of base stations, instead of displaying statistics for every base station that has been calculated. Hot spot zones are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before computing coverage. For information on defining a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 999. To display the statistics on a coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction whose statistics you want to display. The context menu appears. 4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined by the focus zone (see Figure 10.525). Under Histogram Based on Covered Areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Detailed Results section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics Based on Study Conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.

Figure 10.525: Histogram of a coverage prediction by signal level

10.2.8.7.7

Comparing Coverage Predictions: Examples

Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison study coverage in one of the following ways: Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered by both coverage 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 only are green, and pixels covered only by the second prediction are blue).

To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged).

1002

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 5. Calculate the duplicate coverage prediction. 6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage between them. In this section, the following examples are explained: "Example 1: Studying the Effect of a New Base Station" on page 1003 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 1005.

Example 1: Studying the Effect of a New Base Station

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how you can verify if a newly added base station improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 994. The results are displayed in Figure 10.526. An area with poor coverage is visible on the right side of the figure.

Figure 10.526: Signal level coverage prediction of existing network A new base station is added, either by creating the base station and adding the transmitters, as explained in "Creating a WiMAX Base Station" on page 969, or by placing a station template, as explained in "Placing a New Base Station Using a Station Template" on page 976. Once the new site has been added, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new base station (see Figure 10.527).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1003

Atoll User Manual

Figure 10.527: 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 prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their 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 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.528, shows clearly the area covered only by the new base station.

1004

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.528: Comparison of both signal level coverage predictions

Example 2: Studying the Effect of a Change in Transmitter Tilt

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 995. The results are displayed in Figure 10.529. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated with a red oval in the figure.

Figure 10.529: Coverage prediction by transmitter of existing network You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue. Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original coverage prediction 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.530).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1005

Atoll User Manual

Figure 10.530: Coverage prediction by transmitter of network after modifications As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change in coverage, you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their 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 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 10.531, shows clearly the increase in coverage due at the change in antenna tilt.

Figure 10.531: Comparison of both transmitter coverage predictions

10.2.8.8

WiMAX Coverage Predictions

Two types of WiMAX coverage predictions are available in Atoll: coverage predictions used to analyse the effective signal levels, and coverage predictions used to analyse the signal quality. Effective signal analysis coverage predictions can be used to analyse different signals (preamble, traffic, etc.) in the downlink as well as in the uplink once the user-end gains and losses have been considered. These coverage predictions do not depend on the network load conditions.

1006

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Using signal quality coverage predictions you can study the effective service coverage area and capacity of each cell in the network. These coverage predictions depend on the interference in the network and the cell load conditions. For this reason, the network load must be defined in order to calculate these coverage predictions. For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined service, mobility type, and terminal. The following are explained in the following sections: "Service and User Modelling" on page 1007.

This section explains the coverage predictions available for analysing the effective signal level and signal quality. The following are explained: "Analysing the Effective Signal Levels" on page 1009. "Analysing the Signal Quality" on page 1011.

You can also use the Point Analysis window to study the interference level at a point. Load conditions can be selected for the analysis as well as the characteristics of the user-definable probe receiver, i.e., a terminal, a mobility, and a service: "Analysing Interference Areas Using a Point Analysis" on page 1020.

10.2.8.8.1

Service and User Modelling

Atoll can base its signal quality studies on the DL traffic load and the UL noise rise entered in the Cells table (for more information, see "Setting the Traffic Loads and the UL Noise Rise" on page 1011). Before you can model services, you must define WiMAX radio bearers. For more information on WiMAX radio bearers, see "Defining WiMAX Radio Bearers" on page 1145. In this section, the following are explained: "Modelling Services" on page 1007. "Modelling Mobility Types" on page 1008. "Modelling Terminals" on page 1008.

Modelling Services
Services are the various services available to users. These services can be either voice or data type services. This section explains how to create a service. The following parameters are used in predictions: Throughput scaling factor Throughput offset Body loss

To create or modify a service: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the WiMAX Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. Note: You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.

5. You can edit the fields on the General tab to define the new service. Some fields depend on the type of service you choose. You can change the following parameters. 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. 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-RealTime 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 1148. Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for users accessing a voice type service during Monte Carlo simulations. 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. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1007

Atoll User Manual 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.

6. Click OK.

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 WiMAX 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. To create or modify a mobility type: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the WiMAX Parameters folder.

3. Right-click the Mobility Types folder. The context menu appears. 4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears. Note: You can modify the properties of an existing mobility type by right-clicking the mobility type in the Mobility Types folder and selecting Properties from the context menu.

5. You can enter or modify the following parameters in the Mobility Types New Element Properties dialogue: Name: Enter a descriptive name for the mobility type. Average Speed: Enter an average speed for the mobility type. This field is for information only; the average speed is not used by any calculation.

6. Click OK.

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 on-board navigation device. The following parameters are used in predictions: Antenna WiMAX equipment Maximum and minimum terminal power Gain and losses Noise figure Supported antenna diversity technique Number of transmission and reception antennas for MIMO

To create or modify a terminal: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the WiMAX Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select New from the context menu. The Terminals New Element Properties dialogue appears. Note: You can modify the properties of an existing terminal by right-clicking the terminal in the Terminals folder and selecting Properties from the context menu.

5. You can enter or modify the following parameters in the Terminals New Element Properties dialogue: Name: Enter a descriptive name for the terminal. Under Transmission/Reception, Min Power: Enter the minimum transmission power of the terminal. Max Power: Enter the maximum transmission power of the terminal. Noise Figure: Enter the noise figure of the terminal (used to calculate the downlink total noise). Losses: Enter the losses of the terminal. WiMAX Equipment: Select a WiMAX equipment from the list of available equipment. For more information on WiMAX equipment, see "Defining WiMAX Equipment" on page 1146. Under Antenna, 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. -

1008

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Note:

Keep in mind that 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. 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 (permutation zone in WiMAX 802.16e) that supports both antenna diversity techniques, both AAS and MIMO gains will be applied. Number of Transmission Antennas: Under MIMO, enter the number of antennas used by the terminal in transmission. Number of Reception Antennas: Under MIMO, enter the number of antennas used by the terminal in reception.

6. Click OK.

10.2.8.8.2

Analysing the Effective Signal Levels

Atoll offers a couple of WiMAX coverage predictions which can be based on the predicted signal level from the best server and the thermal background noise at each pixel, i.e., received carrier power (C) and the carrier-to-noise ratio (C/N). This section explains the coverage predictions available for analysing the effective signal levels. Downlink and uplink effective signal analysis coverage predictions predict the effective signal levels of different types of WiMAX signals, such as preamble, traffic, etc., in the part of the network being studied. Atoll calculates the serving transmitter for each pixel depending on the downlink preamble signal level. The serving transmitter is determined according to the received preamble signal level from the cell with the highest preamble power. If more than one cell covers the pixel, the one with the lowest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the effetive signal (C or C/N for preamble, traffic, etc.). Pixels are coloured if the display threshold condition is fulfilled (in other words, if the C or C/N is higher than the C or C/N threshold). To make an effective signal analysis coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Effective Signal Analysis (DL) or Effective Signal Analysis (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 10.532). On the Condition tab, you can select a Terminal, a Mobility type, and a Service. The effective signal analysis coverage prediction is always a best server coverage prediction. The Noise Figure defined in the terminal types properties dialogue 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 WiMAX equipment, see "Modelling Services" on page 1007, "Modelling Terminals" on page 1008, "Modelling Mobility Types" on page 1008, and "Defining WiMAX Equipment" on page 1146, respectively. 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 for the effective signal analysis calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1009

Atoll User Manual

Figure 10.532: Condition settings for an effective signal analysis coverage prediction 7. Click the Display tab. 8. From the Display Type list, choose one of the following: Discrete Values: Select "Discrete Values" as the Display Type and "Permutation Zone (DL)" or "Segment" from the Field list for Effective Signal Analysis (DL) if you want Atoll to colour the pixels in a cells coverage area according to the downlink permutation zones assigned to them or the segment(s) covering them. Select "Discrete Values" as the Display Type and "Permutation Zone (UL)" from the Field list for Effective Signal Analysis (UL) if you want Atoll to colour the pixels in a cells coverage area according to the uplink permutation zones assigned to them. Value Intervals: Select "Value Intervals" as the Display Type to colour the pixels in the cells coverage area according the value interval of the value selected from the Field list. You can choose from displaying results by "Best Preamble Signal Level," "Best Pilot Signal Level," "Best Traffic Signal Level," "Preamble C/N Level," "Pilot C/N Level," or "Traffic C/N Level" for Effective Signal Analysis (DL), and between displaying results by Signal Level or C/N Level for Effective Signal Analysis (UL).

For information on adjusting the display, see "Display Properties of Objects" on page 32. 9. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 10.533 and Figure 10.534).

Figure 10.533: Downlink traffic C/N coverage prediction

1010

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.534: Uplink C/N coverage prediction

10.2.8.8.3

Analysing the Signal Quality

In WiMAX, the capacity and the effective service coverage areas of cells are influenced by network loads. As the network load increases, the area where a cell provides service decreases. For this reason, network loads must be defined in order to calculate these coverage predictions. Atoll offers a series of coverage predictions which are based on the predicted signal level from the best server and the predicted signal levels from other cells (interference) at each pixel, i.e., carrier-to-interference-and-noise ratio, or C/(I+N). The downlink interference received from different cells of the network is weighted by their respective downlink traffic loads. The measure of uplink interference for each cell is provided by the uplink noise rise. If you have traffic maps, you can do a Monte Carlo simulation to determine the downlink traffic loads and the uplink noise rise values for a generated user distribution. If you do not have traffic maps, Atoll can calculate these coverage predictions using the downlink traffic loads and the uplink noise rise values defined for each cell. In this section, these coverage predictions will be calculated using downlink traffic loads and the uplink noise rise values defined at the cell level. Before making a prediction, you will have to set the downlink traffic loads and the uplink noise rise, and the parameters that define the services and users. These are explained in the following sections: "Setting the Traffic Loads and the UL Noise Rise" on page 1011.

Several signal quality coverage predictions are explained in this section. The following studies are explained: "Making a Coverage Prediction by C/(I+N) Level" on page 1012. "Making a Coverage by Best Bearer" on page 1014. "Making a Coverage by Throughput" on page 1016. "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1018. "Making a Coverage by Quality Indicator" on page 1019. "Analysing Interference Areas Using a Point Analysis" on page 1020.

Setting the Traffic Loads and the UL Noise Rise

If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the Cells tab of the transmitters Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all the cells using the Cells table. To set the traffic loads and the uplink noise rise using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Enter a value in the following columns: Traffic Load (DL) (%) UL Noise Rise (dB) Segmentation Usage (DL) (%) (WiMAX 802.16e)

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 UL Noise Rise (dB). For a definition of the values, see "Cell Description" on page 972.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1011

Atoll User Manual 5. To enter the same values in one column for all cells in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

Making a Coverage Prediction by C/(I+N) Level

Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels in the part of the network being studied. Atoll calculates the best server for each pixel depending on the downlink preamble signal level. The serving transmitter is determined according to the received preamble signal level from the cell with the highest preamble power. If more than one cell covers the pixel, the one with the lowest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured if the display threshold condition is fulfilled (in other words, if the C/(I+N) is higher than C/(I+N) threshold). Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference, which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information on frequency bands, see "Defining Frequency Bands" on page 1139. The preamble C/(I+N) is calculated using the preamble power and the main antenna. Interference on the preamble does not depend on the cell load conditions. It depends only on the probabilities of collision between the subcarriers used to transmit the preamble. The downlink traffic C/(I+N) is calculated using the traffic power, the main antenna or the smart antenna equipment, downlink traffic load, the segmentation usage ratio, and any AAS simulation results stored either in the cell properties or in the selected simulation results. The downlink traffic C/(I+N) also takes into account the probabilities of collision between subcarriers when segmentation is used. The uplink C/(I+N) is calculated using the terminal power calculated after power control, the main antenna or the smart antenna equipment, uplink noise rise, and any AAS simulation results stored either in the cell properties or in the selected simulation results. To make a coverage prediction by C/(I+N) level: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 10.535). 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. Note: 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, 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 dialogue 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 WiMAX equipment, see "Modelling Services" on page 1007, "Modelling Terminals" on page 1008, "Modelling Mobility Types" on page 1008, and "Defining WiMAX Equipment" on page 1146, respectively. 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 for C(I+N) calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

1012

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.535: Condition settings for a coverage prediction by C/(I+N) level 7. Click the Display tab. You can choose from displaying results by Traffic C/(I+N) Level (DL), Traffic Total Noise (I+N) (DL), Preamble C(I+N) Level (DL), or Preamble Total Noise (I+N) (DL) for the Coverage by C/(I+N) Level (DL) and by C/(I+N) Level (UL), Total Noise (I+N) (UL), Allocated Bandwidth (UL) (No. of Subchannels), C/(I+N) Level for 1 Subchannel (UL), or Transmission Power (UL) (dBm) for the Coverage by C/(I+N) Level (UL). The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 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 1148. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 10.536 and Figure 10.537).

Figure 10.536: Coverage prediction by downlink traffic C/(I+N)

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1013

Atoll User Manual

Figure 10.537: Coverage prediction by uplink C/(I+N)

Making a Coverage by Best Bearer

Downlink and uplink best radio bearer coverage predictions calculate and display the best WiMAX radio bearers based on C(I+N) for each pixel. To make a coverage prediction by best bearer: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Best Bearer (DL) or Coverage by Best Bearer (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 10.538). 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 downlink traffic load, uplink noise rise, and any AAS simulation results stored in the cell properties. Note: 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, 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 dialogue 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 traffic C(I+N) level is performed using the bearer selection thresholds defined in the WiMAX equipment. This WiMAX 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. Note: You can make Atoll use only the bearers for which selection thresholds are defined in both the terminals and the cells WiMAX 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 WiMAX equipment, see "Modelling Services" on page 1007, "Modelling Terminals" on page 1008, "Modelling Mobility Types" on page 1008, and "Defining WiMAX Equipment" on page 1146, respectively.

1014

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 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 for C(I+N) calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Figure 10.538: Condition settings for a coverage prediction on WiMAX bearers 7. Click the Display tab. You can display results by Best Bearer or Modulation. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 10.539 and Figure 10.540).

Figure 10.539: Coverage prediction by downlink best bearer

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1015

Atoll User Manual

Figure 10.540: Coverage prediction by uplink best bearer

Making a Coverage by Throughput

Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities based on C(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1018. To make a coverage prediction by throughput: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 10.541). 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 downlink traffic load, uplink noise rise, and any AAS simulation results stored in the cell properties. Note: 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, 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 dialogue 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 WiMAX equipment. This WiMAX 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. The Mobility is used to indicate the bearer selection threshold graph to use. The service is used for the application throughput parameters defined in the service Properties dialogue. Note: You can make Atoll use only the bearers for which selection thresholds are defined in both the terminals and the cells WiMAX equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual.

1016

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on page 1007, "Modelling Terminals" on page 1008, "Modelling Mobility Types" on page 1008, and "Defining WiMAX Equipment" on page 1146, respectively. 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 for C(I+N) calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Figure 10.541: Condition settings for a throughput coverage prediction 7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. You can set parameters to display the following results: Channel throughputs: To display channel throughputs, select "Peak MAC Channel Throughput," "Effective MAC Channel Throughput," or "Application Channel Throughput" from the Field list. Cell capacities: To display cell capacities, select "Peak MAC Cell Capacity," "Effective MAC Cell Capacity," or "Application Cell Capacity" from the Field list. Allocated bandwidth throughputs in uplink: To display allocated bandwidth throughputs in uplink, select "Peak MAC Allocated Bandwidth Throughput," "Effective MAC Allocated Bandwidth Throughput," or "Application Allocated Bandwidth Throughput" from the Field list.

The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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 WiMAX equipment defined in the selected terminal for downlink or the WiMAX 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 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 "The Global Transmitter Parameters" on page 1140. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1017

Atoll User Manual

Figure 10.542: Coverage prediction by downlink channel throughput

Figure 10.543: Coverage prediction by uplink channel throughput

Making an Aggregate Throughput Coverage Prediction Using Simulation Results

Atoll calculates the aggregate peak MAC, effective MAC, and application cell throughputs during Monte Carlo simulations. The aggregate cell throughputs are the sums of the cells user throughputs. You can create a coverage prediction that calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its aggregate throughput. To create an aggregate throughput coverage prediction: 1. Create and run a Monte Carlo simulation. For more information on creating Monte Carlo simulations, see "Calculating and Displaying Traffic Simulations" on page 1054. 2. Create a coverage prediction by throughput as explained in "Making a Coverage by Throughput" on page 1016, with the following exceptions: a. On the Condition tab, select a simulation or group of simulations from the Load Conditions list. The coverage prediction will display the results based on the selected simulation or on the average results of the selected group of simulations. b. On the Display tab, you can display results by Peak MAC Aggregate Throughput, Effective MAC Aggregate Throughput, or Aggregate Application Throughput. The coverage prediction results will be in the form of thresholds. For information on defining the display, see "Display Properties of Objects" on page 32.

1018

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 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 1068.

Making a Coverage by Quality Indicator

Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators (BLER, BER, etc.) based on the best WiMAX radio bearers and on C(I+N) for each pixel. To make a coverage prediction by quality indicator: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 10.538). 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 downlink traffic load, uplink noise rise, and any AAS simulation results stored in the cell properties. Note: 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, 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 types properties dialogue 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 traffic C(I+N) level is performed using the bearer selection thresholds defined in the WiMAX equipment, and the quality indicator graphs from the WiMAX equipment are used to determine the values of the selected quality indicator on each pixel. The WiMAX equipment is the one defined for 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. Note: You can make Atoll use only the bearers for which selection thresholds are defined in both the terminals and the cells WiMAX 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 WiMAX equipment, see "Modelling Services" on page 1007, "Modelling Terminals" on page 1008, "Modelling Mobility Types" on page 1008, and "Defining WiMAX Equipment" on page 1146, respectively. 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 for C(I+N) calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Figure 10.544: Condition settings for a coverage prediction by quality indicators

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1019

Atoll User Manual 7. 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 1145. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 10.545 and Figure 10.546).

Figure 10.545: Coverage prediction by downlink BLER

Figure 10.546: Coverage prediction by uplink BLER

10.2.8.8.4

Analysing Interference Areas Using a Point Analysis

In Atoll, you can study the interferers of a transmitter using the Point Analysis tool.

1020

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks To study interference areas using a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Interference tab. The Interference tab displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar indicating the total noise (I+N) experienced by the receiver, and bars representing the interference received from each interferer. The information displayed in the bar graph depends on the selections made at the top of the Interference tab: Load Conditions: Select the load conditions Atoll will use to calculate interference: the settings defined in the Cells table, the load conditions from a traffic density map, or the load conditions from a simulation. Display: Select whether Atoll should display the interference on the Preamble, the Traffic, or the Pilot signal. Select a Terminal, Service, and Mobility.

Figure 10.547 gives an example of the Interference tab. The signal level of the transmitter, Site62_2, is -82.38 dB and is indicated by a red bar. The black bar indicates the total noise (I+N) experienced by the receiver (-86.55 dB). The three interferers are responsible for -92.26 dB (purple), -100.39 dB (light green), and -103.29 dB (light blue). The displayed bars are all filled. However, if the bar corresponding to an interferer is 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. If you let the pointer rest on a bar, details are displayed in the tooltip: 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.

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 tooltip.

Figure 10.547: Point Analysis Tool: Interference tab 5. You can change the following options at the top of the Interference tab: Sort by Interference: You can select the Sort by Interference check box if you want Atoll to display the interfers by the effective interference received. Intra-technology: You can select the Intra-technology check box if you want Atoll to display the intra-technology interference.

6. Right-click the Interference tab and select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. 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. You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.

To get the details about the best server and all the interferers in the form of a report: a. Right-click the Point Analysis window and select Report from the context menu. The Analysis Report dialogue appears. 7. Click the Results tab.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1021

Atoll User Manual The Results tab displays, for each cell received, the cells name, its distance from the receiver, its preamble index (for 802.16e documents), and the preamble C, and C/N for all cells. Additionally, the interference from all the cells other than the best server is displayed. 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 in tool tips for these arrows. 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 preamble signal level. 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 tooltip. 8. You can select a Terminal, Service, and Mobility at the top of the Results tab.

10.2.8.9

Printing and Exporting Coverage Prediction Results

Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. 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 65. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 46. 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 49.

10.2.9

Planning Neighbours
You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you set. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbours only to the cells within the computation zone. The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo tab in the Explorer window is selected. Usually, you will allocate neighbours globally during the beginning of a radio planning project. Afterwards, you will allocate neighbours to base stations or transmitters as you add them. You can use automatic allocation on all cells in the document, or you can define a group of cells either by using a focus zone or by grouping transmitters in the Explorer window. For information on creating a focus zone, see "Using a Focus Zone or Hot Spot Zones" on page 43. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 69. Atoll supports the following neighbour types in a WiMAX 802.16e network: Intra-technology neighbours: Intra-technology neighbours are cells defined as neighbours that also use WiMAX 802.16e. Inter-technology neighbours: Inter-technology neighbours are cells defined as neighbours that use a technology other than WiMAX 802.16e.

In this section, the following are explained: "Importing Neighbours" on page 1022 "Defining Exceptional Pairs" on page 1023 "Configuring Importance Factors for Neighbours" on page 1023 "Allocating Neighbours Automatically" on page 1023 "Checking Automatic Allocation Results" on page 1026 "Allocating and Deleting Neighbours per Cell" on page 1029 "Calculating the Importance of Existing Neighbours" on page 1031 "Checking the Consistency of the Neighbour Plan" on page 1032 "Exporting Neighbours" on page 1033.

10.2.9.1

Importing Neighbours
You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table.

1022

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Data tab of the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 63.

10.2.9.2

Defining Exceptional Pairs

In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs might be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Right-click the cell for which you want to define neighbour constraints. The context menu appears. 5. Select Record Properties from the context menu. The cells Properties dialogue appears. 6. Click the Intra-technology Neighbours tab. 7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( a. Select the cell from the list in the Neighbours column. b. In the Status column, select one of the following: Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell. ):

8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table by right-clicking the Transmitters folder and selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.

10.2.9.3

Configuring Importance Factors for Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. On the Intra-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency Factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 1023. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 1023.

5. Click OK.

10.2.9.4

Allocating Neighbours Automatically

Atoll can automatically allocate neighbours in a WiMAX 802.16e network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. To allocate WiMAX 802.16e neighbours automatically: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1023

Atoll User Manual 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Automatic Neighbour Allocation tab. 5. You can set the following parameters: Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour. Max. No. of Neighbours: Set the maximum number of neighbours that can be allocated to a cell. This value can be either set here for all the cells, or specified for each cell in the Cells table. Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Preamble C/N Threshold: Select the Preamble C/N Threshold check box if you want to set a global value for the Preamble C/N Threshold. If you set a global Preamble C/N Threshold value here, Atoll will either use this value or the per-cell Preamble C/N Threshold value, whichever is higher. 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 (see Figure 10.548). 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 (see Figure 10.548). 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 candidate neighbours. The area between the Handover Start and the Handover End constitutes the area within which Atoll will search for neighbours. 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 possible neighbours can be processed. Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations. % Min. Covered Area: Enter the minimum surface area, in percentage, that a possible neighbour cells coverage area must overlap the reference cells coverage area.

6. Select the desired calculation parameters: Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located on the same site as the reference cell to be automatically considered as neighbours. Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell is the best server, or where the possible neighbour cell is the second best server (respecting the handover margin). Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from the list of neighbours of the reference cell. Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 1023. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.

1024

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.548: The handover area between the reference cell and the possible neighbour 7. Click the Importance Weighting button to set the relative importance of possible neighbours: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 6., set the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell. Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 6., set the minimum and maximum importance of a possible neighbour cell being located on the same site as reference cell.

8. Click Calculate. Atoll begins the process of allocating neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Deleting existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance as calculated with the options selected in step 7. Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the reference cell, as identified in the Cell column. The possible reasons are: Co-site Adjacency Symmetry Coverage Existing

Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell is best server or second best server.

9. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations,

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1025

Atoll User Manual The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

10. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue. Notes: A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint on the forbidden neighbour will be ignored by the algorithm because the neighbour already exists. When the options Force exceptional pairs and Force symmetry are selected, Atoll considers the constraints between exceptional pairs in both directions in order to respect symmetry. On the other hand, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event Viewer. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Exporting a User Configuration" on page 79.

10.2.9.4.1

Allocating Neighbours to a New Base Station

When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects the coverage area of the cells of the new base station. To allocate neighbours to a new base station: 1. On the Data tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects" on page 69. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 1023.

10.2.9.5

Checking Automatic Allocation Results

You can verify the results of automatic neighbour allocation in the following ways: "Displaying Neighbour Relations on the Map" on page 1026. "Displaying the Coverage of Each Neighbour of a Cell" on page 1028.

10.2.9.5.1

Displaying Neighbour Relations on the Map

You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

2. Select Display Options from the context menu. The Visual Management dialogue appears. 3. Under Intra-technology Neighbours, select the Display Links check box. 4. Click the Browse button ( ) beside the Display Links check box.

5. The Intra-technology Neighbour Display dialogue appears. 6. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours table, or according to the neighbour frequency band. Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to the importance, as determined by the weighting factors.

1026

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Tip:

You can display the number of handoff attempts for each cell-neighbour pair by first 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 along with "Value Intervals" as the Display Type. For information on adding a new field to a table, see "Adding a Field to an Object Types Data Table" on page 54.

Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you can display or hide neighbour link display types individually. For information on changing display properties, see "Display Properties of Objects" on page 32. 7. Select the Add to Legend check box to add the displayed neighbour links to the legend. 8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each neighbour link. 9. Click OK to save your settings. 10. Under Advanced, select which neighbour links to display: Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations where the selected cell is the reference cell and where the neighbour relation is not symmetric. Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations where the selected cell is neighbour and where the neighbour relation is not symmetric. Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the selected cell and the neighbour.

11. Click OK to save your settings. 12. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 14. Click the Visual Management button ( ) in the Radio toolbar.

15. Click a transmitter on the map to display the neighbour relations. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). Atoll displays the following information (see Figure 10.549) for the selected cell: The symmetric neighbour relations of the selected (reference) cell are indicated by a line. The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (see Site1_2(0)) in Figure 10.549.). The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (see Site9_3(0)) in Figure 10.549.).

In Figure 10.549, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward neighbour links are coloured according to the corresponding neighbour transmitters and the inward neighbour link is coloured according to the reference transmitter because it is neighbour of Site9_3(0) here.

Figure 10.549: Neighbours of Site 22_3(0) - Display According to the Neighbour In Figure 10.550, neighbour links are displayed according to the neighbour frequency. Here, all neighbour relations are symmetric.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1027

Atoll User Manual

Figure 10.550: Neighbours of Site 22_3(0) - Display According to The Neighbour Frequency Note: You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

10.2.9.5.2

Displaying the Coverage of Each Neighbour of a Cell

By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cells neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a "Coverage by Transmitter" prediction, with the Display Type set to "Discrete Values" and the Field set to "Transmitter" (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 995). 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

3. Select Display Options from the context menu. The Neighbourhood Display dialogue appears. 4. Under Intra-technology Neighbours, select the Display Coverage Areas check box. 5. Click the Browse button ( ) beside the Display Coverage Areas check box.

6. The Intra-technology Neighbour Display dialogue appears. 7. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neighbours with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology Neighbours table. Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to the importance, as determined by the weighting factors.

8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each coverage area. 9. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 11. Click the Visual Management button ( ) in the Radio toolbar.

12. Click a transmitter on the map to display the coverage of each neighbour. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). 13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( Radio toolbar. ) in the

1028

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.2.9.6

Allocating and Deleting Neighbours per Cell

Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of a transmitters Properties dialogue. This section explains the following: "Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1029. "Allocating or Deleting Neighbours Using the Neighbours Table" on page 1029. "Allocating or Deleting Neighbours on the Map" on page 1030.

Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete WiMAX 802.16e neighbours using the Cells tab of the transmitters Properties dialogue: 1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, click the Browse button ( 5. Click the Intra-technology Neighbours tab. 6. If desired, you can enter the maximum number of neighbours. 7. Allocate or delete a neighbour. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table when you have finished creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 8. Click OK. ) beside Neighbours. The cells Properties dialogue appears.

Allocating or Deleting Neighbours Using the Neighbours Table

To allocate or delete WiMAX 802.16e neighbours using the Neighbours table: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. Note: For information on working with data tables, see "Working with Data Tables" on page 53.

4. Allocate or delete a neighbour. To allocate a new neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. ), select a reference cell in the Cell column.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1029

Atoll User Manual When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. To take into consideration all exceptionnal pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either selected forced neighbours or selected forbidden neighbours using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu.

To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. To delete several symmetric neighbour relations: a. Click in the left margins of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour.

Allocating or Deleting Neighbours on the Map

You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 1026. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters to the intra-technology neighbours list. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitters from the intra-technology neighbours. To add an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the intra-technology neighbour list of the transmitter.

1030

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks To remove an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the intra-technology neighbours list of the transmitter. To add an inward neighbour relation: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the intra-technology neighbours list of the reference transmitter. Notes: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

10.2.9.7

Calculating the Importance of Existing Neighbours

After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Select the Neighbours tab. 5. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 1023): Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference transmitters when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.

6. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Preamble C/N Threshold: Select the Preamble C/N Threshold check box if you want to set a global value for the Preamble C/N Threshold. If you set a global Preamble C/N Threshold value here, Atoll will either use this value or the per-cell Preamble C/N Threshold value, whichever is higher. Handover Start: Enter the handover start margin which must be provided by reference cell A in an overlapping area. Handover End: Enter the handover end margin between reference cell A and possible neighbour cell B in the overlapping area. Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

7. Click OK to save your modifications and close the Coverage Conditions dialogue. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1031

Atoll User Manual

Notes:

You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

8. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 5. Cause: The reason Atoll has allocated value in the Importance column. Co-site Adjacency Symmetry Coverage

Coverage: The amount of reference transmitters coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neighbour transmitter is best server or second best server. Distance: The distance in kilometres between the reference cell and the neighbour.

The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

10.2.9.8

Checking the Consistency of the Neighbour Plan

You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Intra-technology Neighbours tab.s 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want 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 the Full Lists check box if you want 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 the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours > check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax: |CELL|

Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

1032

Chapter 10: WiMAX BWA Networks Syntax: Note: |CELL| |NUMBER| |MAX NUMBER| If the field Max number of intra-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

10.2.9.9

Exporting Neighbours
The neighbour data of an Atoll document is stored in a series of tables. You can export the neighbour data to use it in another application or in another Atoll document. To export neighbour data: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours and then select the neighbour table containing the data you want to export from the context menu: Intra-Technology Neighbours: This table contains the data for the intra-technology neighbours in the current Atoll document. Inter-Technology Neighbours: This table contains the data for the inter-technology neighbours in the current Atoll document. Intra-technology Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document. Inter-technology Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs (forced and forbidden) in the current Atoll document.

4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files" on page 61.

10.2.10

Planning Frequencies
You can assign frequencies, i.e., frequency bands and channel numbers, manually to cells or use the Automatic Frequency Planning (AFP) tool to automatically allocate channels to cells. The AFP allocates channels to cells automatically such that the overall interference in the network is minimised. Once allocation is completed, you can analyse the frequency plan by creating and comparing preamble C/(I+N) coverage predictions, and view the frequency allocation on the map. The procedure for planning frequencies is: Allocating frequencies "Automatically Allocating Frequencies to Cells" on page 1034. "Allocating Frequencies to Cells Manually" on page 1035. "Using the Search Tool to Display Frequency Allocation" on page 1035. "Displaying Frequency Allocation Using Transmitter Display Settings" on page 1036. "Grouping Transmitters by Frequency" on page 1036. "Analysing the Frequency Allocation Using Coverage Predictions" on page 1037.

Displaying and analysing the frequency allocation

10.2.10.1

Allocating Frequencies
Atoll can automatically assign frequencies to cells according to set parameters. For example, the AFP takes into account the interference matrices, minimum reuse distance, and any constraints imposed by neighbours. The AFP can also be used to allocate preamble indexes automatically to the cells of an 802.16e network. The AFP can base the automatic frequency and preamble index allocation on interference matrices, whereas the automatic preamble index allocation feature available in the WiMAX module does not use interference matrices. Apart from this difference, the two automatic

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1033

Atoll User Manual preamble index allocation features are alike. For further information on preamble indexes, see "Planning Preamble Indexes" on page 1037. You can also allocate frequencies and preamble indexes to cells manually. In this section, the following methods of allocating preamble indexes are described: "Automatically Allocating Frequencies to Cells" on page 1034. "Allocating Frequencies to Cells Manually" on page 1035.

10.2.10.1.1

Automatically Allocating Frequencies to Cells

The AFP enables you to automatically allocate frequencies to the cells in the current network. To automatically allocate frequencies: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Frequency Plan > Automatic Allocation. The Frequency Allocation dialogue appears. 4. Under Allocate, select Frequencies to perform automatic frequency planning. 5. Under Relations, you can set the relations to take into account in automatic allocation. Under Interference Matrices, you can calculate and take interference matrices into account for the frequency allocation. When the Frequency Allocation dialogue opens, the Take into account check box is disabled because interference matrices are not yet available. For more information on defining and calculating interference matrices for automatic allocation, see "Using Interference Matrices with the AFP" on page 1034. Take neighbours into account: In WiMAX 802.16e documents, select this check box if you want the AFP to take neighbour relations into account for the allocation. For frequency 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 "Planning Neighbours" on page 1022. Take min reuse distance into account: Select this check box if you want the AFP to take relations based on distance into account for the allocation. You can enter the Default radius within which two cells whose channels have a co-channel overlap cannot have the same channel assigned. Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue or in the Cells table). If defined, a cell-specific reuse distance will be used instead of default the value entered here.

6. Under Results, Atoll displays the Total Cost of the current frequency allocation taking into account the parameters set in step 5. You can modify the parameters and click Recalculate Cost to see the change in the total cost. 7. Click Calculate. Atoll begins the process of allocating frequencies. Once Atoll has finished allocating frequencies, the proposed allocation is visible under Results. The Results table contains the following information. Site: The name of the base station. Transmitter: The name of the transmitter. Name: The name of the cell. Initial Channel Number: The channel number of the cell before automatic allocation. Channel Number: The channel number of the cell after automatic allocation. Channel Allocation Status: The value of the Channel Allocation Status of the cell. Initial Preamble Index: The preamble index of the cell before automatic allocation. Preamble Index: The preamble index of the cell after automatic allocation. Initial Segment: The segment of the cell before automatic allocation. Segment: The segment of the cell after automatic allocation. Initial Cell PermBase: The permbase of the cell before automatic allocation. Cell PermBase: The permbase of the cell after automatic allocation. Cost: The cost of the new frequency allocation of the cell. Preamble Index Status: The value of the Preamble Index Status of the cell.

8. Click Commit. The channel numbers are committed to the cells.

Using Interference Matrices with the AFP

In Atoll, the probability of interference between pairs of cells is stored in an interference matrix. An interference matrix can be thought of as the probability that a user in the interfered cell will receive interference higher than a defined threshold. The WiMAX AFP calculates interference matrices in the form of co- and adjacent channel interference probabilities for each interfered and interfering cell pair. The probabilities of interference are stated as percentages of the interfered area. In other words, it is the ratio of the interfered surface area to the best server coverage area of an interfered cell: When Atoll calculates interference matrices, it calculates the value of the preamble C/(I+N) for each pixel of the interfered service area between two cells (the interfered cell and the interfering cell). For co-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. For adjacent channel

1034

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 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 (i.e., 0 dB). To calculate interference matrices: 1. Enter a value for the Quality Margin. 2. Click the Calculate button. Atoll calculates the interference matrices. The calculation progress is displayed in the Event Viewer window. To stop the calculation of interference matrices at any moment, click the Stop button. Interference matrices are calculated using the default calculation resolution set in the Properties dialogue of the Predictions folder. 3. Click the Close button once the interference matrices have been calculated. The Event Viewer window closes. To display details of the calculated interference matrices: 1. Click the Details button. The Interference Matrices Display dialogue appears. This dialogue lists all the interfered and interfering cell pairs and their respective interference probabilities in co- and adjacent channel cases. 2. Click the Close button. The Interference Matrices Display dialogue closes. To delete the calculated interference matrices: 1. Click the Delete button. To take the calculated interference matrices into account: Select the Take into account check box.

10.2.10.1.2

Allocating Frequencies to Cells Manually

When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically, as described in "Automatically Allocating Frequencies to Cells" on page 1034. However, if you want to assign a frequency to one cell or to modify the assigned frequency, you can do it by accessing the properties of the cell. To allocate the frequency to a cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate the frequency. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Select the Cells tab. 4. Select a Frequency Band and Channel Number for the cell. 5. You can set the Channel Allocation Status to Locked if you want to lock the frequency that you assigned. 6. Click OK.

10.2.10.2

Displaying the Frequency Allocation

Once you have allocated frequencies, you can verify several aspects of the allocation. You can display frequencies in several ways: "Using the Search Tool to Display Frequency Allocation" on page 1035. "Displaying Frequency Allocation Using Transmitter Display Settings" on page 1036. "Grouping Transmitters by Frequency" on page 1036. "Analysing the Frequency Allocation Using Coverage Predictions" on page 1037.

Using the Search Tool to Display Frequency Allocation

In Atoll, you can search for frequency bands and channel numbers using the Search Tool. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Frequencies 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 995. To find a frequency band using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Channel tab. 3. Select a Frequency Band from the list of available frequency bands. 4. Set Channel Number to All. 5. Click Search. Transmitters whose cells use the selected frequency band are displayed in red. Transmitters with cells using other frequency bands are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1035

Atoll User Manual To find a channel number using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Channel tab. 3. Select a Frequency Band from the list of available frequency bands. 4. Select the Channel Number from the list of available channel numbers. 5. If you want only want the channel entered in the Channel Number box to be displayed, select the Co-channel Only check box. 6. 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 selected the Co-channel Only 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 Search Tool window. Note: 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 "Defining the Object Type Label" on page 35.

Displaying Frequency Allocation Using Transmitter Display Settings

You can display the frequency allocation per transmitter by using the transmitters display characteristics. To display the frequency allocation on the map: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete Values" as the Display Type and "Cells: Channel Number" as the Field. 6. Click OK. Transmitters will be displayed by channel number. You can also display the frequency band and channel number in the transmitter label or tooltip by selecting "Cells: Frequency Band" and "Cells: Channel Number" from the Label or Tip Text Field Selection dialogue. For information on display options, see "Display Properties of Objects" on page 32.

Grouping Transmitters by Frequency

You can group transmitters on the Data tab of the Explorer window by their frequency bands or channel numbers. To group transmitters by frequency bands or channel numbers: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group By. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: Frequency Band Channel Number Min Reuse Distance Channel Allocation Status

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. 8. 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 the transmitters will be grouped. . The selected parameter is removed from the list of parameters on which

1036

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 9. 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 b. Select a parameter and click to move it up to the desired position. to move it down to the desired position.

10. Click OK to save your changes and close the Group dialogue.

Analysing the Frequency Allocation Using Coverage Predictions

You can create and compare preamble C/(I+N) coverage predictions before and after the automatic frequency allocation in order to analyse and compare the improvements made by the AFP. For more information on creating preamble C/(I+N) coverage predictions, see "Making a Coverage Prediction by C/(I+N) Level" on page 1012. For more information on comparing two coverage predictions, see "Comparing Coverage Predictions: Examples" on page 1002.

10.2.11

Planning Preamble Indexes

In WiMAX 802.16e, 114 preamble indexes are available, numbered from 0 to 113. There are as many pseudo-noise sequences defined in the IEEE specifications. A PN sequence is transmitted on the preamble subcarriers corresponding to each preamble index using BPSK1/2. Mobiles recognize their serving cells by comparing the received PN sequences with the 114 sequences stored in their memory. The preamble index of the serving cell is simply the number of the PN sequence received with the highest power. The preamble index provides the segment number (0, 1, or 2) and the cell permbase (DL_PermBase of the first downlink PUSC zone, also called ID_Cell, which is a value from 0 to 31.) Therefore, the mobile knows which subcarriers to listen to for the FCH, DCD, UCD, DL-MAP, and UL-MAP. Because the cell search and selection depend on the preamble index of the cells, preamble indexes must be intelligently allocated to cells in order to avoid unnecessary interference on the preamble. The subcarriers used for preamble transmission are divided into 3 carrier sets. Preamble carrier sets are defined by the equation: Preamble Carrier Set n = n + 3 k Where n is the segment number (0, 1, or 2), and k is a running index from 0 to 567, 283, 142, and 35 for FFT sizes 2048, 1024, 512, and 128, respectively. Therefore, each preamble carrier set uses every third subcarrier. 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. The procedure for planning preamble indexes for a WiMAX 802.16e project is: "Allocating Preamble Indexes" on page 1037: "Automatically Allocating Preamble Indexes to WiMAX 802.16e Cells" on page 1037. "Allocating Preamble Indexes to WiMAX 802.16e Cells Manually" on page 1038.

"Checking the Consistency of the Preamble Index Plan" on page 1039. "Displaying the Allocation of Preamble Indexes" on page 1039: "Using the Search Tool to Display Preamble Index Allocation" on page 1039. "Displaying Preamble Index Allocation Using Transmitter Display Settings" on page 1040. "Grouping Transmitters by Preamble Index" on page 1040. "Displaying the Preamble Index Allocation Histogram" on page 1041.

10.2.11.1

Allocating Preamble Indexes

Atoll can automatically assign preamble indexes to the cells of a WiMAX 802.16e network according to set parameters. For example, it takes into account the selected cell permbase allocation strategy (free or same cell permbase per site), minimum reuse distance, and any constraints imposed by neighbours. You can also allocate preamble indexes manually to the cells of a WiMAX 802.16e network. In this section, the following methods of allocating preamble indexes are described: "Automatically Allocating Preamble Indexes to WiMAX 802.16e Cells" on page 1037. "Allocating Preamble Indexes to WiMAX 802.16e Cells Manually" on page 1038.

Automatically Allocating Preamble Indexes to WiMAX 802.16e Cells

Atoll enables you to automatically allocate preamble indexes to cells in the current network. To automatically allocate preamble indexes: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Preamble Indexes > Automatic Allocation. The Preamble Index Allocation dialogue appears. 4. If you have access to the WiMAX AFP module, under Allocate, select Preamble Indexes to allocate preamble indexes to cells automatically.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1037

Atoll User Manual 5. Select the Preamble Index Allocation Range. You can choose to allocate preamble indexes from the Entire (0113) range, a Reduced (0-95) range, or you can choose Custom and enter the Excluded Preamble Indexes 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 index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5"). 6. Select the Allocate 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. 7. Under Cell PermBase Allocation Strategy, you can select one of the following automatic allocation strategies (for more information, see the Technical Reference Guide): Free: The preamble index allocation will only be restricted by the segment number allocated to nearby cells. Cell permbases will not necessarily be the same for all the cells of a site. Same per Site: This strategy allocates preamble indexes to cells such that the same cell permbase is assigned to all the cells of a site.

8. Under Relations, you can set the relationships to take into account in automatic allocation. If you have access to the WiMAX AFP module, under Interference Matrices, you can calculate and take interference matrices into account for the preamble index allocation. When the Preamble Index Allocation dialogue opens, the Take into account check box is disabled because interference matrices are not yet available. For more information on defining and calculating interference matrices for automatic allocation, see "Using Interference Matrices with the AFP" on page 1034. Take neighbours into account: In WiMAX 802.16e documents, select this check box if you want Atoll to take neighbour relations into account for the allocation. During preamble index allocation, Atoll will try to allocate different preamble indexes to a cell and all of its neighbours. This means that in an ideal situation, none of a cells neighbours should have the same preamble index as the cell, and no two neighbours of the cell should have the same preamble index either. Atoll can only take neighbour relations into account if neighbours have already been allocated. For information on allocating neighbours, see "Planning Neighbours" on page 1022. Take min reuse distance into account: Select this check box if you want Atoll to take relations based on distance into account for the allocation. You can enter the Default radius within which two cells whose channels have a co-channel overlap cannot have the same preamble index assigned. Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue or in the Cells table). If defined, a cell-specific reuse distance will be used instead of default the value entered here.

9. Under Results, Atoll displays the Total Cost of the current preamble index allocation taking into account the parameters set in step 8. You can modify the parameters and click Recalculate Cost to see the change in the total cost. 10. Click Calculate. Atoll begins the process of allocating preamble indexes. Once Atoll has finished allocating preamble indexes, the indexes are visible under Results. The Results table contains the following information. Site: The name of the base station. Transmitter: The name of the transmitter. Name: The name of the cell. Initial Preamble Index: The preamble index of the cell before automatic allocation. Preamble Index: The preamble index of the cell after automatic allocation. Initial Segment: The segment of the cell before automatic allocation. Segment: The segment of the cell after automatic allocation. Initial Cell PermBase: The permbase of the cell before automatic allocation. Cell PermBase: The permbase of the cell after automatic allocation. Cost: The cost of the new preamble index allocation of the cell. Preamble Index Status: The value of the Preamble Index Status of the cell.

11. Click Commit. The preamble indexes are committed to the cells.

Allocating Preamble Indexes to WiMAX 802.16e Cells Manually

When you allocate preamble indexes to a large number of cells, it is easiest to let Atoll allocate preamble indexes automatically, as described in "Automatically Allocating Preamble Indexes to WiMAX 802.16e Cells" on page 1037. 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 802.16e cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a preamble index. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears.

1038

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 3. Select the Cells tab. 4. Enter a Preamble Index in the cells column. 5. You can set the Preamble Index Status to Locked if you want to lock the preamble index that you assigned. 6. Click OK.

10.2.11.2

Checking the Consistency of the Preamble Index Plan

Once you have completed allocating preamble indexes, you can verify whether the allocated preamble indexes respect the specified constraints and relations by performing an audit of the plan. The preamble index audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Preamble Indexes > Audit. The Preamble Index Audit dialogue appears. 4. In the Preamble Index Audit dialogue, select the allocation criteria that you want to verify: Distance: If you select the Distance check box and set a reuse distance, Atoll will check for and list cells that do not respect this reuse distance. Neighbours: If you select the Neighbours check box, Atoll will check that no cell has the same preamble index as any of its neighbours, and that no two neighbours of a cell have the same preamble index. The report will list any cell that does have the same preamble index as one of its neighbours. Same Cell PermBase at a Site: If you select the Same Cell PermBase at a Site check box, Atoll will check for and list base stations whose cells have preamble indexes that correspond to different cell permbases. Segments of Co-transmitter Cells: If you select the Segments of Co-transmitter Cells check box and select Different, Atoll will check for and list co-transmitter cells that do not match the criterion, i.e., the cotransmitter cells with preamble indexes that correspond to the same segment numbers. If you select Same, Atoll will check for and list co-transmitter cells with preamble indexes that correspond to different segment numbers. Segments of Co-site Cells: If you select the Segments of Co-site Cells check box and select Different, Atoll will check for and list co-site cells with preamble indexes that do not match the criterion, i.e., the co-site cells with preamble indexes that correspond to the same segment numbers. If you select Same, Atoll will check for and list co-site cells with preamble indexes that correspond to the same segment numbers.

5. Click OK. Atoll displays the results of the audit in a text file called IndexCheck.txt, which it opens at the end of the audit. For each selected criterion, Atoll gives the number of detected inconsistencies and details for each inconsistency.

10.2.11.3

Displaying the Allocation of Preamble Indexes

Once you have completed allocating preamble indexes, you can verify several aspects of preamble index allocation. You can display preamble indexes in several ways: "Using the Search Tool to Display Preamble Index Allocation" on page 1039. "Displaying Preamble Index Allocation Using Transmitter Display Settings" on page 1040. "Grouping Transmitters by Preamble Index" on page 1040. "Displaying the Preamble Index Allocation Histogram" on page 1041.

Using the Search Tool to Display Preamble Index Allocation

In Atoll, you can search for preamble indexes, segment numbers, and cell permbases using the Search Tool. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Preamble indexes 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 995. To find a preamble index using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Segment tab. 3. Select Preamble Index. 4. Enter a Preamble Index. 5. Click Search. Transmitters whose cells use the entered preamble index are displayed in red. Transmitters with cells that use other preamble indexes are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window. Note: 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 "Defining the Object Type Label" on page 35.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1039

Atoll User Manual To find a segment using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Segment tab. 3. Select Segment. 4. Select the segment to search for, i.e., All, 0, 1, or 2. 5. Click Search. When you select a specific segment number, transmitters whose cells use the selected segment number are displayed in red. Transmitters with cells that use other segments are displayed as grey lines. When you choose to search for all segment numbers, 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. Note: Transmitters with more than one cell may use different segments in different cells. Therefore, the search for all segment numbers is only valid for single-cell transmitters.

To restore the initial transmitter colours, click the Reset Display button in the Search Tool window. To find a cell permbase using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Segment tab. 3. Select Cell PermBase. 4. Enter a Cell PermBase. 5. Click Search. Transmitters whose cells use the entered cell permbase are displayed in red. Transmitters with cells that use other cell permbases are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.

Displaying Preamble Index Allocation Using Transmitter Display Settings

You can display preamble index allocation on transmitters by using the transmitters display characteristics. To display preamble index allocation on the map: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete Values" as the Display Type and "Cells: Preamble Index" as the Field. 6. Click OK. Transmitters will be displayed by preamble index. You can also display the preamble index in the transmitter label or tooltip by selecting "Cells: Preamble Index" from the Label or Tip Text Field Definition dialogue. For information on display options, see "Display Properties of Objects" on page 32.

Grouping Transmitters by Preamble Index

You can group transmitters on the Data tab of the Explorer window by their preamble index or their reuse distance. To group transmitters by preamble index: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: Preamble Index Min Reuse Distance Preamble Index Status

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.

1040

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 8. 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 the transmitters will be grouped. . The selected parameter is removed from the list of parameters on which

9. 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 b. Select a parameter and click to move it up to the desired position. to move it down to the desired position.

10. Click OK to save your changes and close the Group dialogue.

Displaying the Preamble Index Allocation Histogram

You can use a histogram to analyse the use of allocated preamble indexes in a network. The histogram represents the preamble indexes as a function of the frequency of their use. To display the preamble index histogram: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Preamble Indexes > Index Distribution. The Distribution Histograms dialogue appears. Each bar represents a preamble index, its height depending on the frequency of its use. 4. Move the pointer over the histogram to display the frequency of use of each preamble index. The results are highlighted simultaneously in the Detailed Results list.

10.3

Studying Network Capacity

Interference is the major limiting factor in the performance of WiMAX networks. It has been recognized as the major bottleneck in network capacity and is often responsible for poor performance. Frequency reuse means that in a given coverage area there are several cells that use a given set of frequencies. The cells that use the same frequency are called co-channel cells, and the interference from users with the same channel in the other co-channel cells is called co-channel interference. Unlike thermal noise which can be overcome by increasing the signal-to-noise ratio (SNR), co-channel interference cannot be countered by simply 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 WiMAX 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 minimized 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, 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 or subscriber lists must be provided. Once services and users have been modelled and traffic maps and subscriber lists have been created, you can make simulations of the network traffic. In this section, the following are explained: "Defining Multi-service Traffic Data" on page 1041. "Creating a Traffic Map" on page 1042. "Exporting a Traffic Map" on page 1050. "Working with a Subscriber Database" on page 1051. "Calculating and Displaying Traffic Simulations" on page 1054. "Making Coverage Predictions Using Simulation Results" on page 1068.

10.3.1

Defining Multi-service Traffic Data

The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1041

Atoll User Manual using the WiMAX Radio Bearer table. For information on defining radio bearers, see "Defining WiMAX Radio Bearers" on page 1145. Services: Services are the various services, such as VoIP, FTP download, etc., 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 1007. Mobility type: In WiMAX, 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 1008. 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 on-board navigation device. For information on modelling terminals, see "Modelling Terminals" on page 1008.

10.3.2

Creating a Traffic Map

The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for WiMAX projects. Sector traffic map User profile traffic map User density traffic map (number of users per km2)

These maps can be used for 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 . For more information, see "Creating a Sector Traffic Map" on page 1042. 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 traffic maps, where each pixel has an assigned environment class, are both supported. For more information, see "Importing a User Profile Traffic Map" on page 1045, "Importing a User Profile Environment Based Traffic Map" on page 1046 and "Creating a User Profile Environment Based Traffic Map" on page 1047. User density traffic maps (number of users per km2) can be used if you have population-based traffic data, or 2G network statistics. Each pixel has a user density assigned. For more information, see "Creating User Density Traffic Maps (No. Users/km2)" on page 1048, "Importing a User Density Traffic Map" on page 1048, "Converting 2G Network Traffic" on page 1050 and "Exporting Cumulated Traffic" on page 1050.

10.3.2.1

Creating a Sector Traffic Map

This section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the uplink and in the downlink or the number of users per activity status . A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 995. To create a sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector Traffic Map. 5. Select the type of traffic information you want to input. You can choose between Throughputs in Uplink and Downlink or Number of Users per Activity Status. 6. Click the Create button. The Sector Traffic Map dialogue appears. Note: 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 another Atoll document.

7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 8. Enter the data required in the Sector Map dialogue: If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and downlink for each sector and for each listed service. If you have selected Number of Users per Activity Status, enter the number of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each service.

1042

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Note:

You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 63.

9. Click OK. The Sector Traffic Map Properties dialogue appears. 10. Select the Traffic tab. Enter the following: a. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. b. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. c. Under Clutter Distribution, for each clutter class, enter: A weight to spread the traffic over the vector. The percentage of indoor users. An additional loss will be counted for indoor users during Monte-Carlo simulations.

11. 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 the sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 5. Select the Traffic tab. 6. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 7. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 8. Under Clutter Distribution, for each clutter class, enter a weight to spread the traffic over the clutter classes and the percentage of indoor users. 9. Click OK. Atoll saves the traffic map with its modifed values. You can update the information, throughput demands and the number of users, on the map afterwards. You can update sector traffic maps. You must first recalculate the coverage prediction by transmitter. For more information, see "Making a Coverage Prediction by Transmitter" on page 995. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map that you want to update. The context menu appears. 4. Select Update from the context menu. The Sector Traffic Map dialogue appears. 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. 5. Click OK. The Sector Traffic Map Properties dialogue appears. 6. 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 1049.

10.3.2.2

Creating a User Profile Traffic Map

The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There may also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments. A user profile models the behaviour of different user categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for calls of the type "voice") or uplink and downlink volume (for calls of the type "data"). Environment classes are used to describe the distribution of users 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 users with the same profile per km).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1043

Atoll User Manual The sections "Importing a User Profile Traffic Map" on page 1045, "Importing a User Profile Environment Based Traffic Map" on page 1046 and "Creating a User Profile Environment Based Traffic Map" on page 1047 describe how to use traffic data from the marketing department in Atoll to model traffic. In this section, the following are explained: "Modelling User Profiles" on page 1044. "Modelling Environments" on page 1044.

Modelling User Profiles

You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user may be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the WiMAX Parameters folder.

3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. Note: 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.

5. You can modify the following parameters: Name: Enter a descriptive name for the user profile. Service: Select a service from the list. For information on services, see "Modelling Services" on page 1007. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 1008. Calls/Hour: For services of the type "voice," enter the average number of calls per hour for the service. The calls per hour is used to calculate the activity probability. For services of the type "voice," one call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each. For services of the type "data," 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 services of the type "data," however, he may 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 may be downloading web pages and other times he may not be using the application, or he may be browsing local files, but the session is still considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time. Note: 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 (sec.): For services of the type "voice," enter the average duration of a call in seconds. For services of the type "data," this field is left blank. UL Volume (KBytes): For services of the type "data," enter the average uplink volume per session in kilobytes. DL Volume (KBytes): For services of the type "data," enter the average downlink volume per session in kilobytes.

6. Click OK.

Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of users with the same profile per km). To get an appropriate user distribution, you can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers for each clutter class. In a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss. To create or modify a WiMAX environment: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the WiMAX Parameters folder.

3. Right-click the Environments folder. The context menu appears. 4. Select New from the context menu. The Environments New Element Properties dialogue appears.

1044

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Note:

You can modify the properties of an existing environment by right-clicking the environment in the Environments folder and selecting Properties from the context menu.

5. Click the General tab. 6. Enter a Name for the new WiMAX environment. 7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility combination that this WiMAX environment will describe: User: Select a user profile. Mobility: Select a mobility type. Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination of user profile and mobility type.

8. Click the Clutter Weighting tab. 9. For each clutter class, enter a weight that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

For example: An area of 10 km with a user density of 100/km. Therefore, in this area, there are 1000 users. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in the Building clutter class. 10. If you wish you can specify a percentage of indoor users for each clutter class. During a Monte Carlo simulation, an additional loss will be added to the indoor users path loss. 11. Click OK.

10.3.2.2.1

Importing a User Profile Traffic Map

User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscriberskm, or polygons with a number of subscriberskm) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Densities from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1047.

7. Select the file to import. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab (see Figure 10.551). 12. Under Traffic Fields, you can specify the user profiles to be considered, their mobility type (kmh), and their density. If the file you are importing has this data, you can define the traffic characteristics by identifying the corresponding fields in the file. If the file you are importing does not have data describing the user profile, mobility, or density, you can assign values. When you assign values, they apply to the entire map.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1045

Atoll User Manual

Figure 10.551: Traffic map properties dialogue - Traffic tab Define each of the following: User Profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the WiMAX Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the WiMAX Parameters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points. Important: 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 WiMAX Parameters folder of the Data tab. If the imported user profile or mobility does not match, Atoll will display a warning. 13. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

14. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss will be added to the indoor users path loss. 15. Click OK to finish importing the traffic map.

10.3.2.2.2

Importing a User Profile Environment Based Traffic Map

Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map.

1046

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 5. Select User Profile Environments from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1047.

7. Select the file to import. The file must be in one of the following supported 8 bit raster formats: TIF, JPEG 2000, BIL, IST, BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Description tab. In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the Code column. 12. For each Code, select the environment it corresponds to from the Name column. The environments available are those available in the Environments folder, under WiMAX Parameters on the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 1044. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 32. 14. Click OK.

10.3.2.2.3

Creating a User Profile Environment Based Traffic Map

Atollenables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 10.552).

Draw Map

Delete Map

Figure 10.552: Environment Map Editor toolbar 7. Select the environment class from the list of available environment classes. 8. Click the Draw Polygon button ( 9. Click the Delete Polygon button ( ) to draw the polygon on the map for the selected environment class. ) and click the polygon to delete the environment class polygon on the map.

10. Click the Close button to close the Environment Map Editor toolbar and end editing.

10.3.2.2.4

Displaying Statistics on a User Profile Environment Traffic Map

You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1047

Atoll User Manual The Statistics window lists the surface (Si in km) and the percentage of surface (% of i) for each environment Si class "i" within the focus zone. The percentage of surface is given by: % of i = ------------- 100 Sk

You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.

10.3.2.3

Creating User Density Traffic Maps (No. Users/km2)

User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. In this section, the following ways of creating a user density traffic map are explained: "Importing a User Density Traffic Map" on page 1048 "Creating a User Density Traffic Map" on page 1049.

User density traffic maps may be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. for more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 1049.

10.3.2.3.1

Importing a User Density Traffic Map

The user density traffic map defines the density of users per pixel. For a traffic density of X users per km, Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic maps properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (No. Users/km2). 5. Select the type of traffic information you input: Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity.

6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1047.

7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP, PlaNET, TIF, JPEG 2000, ISTAR, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab. 12. Select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink. 13. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. 14. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 15. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.

1048

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks An additional loss will be counted for indoor users during Monte Carlo simulations. You do not have to define a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel. 17. Click OK. Atoll creates the traffic map in the Traffic folder.

10.3.2.3.2

Creating a User Density Traffic Map

Atollenables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (Number of users per km2). 5. Select the type of traffic information you input. You can choose from: Active in Uplink: Select Active in Uplink if the map you are importing provides the density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides the density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides the density of users with both uplink and downlink activity.

6. Click the Create button. The traffic maps property dialogue appears. 7. Select the Traffic tab. 8. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. 9. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 10. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 11. Under Clutter Distribution, enter the percentage of indoor users for each clutter class. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for user density traffic maps because the traffic is provided in terms of user density per pixel. 12. Click OK. Atoll creates the traffic map in the Traffic folder. 13. Right-click the traffic map. The context menu appears. 14. Select Edit from the context menu. 15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit contours, see "Editing Polygons, Lines, and Points" on page 46. Atoll creates an item called Density values in the User Density Map folder. 16. Right-click the item. The context menu appears. 17. Select Open Table from the context menu. 18. In the table, enter a traffic density value (i.e., the number of users per km2) for each contour you have drawn. 19. Right-click the item. The context menu appears. 20. Select Edit from the context menu to end editing.

10.3.2.3.3

Creating User Density Traffic Maps from Sector Traffic Maps

You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps 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. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map from which you want to create user density traffic maps. The context menu appears. 4. Select Create density maps from the context menu. Atoll creates as many user density traffic maps as the number of services present in the sector traffic map. The user density map files use the resolution of the coverage prediction used for the sector traffic map and are embedded in the document.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1049

Atoll User Manual

10.3.2.4

Converting 2G Network Traffic

Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as user density traffic maps into your WiMAX document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 1050, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1048. To import a 2G traffic map into a WiMAX document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 254. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 1050. 3. Import the traffic exported in step 2 to your WiMAX document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1048.

10.3.2.5

Exporting Cumulated Traffic

Atoll allows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: The Entire Project Area: This option allows you to export the cumulated traffic over the entire project. The Computation Zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone.

7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains at "0" and no data will be exported. 8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic data to be exported. Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal. Service: Select the service that will be exported, or select "Voice services" to export voice traffic, or select "Data services" to export data traffic. Mobility: Select the mobility type that will be exported or select "All" to export all mobility types. Activity: Select one of the following: All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status. Uplink: Select Uplink to export mobiles active in the uplink only. Downlink: Select Downlink to export mobiles active in the downlink only. Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.

9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the cumulated traffic. 10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.

10.3.3

Exporting a Traffic Map

To export a traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save.

1050

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks If you are exporting a raster traffic map, you have to define: The Export Region: Entire Project Area: Saves the entire traffic map. Only Pending Changes: Saves only the modifications made to the map. Computation Zone: Saves only the part of the traffic map inside the computation zone.

An export Resolution.

10.3.4

Working with a Subscriber Database

The WiMAX BWA module includes a subscriber database for modelling fixed user distributions in a network. A subscriber database can be used for Fixed Wireless Access (FWA) networks, like the IEEE 802.16d. The subscriber database consists of subscriber lists. You can create subscriber lists in Atoll by adding subscribers to the list using the mouse, or by copying data from any other source such as a spreadsheet. You can also directly import subscriber lists in Atoll from text (TXT) and comma separated value (CSV) files. Atoll can allocate reference or serving base stations (cells) to subscribers. You can also have the subscriber antenna oriented towards its serving cell to decrease interference. The automatic server allocation performs a number of calculations on the subscriber locations. In this section, the following are explained: "Creating a Subscriber List" on page 1051. "Performing Calculations on Subscriber lists" on page 1054.

10.3.4.1

Creating a Subscriber List

You create subscribers in Atoll in two steps. First, you create a subscriber list, and then you add subscribers to the list. You can add subscribers to the list directly on the map using the mouse. For more information, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1053. If you need to create a large number of subscribers, Atoll allows you to import them from another Atoll document or from an external source. For more information, see "Importing a Subscriber List" on page 1053. To create a subscriber list: 1. Click the Data tab in the Explorer window. 2. Right-click the Subscribers folder. The context menu appears. 3. Select New List from the context menu. The Subscriber List N Properties dialogue appears (see Figure 10.553), where N is an incremental digit.

Figure 10.553: New subscriber list dialogue - General tab 4. Select the General tab. The following options are available: Name: The name of the subscriber list. You can change the name of the list if desired. Coordinate System: The current coordinate system used by the subscriber list. You can change the coordinate system of the list by clicking the Change button. Sort: Click the Sort button to sort the data in the subscriber list. For information on sorting, see "Sorting Data" on page 73. Filter: Click the Filter button to filter the data in the subscriber list. For information on filtering, see "Filtering Data" on page 74.

5. Click the Display tab. You can modify how subscribers added to the list are displayed. For information on defining the display properties, see "Display Properties of Objects" on page 32. 6. Click OK. Atoll creates a new subscriber list. The following parameters are available by default in a new subscriber list:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1051

Atoll User Manual ID: The subscriber ID in the subscriber list. It is an automatically created identification number. X and Y coordinates: The geographical coordinates of the subscriber. A subscribers location is always fixed. Height: The altitude of the subscriber antenna with respect to the ground (DTM). Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose contents are automatically updated. Name: You can assign a descriptive name to each subscriber. User Profile: A user profile defines the traffic demand characteristics of subscribers. Atoll determines the terminal used, the service accessed, and the activity status of subscribers during Monte Carlo simulations according to the information in the user profiles. For more information, see "Modelling User Profiles" on page 1044. Terminal: The default terminal (CPE) is the user equipment with an antenna, WiMAX equipment, and noise characteristics. The properties of this terminal are taken into consideration when performing calculations on the subscriber list. Service: The service that the subscriber accesses by default. The properties of this service are taken into consideration when performing calculations on the subscriber list. Mobility: The mobility type associated with the subscriber. It is used to identify the thresholds and graphs to be used for the subscriber in calculations. Indoor: This field indicates whether the subscriber is indoor or outdoor. Azimuth: The orientation of the subscriber antenna in the horizontal plane. Azimuth is always considered with respect to the north. You can either define this value manually or let Atoll calculate it for the subscriber. Atoll points the subscriber antenna towards its serving base station. Mechanical Downtilt: The orientation of the subscriber antenna in the vertical plane. Mechanical downtilt is positive when it is downwards and negative when upwards. You can either define this value manually or let Atoll calculate it for the subscriber. Atoll points the subscriber antenna towards its serving base station. Lock Status: You can choose to lock the subscriber antenna orientation and serving transmitter. Use this option if you do not want Atoll to change the assigned server or the antenna orientation. Serving Base Station: The serving transmitter of the subscriber. You can either define this value manually or let Atoll calculate it for the subscriber. The serving base station is determined according to the received preamble signal level from the cell with the highest preamble power. Reference Cell: The reference cell of the serving transmitter of the subscriber. You can either define this value manually or let Atoll calculate it for the subscriber. If more than one cell of the serving base station covers the subscriber, the one with the lowest layer is selected as the reference cell. Path Loss (dB): The path loss calculated for the subscriber. Distance: The distance of the subscriber from its serving base station. This is a non-editable field whose contents are automatically updated. Received Preamble Power (DL) (dBm): The preamble signal level received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. Received Traffic Power (DL) (dBm): The traffic signal level received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. Received Pilot Power (DL) (dBm): The pilot signal level received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. Preamble Total Noise (I+N) (DL) (dBm): The sum of the preamble interference and noise experienced at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Traffic Total Noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Preamble C/(I+N) (DL) (dB): The preamble C/(I+N) at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Traffic C/(I+N) (DL) (dB): The traffic C/(I+N) at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Pilot C/(I+N) (DL) (dB): The pilot C/(I+N) at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Bearer (DL): The highest WiMAX bearer available for the traffic C/(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Permutation Zone (DL) (WiMAX 802.16e): The downlink permutation zone allocated to the subscriber. BLER (DL): The Block Error Rate read from the subscribers terminal types WiMAX equipment for the traffic C(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. 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 subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Effective MAC Channel Throughput (DL) (kbps): The effective MAC channel throughput attainable using the highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Received Power (UL) (dBm): The signal level received at the serving transmitter from the subscriber terminal in the uplink. This value is generated by Atoll during the calculations on subscriber lists. Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists. C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists. Bearer (UL): The highest WiMAX bearer available for the C/(I+N) level at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists. Permutation Zone (UL) (WiMAX 802.16e): The uplink permutation zone allocated to the subscriber.

1052

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks BLER (UL): The Block Error Rate read from the reference cells WiMAX equipment for the C/(I+N) level at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists. Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink. Transmission Power (UL) (dBm): The transmission power of the subscribers terminal after power control in the uplink. This value is generated by Atoll during the calculations on subscriber lists. 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. This value is generated by Atoll during the calculations on subscriber lists. Peak MAC Channel Throughput (UL) (kbps): The maximum MAC channel throughput attainable using the highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists. Effective MAC Channel Throughput (UL) (kbps): The effective MAC channel throughput available using the highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.

For information on how to select the columns to display in the subscriber list table, see "Selecting the Columns to Display in the Subscriber Lists" on page 1054. For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations on Subscriber lists" on page 1054. You can now move the pointer over the map and click once to place a new subscriber at the location of the pointer. Press ESC or click the normal pointer button ( ), to finish adding subscribers on the map. For information on adding subscribers to a list, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1053. You can open the subscriber list table containing all the subscribers and their parameters. To open the subscriber list table: 1. Click the Data tab in the Explorer window. 2. Right-click the Subscribers folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the ASCII text file you want to open and click Open. The Import dialogue appears. In the Import dialogue, you can change the reference coordinate system for the file being imported by selecting the system from the Coordinates list. Atoll will convert the coordinates of the list to the coordinate system of the document upon import. For information on working with data tables, see "Working with Data Tables" on page 53.

10.3.4.1.1

Adding Subscribers to a Subscriber List Using the Mouse

You can use the mouse to add subscribers to an existing subscriber list. Atoll applies the default parameters defined in the Table tab of the subscriber list Properties dialogue to all the subscribers you add to the list. For more information on the Table tab, see "Creating a Subscriber List" on page 1051. To add subscribers to a subscriber list using the mouse: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Subscribers folder.

3. Right-click the subscriber list to which you want to add subscribers. The context menu appears. 4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode ( 5. Move the mouse over the Map window, and click once to add each subscriber. 6. Press ESC or click the normal pointer button ( ) to finish adding subscribers. ).

Tip:

To place subscribers more accurately, before clicking the map, you can zoom in on the map. For information on using the zooming tools, see "Changing the Map Scale" on page 38.

10.3.4.1.2

Importing a Subscriber List

You can also import subscriber lists from text files (TXT) or comma separated value files (CSV), including Microsoft Excel files exported in CSV format. To import a subscriber list: 1. Click the Data tab in the Explorer window. 2. Right-click the Subscribers folder. The context menu appears. 3. Select Import from the context menu. For more information on importing table data, see "Importing Tables from Text Files" on page 63.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1053

Atoll User Manual

Note:

You can also export subscriber lists. For information on exporting table data, see "Exporting Tables to Text Files" on page 61.

10.3.4.1.3

Selecting the Columns to Display in the Subscriber Lists

From the columns listed in "Creating a Subscriber List" on page 1051, you can select the ones to display in the Properties dialogue of the Subscribers folder. To select the columns to display in subscriber lists: 1. Click the Data tab in the Explorer window. 2. Right-click the Subscribers folder. The context menu appears. 3. Select Properties from the context menu. The Subscribers Properties dialogue appears. 4. Click the Column Selection tab. 5. Under Configuration, you can Open an existing configuration of the columns to display, Save the current settings in an exsting configuration file, or Save as a new configuration file. 6. Select the columns you want to display: a. To display a column, select the column in the Available Columns list and click Columns to Display list. b. To hide a column, select the column in the Columns to Display list and click c. To change the order of the columns, select a column and click 7. Click OK to close the Subscribers Properties dialogue. or . to move it to the

to move it up or down in the list.

10.3.4.2

Performing Calculations on Subscriber lists

You can perform calculations on subscriber lists without having to carry out simulations first. Atoll does not base calculations performed on subscriber lists on the path loss matrices calculated for transmitters. This is because the path loss matrices are calculated for a given receiver height (1.5 m by default) defined in the Properties dialogue of the Predictions folder, but each subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates the path loss, received power, and other output for each subscriber when you perform calculations based on subscribers. Atoll includes an Automatic Server Allocation feature which performs the following for all the subscribers in a list. To perform calculations on a subscriber list: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Subscribers folder.

3. Right-click the subscriber list on which you want to perform calculations. The context menu appears. 4. Select Calculations > Automatic Server Allocation from the context menu. The Automatic Server Allocation dialogue appears. If you want the calculations 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 for signal level calculations is based on the model standard deviation, and the shadowing margin for C/(I+N) calculations is based on the C/I standard deviation. 5. Click Calculate. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. 6. Once the calculations are finished, click Close to close the Event Viewer. 7. Click Commit to store the results in the subscriber list. For the list of results that are available after the calculations, see "Creating a Subscriber List" on page 1051.

10.3.5

Calculating and Displaying Traffic Simulations

To plan and optimise WiMAX networks, you will need to study the network capacity and to study the network coverage taking into account realistic user distribution and traffic demand scenarios. 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 networks 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.

1054

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks In this section, the following are explained: "WiMAX Traffic Simulation Algorithm" on page 1055. "Creating Simulations" on page 1056. "Displaying the Traffic Distribution on the Map" on page 1057. "Displaying the Results of a Single Simulation" on page 1061. "Updating Cell Load Values With Simulation Results" on page 1067. "Estimating a Traffic Increase" on page 1068.

10.3.5.1

WiMAX Traffic Simulation Algorithm

Figure 10.554 shows the WiMAX simulation algorithm. The simulation process in WiMAX consists of the following steps: 1. Mobile Generation and Distribution Simulations require traffic data, such as traffic maps (raster, vector, or live traffic data) or subscriber lists. Atoll generates a user distribution for each simulation using a Monte Carlo algorithm. This user distribution is based on the traffic data input and is weighted by a Poisson distribution. 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. The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the subscriber locations.

Figure 10.554: WiMAX simulation algorithm 2. Best Server Determination Atoll determines the best server for each mobile based on the preamble signal level in the downlink. The best serving transmitter is determined according to the received preamble signal level from the cell with the highest preamble power. If more than one cell covers the mobile, the one with the lowest layer is selected as the serving (reference) cell. 3. Downlink Calculations

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1055

Atoll User Manual The downlink calculations include the calculation of downlink preamble and traffic C/(I+N), determination of the best available bearer for the traffic C/(I+N), allocation of resources (RRM), and calculation of user throughputs. Segmentation is performed if the frame configuration, selected for a cell, supports segmentation. Interference calculation is based on the probabilities of collision between segments. 4. Uplink Calculations The uplink calculations include the calculation of uplink C/(I+N), determination of the best available bearer for the C/(I+N), uplink power control and subchannelisation depending on the bearer, allocation of resources (RRM), update of uplink noise rise values for cells, and calculation of user throughputs. 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: a. It determines the total amount of resources in each cell. b. It 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. It sorts the users in decreasing order by service priority d. It 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, the scheduler allocates resources to the users with maximum throughput demands according to the used scheduling algorithm. Note: 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, an active user can be connected in the direction corresponding to his activity status if: he has a best server assigned (step 2.), he has a bearer in the direction corresponding to his activity status (step 3. and step 4.), he is among the users selected by the scheduler for resource allocation (step 5.), and he is not rejected due to resource saturation (step 5.).

If a user is rejected during step 2., the cause of rejection is "No Coverage". If a user is rejected during step 3. or step 4., the cause of rejection is "No Service". If a user is rejected during step 5., the cause of rejection can either be "Scheduler Saturation," i.e., the user is not among the users selected for resource allocation, or he can be rejected due to "Resource Saturation," i.e., 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.

10.3.5.2

Creating Simulations
In Atoll, simulations enable you to study the capacity of your WiMAX network and model the different network regulation mechanisms, such as power control, subchannelisation, and scheduling, in order to optimise network performance and maximise capacity. You can create one simulation or a group of simulations that will be performed in sequence. You must have at least one traffic map or subscriber list in your document to be able to perform simulations. To create a simulation or a group of simulations: 1. Click the Data tab in the Explorer window. 2. Right-click the WiMAX Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name for this simulation or group of simulations. 5. Under Execution on the General tab, you can set the following parameters: Number of Simulations: Enter the number of simulations to be carried out. All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window.

6. Under Load Constraints on the General tab, you can set the constraints that Atoll must respect during the simulation: 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 ) beside the use the maximum uplink traffic load as defined in the properties for each cell, click the button ( box and select Defined per Cell.

1056

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 7. You can enter some Comments if you wish. 8. On the Source Traffic tab, enter the following: Global Scaling Factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). Select Traffic Maps to be Used: Select the traffic maps you want to use for the simulation. Select Subscriber Lists to be Used: Select the subscriber lists you want to use for the simulation. You can select traffic maps of any type. However, if you have several different types of traffic maps and want to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 1042. Note: When you perform simulations for subscriber lists, Atoll does not base the calculations on subscriber lists on the path loss matrices calculated for transmitters. This is because the path loss matrices are calculated for a given receiver height (1.5 m by default), but each subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates the path loss, received power, and other output, for each subscriber when you perform simulations on subscribers.

9. On the Advanced tab, enter the following: 10. Under Generator Initialisation, enter an integer as the generator initialisation value. If you enter "0," the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value.

Tip:

Using the same generated user and shadowing error distribution for several simulations can be useful when you want to compare the results of several simulations where only one parameter changes.

11. Under Convergence, enter the following parameters: Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. 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.

12. Once you have defined the simulation, you can run it immediately or you can save it to run it later: Run: Click Run to save the defined simulation and run it immediately OK: Click OK to save the defined simulation without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. You can now use the results from completed simulations for WiMAX coverage predictions. For more information on using simulation results in coverage predictions, see "Making Coverage Predictions Using Simulation Results" on page 1068.

10.3.5.3

Displaying the Traffic Distribution on the Map

Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to activity status, service, reference cell, or throughputs. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 33. In this section are the following examples of traffic distribution: "Displaying the Traffic Distribution by Activity Status" on page 1058. "Displaying the Traffic Distribution by Connection Status" on page 1058. "Displaying the Traffic Distribution by Service" on page 1058. "Displaying the Traffic Distribution by Throughput" on page 1059. "Displaying the Traffic Distribution by Uplink Transmission Power" on page 1060. "Displaying the Traffic Distribution by the Uplink Allocated Bandwidth" on page 1060.

Tip:

You can make the traffic distribution easier to see by hiding geographic data and coverage predictions. For information, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1057

Atoll User Manual

10.3.5.3.1

Displaying the Traffic Distribution by Activity Status

In this example, the traffic distribution is displayed by the activity status. To display the traffic distribution by the activity status: 1. Click the Data tab in the Explorer window. 2. Right-click the WiMAX Simulations folder. The context menu appears. 3. Select Properties from the context menu. The WiMAX Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "Activity Status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 10.555).

Figure 10.555: Displaying the traffic distribution by activity status

10.3.5.3.2

Displaying the Traffic Distribution by Connection Status

In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Click the Data tab in the Explorer window. 2. Right-click the WiMAX Simulations folder. The context menu appears. 3. Select Properties from the context menu. The WiMAX Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "Connection Status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 10.556).

Figure 10.556: Displaying the traffic distribution by connection status

10.3.5.3.3

Displaying the Traffic Distribution by Service

In this example, the traffic distribution is displayed by service.

1058

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks To display the traffic distribution by service: 1. Click the Data tab in the Explorer window. 2. Right-click the WiMAX Simulations folder. The context menu appears. 3. Select Properties from the context menu. The WiMAX Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 10.557).

Figure 10.557: Displaying the traffic distribution by service

10.3.5.3.4

Displaying the Traffic Distribution by Throughput

In this example, the traffic distribution is displayed by throughput. To display the traffic distribution by throughput: 1. Click the Data tab in the Explorer window. 2. Right-click the WiMAX Simulations folder. The context menu appears. 3. Select Properties from the context menu. The WiMAX Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value Intervals" as the Display Type and one of the following throughput types as the Field: In the downlink: - Peak MAC, effective MAC, or application channel throughput - Peak MAC, effective MAC, or application cell capacity - Peak MAC, effective MAC, or application user throughput In the uplink: - Peak MAC, effective MAC, or application channel throughput - Peak MAC, effective MAC, or application cell capacity - Peak MAC, effective MAC, or application allocated bandwidth throughput - Peak MAC, effective MAC, or application user throughput

5. Click OK. The traffic distribution is now displayed by throughput (see Figure 10.558).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1059

Atoll User Manual

Figure 10.558: Displaying the traffic distribution by throughput

10.3.5.3.5

Displaying the Traffic Distribution by Uplink Transmission Power

In this example, the traffic distribution is displayed by the uplink transmission power of the mobiles. You can analyse the effect of the uplink power control. To display the traffic distribution by uplink transmission power: 1. Click the Data tab in the Explorer window. 2. Right-click the WiMAX Simulations folder. The context menu appears. 3. Select Properties from the context menu. The WiMAX Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value intervals" as the Display Type and "Transmission Power (UL) (dBm)" as the Field. 5. Click OK. The traffic distribution is now displayed by uplink transmission power (see Figure 10.559).

Figure 10.559: Displaying the traffic distribution by uplink transmission power

10.3.5.3.6

Displaying the Traffic Distribution by the Uplink Allocated Bandwidth

In this example, the traffic distribution is displayed by the uplink allocated bandwidth, i.e., the number of subchannels. You can analyse the effect of the uplink subchannelisation. To display the traffic distribution by the uplink allocated bandwidth: 1. Click the Data tab in the Explorer window. 2. Right-click the WiMAX Simulations folder. The context menu appears. 3. Select Properties from the context menu. The WiMAX Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value intervals" as the Display Type and "Allocated Bandwidth (UL) (No. of Subchannels)" as the Field.

1060

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 5. Click OK. The traffic distribution is now displayed by the number of uplink subchannels (see Figure 10.560).

Figure 10.560: Displaying the traffic distribution by the uplink allocated bandwidth

10.3.5.3.7

Displaying Traffic Simulation Results Using Tooltips

You can display information by placing the pointer over a mobile generated during a simulation to read the information displayed in the tool tips. The information displayed is defined by the settings you made on the Display tab. For information on defining the tool tips, see "Defining the Object Type Tip Text" on page 36. To display simulation results in the form of tool tips: In the map window, place the pointer over the user that you want more information on. After a brief pause, the tooltip appears with the information defined in the Display tab of the WiMAX Simulations folder properties (see Figure 10.561).

Figure 10.561: Displaying the traffic simulation results using tool tips

10.3.5.4

Displaying the Results of a Single Simulation

After you have created a simulation, as explained in "Creating Simulations" on page 1056, you can display the results. To access the results of a single simulation: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( you want to access. ) to expand the WiMAX Simulations folder. ) to expand the folder of the simulation group containing the simulation whose results

4. Right-click the simulation. The context menu appears. 5. Select Properties from the context menu. The simulation properties dialogue appears. One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain simulation results as identified by the tab title. The Statistics tab: The Statistics tab contains the following sections: Request: Under Request, is 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; radio resource allocation has not yet finished. The result depends on the traffic description and traffic input.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1061

Atoll User Manual 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 number of iterations that were run in order to converge. 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. These data are also given per service.

Results: Under Results, is data on the connection results: -

The Sites tab: The Sites tab contains the following 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. 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. 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." Connected: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both. Connected DL+UL: The number of users connected to any cell of the site in downlink and uplink both. Connected DL: The number of users connected to any cell of the site in downlink. Connected UL: The number of users connected to any cell of the site in uplink. 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. 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: 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. Segmentation Usage (DL) (%): (WiMAX 802.16e) The percentage of the downlink traffic load that corresponds to the first downlink PUSC zone, if it is segmented. 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. AAS Simulation Results: 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. MU-MIMO Capacity Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.

1062

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 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. 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. 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." Connected: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Connected DL+UL: The number of users connected to the cell in downlink and uplink both. Connected DL: The number of users connected to the cell in downlink. Connected UL: The number of users connected to the cell in uplink. Connection Success Rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. 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. 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 DL, UL, or DL+UL. 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. 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. Indoor: This field indicates whether indoor losses have been added or not. Serving Base Station: The serving transmitter of the subscriber. Reference Cell: The reference cell of the serving transmitter of the subscriber. Path Loss (dB): The path loss 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. 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 serving base station. 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 serving base station.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1063

Atoll User Manual Preamble Total Noise (I+N) (DL) (dBm): The sum of the preamble interference and noise experienced 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 Total Noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced 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. Bearer (DL): The highest WiMAX bearer available for the traffic C/(I+N) level at the user location in the downlink. Permutation Zone (DL) (WiMAX 802.16e): The downlink permutation zone allocated to the user. BLER (DL): The Block Error Rate read from the user terminals WiMAX 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. Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter of the user in the uplink. C/(I+N) (UL) (dB): The C/(I+N) 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) (WiMAX 802.16e): The uplink permutation zone allocated to the user. BLER (UL): The Block Error Rate read from the reference cells WiMAX 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. 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 (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput scaling factor of the service and the throughput offset.

1064

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Notes: In Atoll, channel throughputs are peak MAC, effective MAC, or application throughputs achieved at a given location using the highest WiMAX bearer with the entire channel resources. If a user is rejected, his user throughput is zero.

The Initial Conditions tab: The Initial Conditions tab contains the following information: The global transmitter parameters: The frame duration The cyclic prefix ratio The UL and DL fixed overheads The UL and DL variable overheads The TDD-specific parameters: DL:UL ratio, TTG, and RTG The UL power control margin For WiMAX 802.16d documents: the number of subchannels per channel, and the numbers of total, used, and data subcarriers. The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink traffic load convergence thresholds The uplink noise rise convergence threshold The names of the traffic maps and subscriber lists used.

The input parameters specified when creating the simulation: -

The parameters related to the clutter classes, including the default values.

10.3.5.5

Displaying the Average Results of a Group of Simulations

After you have created a group of simulations, as explained in "Creating Simulations" on page 1056, you can display the average results of the group. If you wish to display the results of a single simulation in a group, see "Displaying the Results of a Single Simulation" on page 1061. To display the averaged results of a group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the WiMAX Parameters folder.

3. Right-click the group of simulations whose results you want to display. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain the averaged results for all simulations of the group. The Statistics tab: The Statistics tab contains the following sections: Request: Under Request is 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; 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 number of iterations that were run in order to converge. 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. These data are also given per service.

Results: Under Results is data on the connection results: -

The Sites (Average) tab: The Sites (Average) tab contains the following 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1065

Atoll User Manual 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. 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. 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." Connected: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Connected DL+UL: The number of users connected to the cell in downlink and uplink both. Connected DL: The number of users connected to the cell in downlink. Connected UL: The number of users connected to the cell in uplink. Connection Success Rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. 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 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. Segmentation Usage (DL) (%): (WiMAX 802.16e) The percentage of the downlink traffic load that corresponds to the first downlink PUSC zone, if it is segmented. 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. AAS Simulation Results: 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. 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. 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. No Service: The number of users unable to connect to the cell for which the rejection cause was "No Service."

1066

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 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." Connected: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Connected DL+UL: The number of users connected to the cell in downlink and uplink both. Connected DL: The number of users connected to the cell in downlink. Connected UL: The number of users connected to the cell in uplink. Connection Success Rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. 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: The global transmitter parameters: The frame duration The cyclic prefix ratio The UL and DL fixed overheads The UL and DL variable overheads The TDD-specific parameters: DL:UL ratio, TTG, and RTG The UL power control margin For WiMAX 802.16d documents: the number of subchannels per channel and the number of total, used, and data subcarriers. The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink traffic load convergence thresholds The uplink noise rise convergence threshold The names of the traffic maps and subscriber lists used.

The input parameters specified when creating the group of simulations: -

The parameters related to the clutter classes, including the default values.

10.3.5.6

Updating Cell Load Values With Simulation Results

After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 1056, you can update cell load values for each cell with the results calculated during the simulation. To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the WiMAX Simulations folder.

c. Right-click the group of simulations whose results you want to access. d. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain average simulation results for all simulations. To display the results for a single simulation: a. Click the Data tab in the Explorer window. b. Click the Expand button ( c. Click the Expand button ( sults you want to access. ) to expand the WiMAX Simulations folder. ) to expand the folder of the simulation group containing the simulation whose re-

d. Right-click the simulation whose results you want to access. e. Select Properties from the context menu. The simulation properties dialogue appears. 2. Click the Cells tab. 3. On the Cells tab, click Commit Results. The following values are updated for each cell: Forsk 2010 Traffic Load (DL) Traffic Load (UL) UL Noise Rise Segmentation Usage (DL) (WiMAX 802.16e) AAS Simulation Results Unauthorized reproduction or distribution of this document is prohibited

1067

Atoll User Manual AAS Usage (DL) MU-MIMO Capacity Gain (UL)

10.3.5.7

Estimating a Traffic Increase

When you create simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increase of traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations as described in "Creating Simulations" on page 1056. 2. Click the Source Traffic tab of the properties dialogue. 3. Enter a Global Scaling Factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).

10.3.6

Making Coverage Predictions Using Simulation Results

In Atoll, you can can analyse simulation results by making coverage predictions using simulation results. In a coverage prediction each pixel is considered as a non-interfering probe user with a defined terminal, mobility, and service. The analyses can be based on a single simulation or on an averaged group of simulations. When no simulations are available, Atoll uses the downlink traffic load, uplink noise rise, and any AAS simulation results stored for each cell to make coverage predictions. For information on cell properties, see "Cell Description" on page 972; for information on modifying cell properties, see "Creating or Modifying a Cell" on page 976. Once you have made simulations, Atoll can use the information from the simulations instead of the defined parameters in the cell properties to make coverage predictions. For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, which uses the average of all simulations in the group. The coverage predictions that can use simulation results are: Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see "Making a Coverage Prediction by C/(I+N) Level" on page 1012. Coverage by Best Bearer: For information on making a downlink or uplink coverage by best bearer, see "Making a Coverage by Best Bearer" on page 1014. Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making a Coverage by Throughput" on page 1016. Coverage by Quality Indicator: For information on making a downlink or uplink coverage by quality indicator, see "Making a Coverage by Quality Indicator" on page 1019.

When no simulations are available, you select "(Cells Table)" from the Load Conditions list, on the Condition 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 Condition tab. 2. From the Load Conditions list, select the simulation or group of simulations on which you want to base the coverage prediction.

10.4

Optimising Network Parameters Using the ACP

Atoll Automatic Cell Planning (ACP) enables radio engineers designing WiMAX networks to automatically calculate the optimal network settings in terms of network coverage and capacity. Atoll ACP can also be used in co-planning projects where WiMAX networks must both be taken into consideration when calculating the optimal network settings. Coverage maps are used for the optimisation process, however, traffic maps can be used for weighting network load distribution. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and cell pilot power. ACP can also be used during the initial planning stage of a WiMAX network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP also enables you to select to select which sites can be added or removed to improve existing or new networks.

10.4.1

The ACP Module and Atoll

Atoll ACP can be used either with existing networks or with networks in the initial planning phases. With existing networks, it is most efficient to focus on tuning the parameters that can be easily changed remotely, for example: Antenna electrical tilt: ACP adjusts the electrical tilt by selecting the best antenna from the antenna group assigned to this transmitter. Preamble power for each cell: The preamble power is set within a defined minimum and maximum value for each cell.

1068

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks When optimising a network that is still in the planning phase, Atoll ACP can calculate how the network can be improved by: Selecting the antenna type for each transmitter: ACP selects the best antenna from the antenna group assigned to this transmitter. Changing the antenna azimuth: ACP sets the antenna azimuth using a defined range on either side of the currently defined azimuth. Changing the mechanical tilt of the antenna: ACP sets the mechanical tilt using a defined range on either side of the currently defined mechanical tilt. Changing the height of the antenna: ACP sets the optimal antenna height using a defined range on either side of the currently defined antenna height. Selecting sites: ACP adds or removes sites that you have indicated as candidates for addition or removal in order to improve existing or new networks.

In this section, the following are explained: "Using Zones with ACP" on page 1069 "Using Traffic Maps with ACP" on page 1069 "Shadowing Margin and Indoor Coverage" on page 1070 "ACP and Antenna Masking" on page 1070.

10.4.1.1

Using Zones with ACP

ACP uses different zones during the optimisation process for different purposes. ACP uses the computation zone to define the area of the network to be optimised. ACP always takes the entire computation zone into consideration, even if the zone selected for optimisation is the focus zone; the sites and transmitters included in the computation zone and not in the focus zone are still taken into consideration when calculating signal, interference, and best server status. ACP enables you to define different targets and different weights for each zone: for the computation zone, for the focus zone, for the hot spot zones, and for each clutter classes. In this section, the following are explained: "Using the Computation Zone and the Focus Zone" on page 1069 "Using Hot Spots" on page 1069 "Using the Filtering Zone" on page 1069.

10.4.1.1.1

Using the Computation Zone and the Focus Zone

Atoll ACP optimises the settings for the sites in either the computation zone or the focus zone. If you have both a computation zone and a focus zone defined, you can select which zone will be used for the optimisation process. If there is no focus or computation zone, the ACP optimises the settings for the cells in a rectangle including all cells in the network. Atoll ACP allows you to define different targets for the computation zone and the focus zone, as well as for the hot spot zones. You can also define different weights for each zone. Note: It is recommended to define a computation zone. ACP uses the computation zone as the area in which the quality figures are calculated and improved during optimisation. Additionally, the zone defined by ACP might take into account areas outside of actual traffic boundaries.

10.4.1.1.2

Using Hot Spots

Atoll ACP also allows you to use hot spot zones, enabling you to specify different quality targets for each hot spot zone and display final results per zone. You can also define different weights for each zone. You can use the hot spot zones defined in the Atoll document, import ArcView SHP files to create hot spot zones, or you can create hot spot zones based on clutter classes.

10.4.1.1.3

Using the Filtering Zone

If there is a filtering zone defined, Atoll ACP will optimise all currently defined and active cells selected by the filtering zone.

Note:

ACP automatically considers all the cells that have an effect on the computation or focus zone, and ignores the rest (for example, cells that are too far away to have an impact on the selected cells). It is nonetheless recommended to use a filtering zone to speed up initial data extraction from the Atoll document.

10.4.1.2

Using Traffic Maps with ACP

Atoll ACP can use traffic maps to determine the traffic density on each pixel. The traffic density is used to weight each of the quality figures according to traffic and to put more emphasis on high traffic areas. You can apply the imported traffic density files to either or both of the quality indicators.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1069

Atoll User Manual

Figure 10.562: ACP traffic parameters Note: For the moment, traffic profiles are only used to evaluate the traffic weighting to apply to each pixel (by adding the load-scaled traffic distribution on each traffic profile). This information will also be used in the future to better manage cell load.

10.4.1.3

Shadowing Margin and Indoor Coverage

Atoll ACP enables you to take indoor coverage and a shadowing margin into consideration. When indoor coverage is taken into consideration, all pixels marked as indoors have an additional indoor loss added to total losses. The indoor loss is defined per clutter class. By default, ACP considers all pixels to be indoors, but Atoll ACP allows you to specify which clutter class should be considered as indoors and which not. When the shadowing margin is taken into consideration, the defined shadowing margin is taken into consideration in the calculation of the received useful signal power and interfering signal power. For more information on how shadowing and macro-diversity gains are calculated, see the Technical Reference Guide. Note: You can set ACP to not take macro-diversity gains into consideration by setting the appropriate option in the acp.ini file. You will need to update the corresponding parameters in the atoll.ini file as well. For information on modifying the atoll.ini file, see the Administrator Guide.

10.4.1.4

ACP and Antenna Masking

When ACP performs any type of antenna reconfiguration, it must determine how attenuation to the path loss changes when the antenna is modified. ACP determines changes to path loss attenuation using antenna masking. Depending on the propagation model used to calculate the path loss matrices, ACP supports the following antenna masking methods: Natively supported propagation models: ACP calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. Because ACP is using the same propagation model as was used to calculate the original path loss matrices, the results are consistent and accurate. For this reason, using natively supported propagation models is the preferred method. For more information, see "Natively Supported Propagation Models" on page 1070. ACPs default propagation model: If the propagation model used to calculate the original path loss matrices is not supported by ACP, ACP can use its own default propagation model. Because the ACP default propagation model is not the same as the one used to calculate the original path loss matrices, accuracy cannot be guaranteed. ACPs default propagation model is similar to Atolls Standard Propagation Model and should deliver acceptable results for any macro-type propagation model. For more information, see "ACPs Default Propagation Model" on page 1071. Precalculated path loss matrices: ACP allows you to designate all propagation models in the project which are not supported by the native method. ACP will then prerecalculated path loss matrices for these propagation models. For more information, see "Precalculated Path Loss Matrices" on page 1071. Note: Preamble power optimisation and site selection (without reconfiguration) are made independently of the method used to determine changes to path loss attenuation.

10.4.1.4.1

Natively Supported Propagation Models

During antenna optimisation, ACP must calculate how the attenuation to the path loss changes when the antenna is modified, i.e., when the antenna type, tile, or azimuth is modified. When ACP uses natively supported propagation models, it calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. The unmasking and remasking operations are strongly dependent on the propagation model that was used to calculate the path losses, especially to: Find the horizontal and vertical emission angles between a transmitter and the receiving pixel. The angles depend strongly on the radial method used to account for the height profile between the transmitter and receiver. Find the correct antenna gain for a given set of horizontal and vertical emission angles. The gain is usually based on a 3-D interpolation of the 2-D patterns and can be model-dependent.

How ACP calculates attenuation depends on the propagation model used by Atoll to generate the path loss. The propagation model parameters which affect processing are automatically extracted by ACP. ACP supports the propagation models commonly used in Atoll. For other propagation models, ACP uses a default model similar to Cost-Hata, however,

1070

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks you can always set ACP to use another propagation model, the SPM for example, if you feel it would give more accurate results. The raster data needed by ACP depends on the propagation model that Atoll used to generate the path loss.

Propagation Model
All Atoll Hata-based propagation models (Cost-Hata, Okumura-Hata, ITU, etc.)

Raster Data Required

DEM file DEM file Clutter Height file (optional) Clutter file (optional) DEM file

Atoll Standard Propagation Model

All other models.

Because the path loss information is not stored in the ACP optimisation setup but in the Atoll document where it is accessed by ACP, changes in the Atoll document can cause inconsistency between the optimisation results and the actual state of the network, for example, when transmitters are modified in the document. ACP deals with this situation by locking optimisation results. An optimisation can not be rerun on locked results if the path loss data are not consistent with the internal state of the optimisation. The results are automatically unlocked if the state of the Atoll document again becomes consistent with the ACP optimisation. The same mechanism applies when settings produced by an optimisation run are committed to the Atoll network. The results are locked after being committed and will be unlocked if the network is rolled back to the state on which the optimisation was based.

10.4.1.4.2

ACPs Default Propagation Model

ACP has an internal default propagation model that can be used if the propagation model used to calculate the original path loss matrices is not supported by ACP. Because the ACP default propagation model is not the same as the one used to calculate the original path loss matrices, accuracy can not be guaranteed, although it should deliver acceptable results for any macro-type propagation model. ACP offers a few parameters that enable you to improve the accuracy of the default propagation model: Use Clutter Height: By selecting Use Clutter Height, ACP will take into consideration clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on Top of Clutter: If the receiver is on top of the clutter, for example, if receivers are located on top of buildings, you can select Receiver on Top of Clutter. The receiver height will then be sum of the clutter height and the receiver height. Use Radial Method: You can select the Use Radial Method check box if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

These parameters can be set individually for each propagation model for which ACP will use the default propagation method. These parameters belong to the advanced parameters; to modify them, you must first make the advanced parameters visible. For information on making the advanced parameters visible, "Configuring the Default Settings" on page 1072.

10.4.1.4.3

Precalculated Path Loss Matrices

After the ACP setup has been created, ACP calculates the path loss matrices necessary (i.e., for sites that are being optimised and do not use natively supported propagation models or the ACP's internal model) while the optimisation is loading. ACP does not calculate all path loss matrices for all possible combinations, for example, five possible changes in electrical tilt and five possible changes in azimuth, i.e., 25 path loss matrices to be calculated. ACP only calculates the path loss matrices for the most common optmisation changes, for example, changes to the electrical tilt. By pre-calculating only the most common changes, ACP reduces the number of path loss changes to be calculated and reduces the calculation time. While the optimisation is running, ACP uses the pre-calculated path loss matrices. If a change is made to a transmitter that was not taken into the consideration when the path loss matrices were calculated, ACP recalculates the path loss matrix for that change only. The end result are considerable savings in both time and computer resources. For information on natively supported propagation models, see "Natively Supported Propagation Models" on page 1070. 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, it is often similar enough to a supported propagation model so that ACP can still use it. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1071

Atoll User Manual

Notes:

Precalculated path loss matrices can only be used when optimising the antenna type and azimuth. Optimising the mechanical tilt is not currently supported.

10.4.2

Configuring the ACP Module

You can change the default settings of the Atoll ACP module so that selected options are the default settings each time you run ACP. Additionally, you can base the default ACP settings on some or all of the settings of a given Atoll optimisation. In this section, the following are explained: "Configuring the Default Settings" on page 1072 "Defining the Antenna Masking Method" on page 1073 "Saving Settings to a User Configuration File" on page 1074.

10.4.2.1

Configuring the Default Settings

To configure the default settings of the ACP module: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Default Settings tab. On the Default Settings tab, you can define the configuration files that contain the default settings. These settings are applied every time you run an optimisation project. Under Loading Default Settings: Global Configuration: The Global Configuration is the configuration file set up by the administrator. This configuration provides the same default settings to everyone on the network. For information on the ACP global configuration file, see the Administrator Manual. User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings you want to be the default settings for the ACP module.

5. Click the User Preferences tab. On the User Preferences tab (see Figure 10.563), you can define settings that are saved to the acp.ini configuration file found in the ACP installation folder. These settings will be applied every time you run a new configuration.

Figure 10.563: Setting ACP user preferences Under Setup Preferences: You can define the following settings: Enable automatic setting from custom table field (antennas, sites): Select the Enable automatic setting from custom table field (antennas, sites) check box if you want ACP to use the custom columns in the SITES and ANTENNAS tables. If you want ACP to use the custom columns, you must set the appropriate options in the acp.ini file. For more information on the acp.ini file, see the Administrator Manual. Show advanced optimisation settings: Select the Show advanced optimisation settings check box if you want the ACP to display the Advanced tab when you define an optimisation setup. When the Advanced tab is available, you can set a few additional options related to services, terminals, clutter, and propagation models. Calculation setting: Adjust the slider to define whether you want ACP to provide its results more quickly, at the expense of precision, or whether you want ACP to provide more accurate results, at the expense of speed. By selecting a higher speed, you will cause ACP to reduce the number of cells monitored for each pixel, some of which might only create a bit of interference at first, but which could possibly create significantly more interference after antenna parameters are changed during the optimisation process. Selecting a higher precision avoids this problem at the expense of more time and computer resources.

1072

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Under Result Preferences: You can define the following setting for report maps: Default map transparency: Define the default map transparency with the slider.

6. Click the Private Directory tab. On the Private Directory tab (see Figure 10.564), you can define the directory to be used by the ACP to store precalculated path loss matrices as well as the path loss matrices for antenna height optimisation.

Figure 10.564: Defining the directory for path loss matrices 7. Enter the name of the directory or click the the Browse button ( 8. Click OK to save your changes. When the propagation model used is not one natively supported by ACP, for example, complex ray-tracing propagation models, ACP can use precalculated path loss matrices to calculate attenuation. For more information, see "Defining the Antenna Masking Method" on page 1073. ) to navigate to the directory.

10.4.2.2

Defining the Antenna Masking Method

You can define how Atoll ACP calculates path loss matrices, using either Atolls propagation models, ACPs internal propagation model, or precalculated path loss matrices. These parameters will be applied to all new and duplicated setups. To define how ACP calculates path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Antenna Masking Model tab (see Figure 10.565).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1073

Atoll User Manual

Figure 10.565: The Antenna Masking Model tab 5. If you are using a propagation model that ACP does not natively support, select the Enable precalculated path loss matrices check box. You will then be able to select the propagation model for which ACP will pre-calculate path attentuation. 6. Under Propagation Models, select the check boxes in each column to define how ACP will interact with that propagation model. Not all parameters are available for all propagation models:

Tip:

By default, all available propagation models are displayed. By selecting the Show only used propagation models check box, ACP will only display the propagation models that are actually used.

Antenna masking method: The Antenna masking method indicates whether ACP can use this propagation model natively, or whether ACP uses its own default method. The information in this column can not be edited. Use precalculated path loss: Select the check box in the Use precalculated path loss column corresponding to every propagation model that is not supported natively by ACP or that can not be replaced using ACPs internal default method. Use clutter height: Select the check box in the Use clutter height column if you want ACP to take clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on top of clutter: Select the check box in the Receiver on top of clutter column if you want the receiver height to be sum of the clutter height and the receiver height. This option can be used, for example, to model receivers on top of buildings. Use radial method: Select the check box in the Use radial method column if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

7. Click OK.

10.4.2.3

Saving Settings to a User Configuration File

To save the settings to a user configuration file: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Default Settings tab. On the Default Settings tab, you can define the configuration files that contain the default settings. These settings are applied every time you run an optimisation project. Under Loading Default Settings: Global Configuration: The Global Configuration indicates the configuration file set up by the administrator. This configuration provides the same default settings to everyone on the network. For information on the ACP global configuration file, see the Administrator Manual. User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings you want to be the default settings for the ACP module.

1074

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 5. Click the Save Configuration File button under Saving Default Settings to save settings to a user configuration file. Note: The settings you save to a user configuration file are from an ACP optimisation from the current Atoll document. If you have not yet used ACP for an optimisation in the current document, the Save Configuration File button is not available.

When you click the Save Configuration File button, the Save Configuration File dialogue opens (see Figure 10.566).

Figure 10.566: The Save Configuration File dialogue 6. From the Save setting based on setup list, select the ACP setup on whose parameters you want to base the user configuration file. 7. Click the Browse button ( file. ) next to To configuration file to select where you will save the user configuration

8. Under Sections to save, select the check boxes of the types of parameters whose settings you want to save to the user configuration file. 9. Click Save.

10.4.3

Optimising Cell Planning with the ACP

Optimising cell planning with the Atoll ACP consists of defining the parameters that will be used during the optimisation process and then running the process. Each optimisation, with its parameters and results, is stored in a Setup folder in the ACP - Automatic Cell Planning folder on the Data tab of the Explorer window. In this section, the following are explained: "Creating an Optimisation Setup" on page 1075 "Defining Optimisation Parameters" on page 1076.

10.4.3.1

Creating an Optimisation Setup

In ACP, you can create an optimisation setup either by creating and running a new one, or by duplicating or opening an existing optimisation, editing the parameters, and then running it. In this section, the following are explained: "Creating a New Optimisation Setup" on page 1075 "Running an Existing Optimisation Setup" on page 1076 "Duplicating an Existing Optimisation Setup" on page 1076.

Creating a New Optimisation Setup

To create a new optimisation setup: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 1076. 4. After defining the optimisation setup:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1075

Atoll User Manual Click the Run button to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 1100. Click the Create Setup button to save the defined optimisation. For information on running the optimisation, see "Running an Existing Optimisation Setup" on page 1076.

Running an Existing Optimisation Setup

To run an existing optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

3. Right-click the optimisation you want to run. The context menu appears. Select Run from the context menu to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 1100. Select Properties from the context menu to view or modify the parameters of the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 1076.

Duplicating an Existing Optimisation Setup

To duplicate an existing optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

3. Right-click the setup you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The ACP Duplicate Options dialogue appears. 5. Under Data Synchronisation Option, select one of the following: Minimal: The duplicated ACP setup will have only the data that was changed by the ACP during optimisation. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid. Complete: The duplicated ACP setup will have have all the data from the ACP optimisation.

6. Run the existing optimisation setup as described in "Running an Existing Optimisation Setup" on page 1076.

10.4.3.2

Defining Optimisation Parameters

In Atoll ACP, when you create a new optimisation setup, you must first define all the parameters. You can also modify the parameters of an existing optimisation setup before running it. Creating a new optimisation setup is explained in "Creating a New Optimisation Setup" on page 1075. Running an existing optimisation is explained in "Running an Existing Optimisation Setup" on page 1076. The optimisation parameters are grouped onto specific tabs of the dialogue. The parameters are the same whether you create a new optimisation setup or whether you modify the parameters of an existing one. In this section, the following parameters are explained: "Setting Optimisation Parameters" on page 1076 "Setting Objective Parameters" on page 1079 "Setting Traffic Parameters for Non-uniform Traffic" on page 1082 "Setting Network Reconfiguration Parameters" on page 1083 "Defining Site Selection Parameters" on page 1089 "Defining Antenna Groups" on page 1093 "Adding Comments to the Optimisation Setup" on page 1097 "Setting Advanced Parameters" on page 1097.

10.4.3.2.1

Setting Optimisation Parameters

The Optimisation tab allows you to define the various parameters related to the optimisation algorithm. To set the optimisation parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Optimisation tab (see Figure 10.567).

1076

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.567: The Optimisation tab 3. Define the following: Number of Iterations: Set the number of iterations for the optimisation algorithm. ACP calculates a suggested number of iterations by multiplying the total number of parameters to optimise (i.e., cell pilot power, antennas, azimuth, mechanical tilt, sites subject to selection) by two. You can accept the number of iterations, or set your own value. Often one-half or one-quarter of the suggested number is sufficient for ACP to find the optimal configuration. Resolution (m): Specify the resolution for the optimisation. Each criterion will be evaluated on each of these pixels. The total number of pixels and the average number per site is indicated. This parameter has a large influence on the accuracy and speed of the optimisation process. You should either set a resolution that is consistent with the path loss and raster data in the Atoll document, or you should set a resolution that will result in between 300 and 3000 positions per site.

4. Under Setup, you can set the following optimisation-related objectives and parameters: a. In the pane on the left-hand side, click Layers. Under Layers (see Figure 10.567 on page 1077), you can define the following for each layer to be optimised: Use: You can select which layers are to be considered in the optimisation process by selecting their check box in the Use column. The signals and interference of the transmitters and sites in the selected layers will be taken into consideration during the optimisation process. If the transmitters and sites in the selected layers are within the area to be optimised (the computation zone or the focus zone, as selected under Zones on the Optimisation tab), these transmitters and cells will be optimised. Selecting layers to be taken into consideration is most useful when you want to take the signal and interference of several layers into consideration, but only want to optimise one of the layers. Selecting the layers here ensures that ACP will take them into consideration. Transmitters and sites in layers which are not selected are treated by 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. Note: If a transmitter on one selected layer that is optimised is linked with a transmitter on another selected layer that is not optimised, the second transmitter will still appear on the Reconfiguration tab and any changes to the first transmitter will be applied to the linked transmitter as well. Name: You can change the name of the layer by clicking it and entering a new name. Weight: You can change the weight assigned to the layer during optimisation by clicking it and entering a new weight. ACP will put more emphasis on increasing the quality of the layer with the greater weight. For example, if one layer has a weight of "2" and another layer has a weight of "1," ACP will consider increasing the quality of the first layer by 1% as equivalent to increasing the quality of the second layer by 2%. Reconfiguration: If you want the layer to be taken into consideration for reconfiguration, you can select the check box in the Reconfiguration column. Site Selection: If you want the layer to be taken into consideration for site selection, you can select the check box in the Site Selection column.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1077

Atoll User Manual The following columns give information about the layer; they can not be edited: Technology: The technology (WiMAX in this case) used by the layer. Freq. Band/Carrier: The frequency band and carrier (if applicable) used by the layer. Nb Tx/Cell: The number of transmitters in the layer.

You can merge layers if you want to define identical objectives for both layers (for more information on objectives, see "Setting Objective Parameters" on page 1079). To merge layers: i. Hold CTRL and click the layers you want to merge.

ii. Click the Merge button. b. In the pane on the left-hand side, click Zones. Under Zones (see Figure 10.569), you can define how the zones will be used during optimisation. The zones are used to define geographical objectives and weighting. The zones are taken into consideration in the following order: the hot spot zones in their defined order, the focus zone, and finally the computation zone. Filtering Zones: Select the Computation Zone check box to lock sectors outside the computation zone and the Focus Zone check box to lock sectors outside the focus zone. If there is no focus zone in the project to be optimised, the computation zone is automatically selected. Hot Spots: For each new hot spot, enter a Name in the row marked with the New Row icon ( click the Browse button ( ) and ) to open the Zone Definition dialogue. You can import an ArcView SHP file

by selecting From file and clicking the the Browse button ( ). Or, you can use an existing hot spot zone in the Atoll document by selecting From hot spot and selecting the hot spot zone from the list. Or, you can create a hot spot zone composed of all areas in the reconfiguration zones that are included in one or more clutter class by selecing From clutter classes and selecting the check box corresponding to the clutter class or classes you want to study.

Figure 10.568: The Zone Definition dialogue You can change the order in which the hot spots will be taken into consideration, by clicking the layers number in the Order column and then clicking the Up button ( ) or the Down button ( ).

Figure 10.569: Configuring zones on the Optimisation tab c. In the pane on the left-hand side, click Cost Control. Under Cost Control (see Figure 10.570), you can define how the costs will be calculated for each optimisation option. ACP will use the defined costs to calculate the optimisations that are the most cost-effective. You can select three types of cost control:

1078

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks No cost control: If you select No cost control, ACP will not take cost into consideration when optimising the network. Maximum cost: If you select Maximum cost, you can enter a maximum cost not to be exceeded and define the costs under Cost Setting. Quality/Cost trade-off: If you select Quality/Cost trade-off, ACP will find a compromise between cost and quality. You can use the slider to define whether ACP should put more emphasis on quality (Low) or cost (High).

Figure 10.570: Configuring costs on the Optimisation tab In the Reconfiguration Cost section, under Cost Setting, define the individual costs for each reconfiguration option. If reconfiguring an option can only be done at the physical location of the transmitter, select the check box in the Site Visit column. The cost will be increased by the defined Site Visit value. The site visit cost is incurred only once per site, independently of the number of reconfigurations that might be made to the same site, including sites supporting more than one technology. In the Site Selection Cost section, under Cost Setting, define the individual costs for each site selection option.

10.4.3.2.2

Setting Objective Parameters

The Objectives tab allows you to define the various parameters related to the objectives of the optimisation. ACP allows you to set different objectives for each layer selected in the Use column under Layers on the Optimisation tab. The objectives vary according to the technology used by the network being optimised. The options are given here. To set the objective parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Objectives tab (see Figure 10.571).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1079

Atoll User Manual

Figure 10.571: The Optimisation tab 3. Under Criteria, you can set the following objective-related objectives and parameters. a. Under Objective, click Preamble Coverage to define the preamble coverage parameters. Computation zone: Select the check box in the Use column if you want to define a CN Minimum threshold (dBm) for CN coverage in computation zone. Under Area Coverage, you can define the percentage by which the current CN coverage should be improved (Improve current coverage (+-)) or a target CN coverage (Target coverage (%)). Focus zone: Select the check box in the Use column if you want to define a CN Minimum threshold (dBm) for CN coverage in focus zone. Hot Spot zone: Each hot spot zone defined under Zones on the Optimisation tab will appear under Name. For each hot spot zone, select the check box in the Use column if you want to define a CN Minimum threshold (dBm) for CN coverage in the hot spot zone.

b. Under Objective, click Parameters under Preamble Coverage to define how ACP will calculate the preamble CN coverage. From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate preamble CN coverage, or you can select Manual Configuration and define the settings yourself. Important: If you want to use a coverage prediction, the coverage prediction must have already been calculated. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own maps. However, if you have saved the display options of an ACP map as default, or if you are using a configuration file for ACP, these defined ranges and colours will be used as the default, overriding the settings in the selected coverage prediction. For information on setting ACP map display options as the default, see "Changing the Display Properties of ACP Maps" on page 1112. For information on saving a configuration file, see "Configuring the Default Settings" on page 1072. If you selected Manual Configuration from the Base prediction settings on list, define the following options: Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell edge coverage probability. When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied. You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced Parameters" on page 1097.

c. Under Objective, click Preamble CINR to define the radio conditions parameters. d. Under Calculation Method, define how the preamble CINR will be calculated:

1080

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Select Using frequency plan if you want the frequency plan to be taken into consideration when calculating the preamble CINR. Select the Apply segmentation check box if you want segmentation (fractional frequency reuse) to be taken into consideration as well when calculating the preamble CINR. Segmentation or fractional frequency reuse is only supported in WiMAX 802.16e/ Select Ignoring frequency plan & segmentation if you want the preamble CINR to be calculated without taking the frequency plan and segmentation into consideration.

Note: -

e. Under Objective, define the Preamble CINR coverage parameters. Computation zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for preamble CINR coverage in the computation zone. Under Area Coverage, you can define the percentage by which the current preamble CINR coverage should be improved (Improve current coverage (+-)) or a target preamble CINR coverage (Target coverage (%)). Focus zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for preamble CINR coverage in the focus zone. Hot Spot zone: Every hot spot zone defined under Zones on the Optimisation tab will appear under Preamble CINR. For each hot spot zone, select the check box in the Use column if you want to define a Minimum threshold (dBm) for preamble CINR in the hot spot zone.

f.

Under Objective, click Parameters under Preamble CINR to define how ACP will calculate preamble CINR coverage. From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate preamble CINR coverage, or you can select Manual Configuration and define the settings yourself.

Important: If you want to use a coverage prediction, the coverage prediction must have already been calculated. If you selected Manual Configuration from the Base prediction settings on list, define the following options: Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell edge coverage probability. When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Macro diversity is also taken into account during the calculation of preamble CINR. Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied. You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced Parameters" on page 1097. Select a Service and a Terminal. The service and terminal specified are 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 terminal noise factor).

g. Under Criteria, click Weighting to set the importance of the objectives (see Figure 10.572).

Figure 10.572: Setting weighting options for WiMAX

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1081

Atoll User Manual i. Under Objective Weighting, move the slider to set the relative importance of signal coverage and preamble CINR coverage. You can set meeting one objective as more important than meeting the other, or you can set meeting only the signal coverage or preamble CINR coverage.

ii. Under Zone weighting, define the weight given to the computation zone, the focus zone, and any hot spot zone. With zone weighting, ACP adds an extra weight to all the pixels of a zone. Because one pixel can belong to several zones (for example, a pixel can be inside both the focus zone and the computation zone and in a hot spot zone, if there is one), the weight applied to that pixel is the weight of the zone with the highest priority: the hot spot zone, if it exists, then the focus zone, finally the computation zone. Important: It is important to remember that, if every zone is assigned the same weight, the optimisation is made as if no weight is assigned to any zone. Defining a weight of "0" for a zone means that that zone will not be taken into consideration when trying to reach the set objectives. Zone weighting is used to focus optimisation on the appropriate areas. The assigned weights are used to weight the traffic parameters selected on the Traffic tab, unless the optimisation is based on uniform traffic. For information on the selected traffic parameters, see "Setting Traffic Parameters for Non-uniform Traffic" on page 1082. However, if no traffic maps are available or if the optimisation is based on uniform traffic, zone weighting can be used to ensure that ACP prioritises the optimisation of areas of high traffic. With multiple layers, you might have a layer that is restricted geographically (for example, the WiMAX 2.5 GHz layer might only be available in rural areas). Because ACP always measures the quality target over the entire computation zone, such a situation would lead to a measurement of poor quality in the urban areas, where there are no WiMAX 2.5 GHz sectors. By defining a weight of "0" outside of the rural area for this layer, you can restrict the measurement of coverage only to the part of the layer with WiMAX 2.5 GHz sectors. This way, the global target (90% of coverage for instance) is measured in a meaningful way. iii. Under Objective, click Miscellaneous to define the overlap threshold margin. Enter an Overlap threshold margin. It will be used for traffic maps.

10.4.3.2.3

Setting Traffic Parameters for Non-uniform Traffic

By default, the traffic is assumed to be uniform within the computation zone. The Traffic tab enables you to select traffic maps in the Atoll document to define non-uniform traffic. The traffic maps describe the distribution of users in the network, along with their characteristics (i.e., services, terminals, and mobility types). Traffic maps can used to weight the quality figures measured on each pixel by using the traffic density on that pixel. You can use traffic maps to weight quality figures. For example, you can optimise CINR coverage based only on area (defined on the Optimisation tab as explained in "Setting Optimisation Parameters" on page 1076) while optimising signal coverage using traffic distribution. When using traffic maps, network quality is always optimised using traffic weighting. ACP supports all traffic maps used by Atoll. To set the traffic parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Traffic tab (see Figure 10.573).

1082

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.573: Defining non-uniform traffic using the Traffic tab 3. Under Traffic Generated From, select one of the following methods for defining non-uniform traffic: Maps based on traffic densities: If you select Maps based on traffic densities, you can define the traffic weighting and traffic profiles. Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of CINR or Coverage or both. The weighting applied is the weighting defined on the Objectives tab. Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Service, Terminal, select a Traffic Density File by clicking the Browse button ( ), and assign a Weight.

When optimising LTE networks, you can use traffic maps as a traffic density file by first exporting traffic maps as traffic density maps. For information on exporting traffic maps, see "Exporting a Traffic Map" on page 1050. Following traffic maps: If you select Following traffic maps, you can select the maps that will be used to generate traffic and define the resolution of the extracted traffic and the traffic weighting. Under Following traffic maps, select the maps that will be used to generate traffic. Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of CINR or Coverage or both. Under Traffic Profiles, the traffic profiles will be displayed after ACP has extracted them from the selected traffic maps.

4. If you want to view the traffic profiles without running the optimisation setup, click Create Setup. ACP will then create the traffic profiles based on the traffic maps selected and the traffic parameters defined.

10.4.3.2.4

Setting Network Reconfiguration Parameters

The Reconfiguration tab allows you to select the WiMAX cells for which the preamble power will be reconfigured and the transmitters for which the antenna, azimuth, height, or tilt will be reconfigured. The Reconfiguration tab also allows you to select which sites or sectors can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly select sites for reconfiguration. For information on site selection, see "Defining Site Selection Parameters" on page 1089. Atoll allows you to export the reconfiguration parameters, modify them in an external application and then reimport them into the Reconfiguration tab. In this section, the following are explained: "Setting WiMAX Cell Reconfiguration Parameters" on page 1084 "Setting Transmitter Reconfiguration Parameters" on page 1085 "Linking Transmitters in Multi-layer Networks" on page 1086 "Using Precalculated Path Loss Matrices to Calculate Path Loss Attenuation" on page 1087 "Importing Network Reconfiguration Parameters" on page 1088.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1083

Atoll User Manual

Setting WiMAX Cell Reconfiguration Parameters

To set the WiMAX cell reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the WiMAX Cells tab (see Figure 10.575).

Figure 10.574: WiMAX cell reconfiguration options 3. Select the Preamble power check box for the preamble power of each selected cell 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 preamble power as offsets of the current power. 4. Select the Synchronise cell power on co-sector cells check box to ensure that all cells on the same sector are assigned the same cell power.

Important: 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. 5. Define the preamble power settings for each cell. Use: Select the Use 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 a minimum and maximum preamble power to be respected during the optimisation process. Note: If you selected the Power max/min as offset check box, you will set the Min. Offset and Max. Offset for each cell.

Step (dB): Set a Step in dB that ACP should use with attempting to find the optimal preamble power. Note: For preamble power optimisation, the preamble range is defined with minimum, maximum and step values. There is an absolute maximum possible preamble power which depends on the other powers used in the cell (for control, traffic, and max cell power).

You can make the same changes to several cells by making the change for one item, selecting the others starting from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 59. You can select the cells to which the reconfiguration options are going to be applied using the Advanced section of the Reconfiguration tab. For more information, see "Selecting Sites for Reconfiguration" on page 1092. You can sort the contents of any column by right-clicking the column and selecting Sort Ascending or Sort Descending from the context menu.

1084

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Caution: Cells that have been filtered out, either by zone or by clearing their check box in the table, will not be optimised but are still present in the network and, therefore, continue to generate interference.

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. For information on importing network reconfiguration options, see "Importing Network Reconfiguration Parameters" on page 1088.

Setting Transmitter Reconfiguration Parameters

To set the transmitter reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Reconfiguration tab (see Figure 10.575).

Figure 10.575: Transmitter reconfiguration options 3. Select the parameters that will be optimised: Antenna type: Select the Antenna type check box for ACP to adjust the antenna type by selecting the best antenna from the antenna group assigned to each selected transmitter. Electrical tilt: Select the Electrical tilt check box for ACP to select the best electrical tilt from the antenna group assigned to each selected transmitter within the defined range. Note: When ACP selects the best antenna type, it will also chose the best electrical tilt from the antenna group even if it is not optimising the electrical tilt. However, because no range is defined, ACP will select the best electrical tilt from all available.

Azimuth: Select the Azimuth check box for ACP to set the antenna azimuth using a defined range on either side of the currently defined azimuth. Note: By default, ACP optimises the antenna azimuth of each sector of a site individually. However, you might want to retain the same inter-sector angle separation. If this is the case, you can select the Azimuth check box corresponding to that site under Lock Site on the Sites tab of the Reconfiguration tab.

Mechanical tilt: Select the Mechanical tilt check box for ACP to set the mechanical tilt within the defined range and in the defined number of steps. Height: Select the Height check box for ACP to set the antenna height within the defined range and in the defined number of steps.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1085

Atoll User Manual

Note:

By default, ACP optimises the height of all antennas of a site identically. In other words, if ACP optimises the antenna of one sector by raising it 1 m., it will also raise the antennas of all other sectors by the same amount, in order to respect the distance between all antennas on the transmitter mast. However, in might not be necessary to maintain this distance, in which case you might want to optimise the height of each antenna of a site individually. f this is the case, you can clear the Height check box corresponding to that site under Lock Site on the Sites tab of the Reconfiguration tab.

The table displays, for each parameter selected, both the current settings for each cell in the selected zone and the currently defined optimisation parameters. Note: If you want ACP to display more information on each transmitter, you can select the Show Advanced Grid check box. ACP will then display, for each transmitter, the antenna masking method, the propagation model used, the transmitter height, and the name and status of the site the transmitter is located on. The propagation model displayed is extracted from the Atoll document but can be changed if the propagation model is not recognised by ACP (for more information, see "ACP and Antenna Masking" on page 1070).

4. Define the settings to be optimised for each cell. If are optimising the antenna azimuth, you can enter a single value in the Variation column, to define a range on either side of the current azimuth, or you can enter a minimum and maximum value separated by a semi-colon in the format "-min;max", (for example, "-20;40") in the Variation column for an asymmetric antenna. You can make the same changes to several cells by making the change for one item, selecting the others starting from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 59.

Linking Transmitters in Multi-layer Networks

When you are optimising transmitters in multi-layer environments, ACP automatically links transmitters in the same location but in different layers to ensure that it applies the same reconfiguration to them. ACP links them not only by location, but also by azimuth, mechanical tilt, and antenna height. If ACP does not automatically link two transmitters which should be linked, it is normally because there is too large a difference in one of the parameters of the two transmitters, for example, a few degrees in azimuth, one degree in mechanical tilt, or one meter difference in antenna height. If two transmitters should be linked but were not, you can manually link them. Note: If the site of one of the linked transmitters has either its antenna heights or azimuths locked, i.e., if changes made to one sector of the site are made to all sectors on that site, then corresponding changes will be made to the other linked transmitter. For more information on locking antenna heights or azimuths, see "Setting Transmitter Reconfiguration Parameters" on page 1085.

To link transmitters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the Transmitters tab. 3. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear. 4. Under Advanced, click the Multi-layer Management tab. On the Multi-layer Management tab, you can link transmitters (see Figure 10.576).

1086

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.576: Multi-layer management To link transmitters in the same location but on different layers: a. Hold CTRL and click the first transmitter in the table above and then the second transmitter. The Link button on the Multi-layer Management tab is now available. b. Click the Link button. The two transmitters are now linked and ACP will apply the same reconfiguration to them both. To unlink linked transmitters: a. Select the transmitters in the table The Unlink button on the Multi-layer Management tab is now available. b. Click the Unlink button. The transmitters are no longer linked. To unlink all linked transmitters: Click the Unlink All button. ACP resets all linked transmitters.

To automatically all transmitters in the same location but on different layers: Click the Auto Link button. ACP links all transmitters that have the same position, azimuth and mechanical tilt.

Using Precalculated Path Loss Matrices to Calculate Path Loss Attenuation

You can define how Atoll ACP calculates path loss matrices, using either Atolls propagation models, ACPs internal propagation model, or precalculated path loss matrices. These parameters will be applied to all new and duplicated setups. To define how ACP calculates path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Reconfiguration tab (see Figure 10.575). 3. If you are using a propagation model that ACP does not natively support, select the Enable precalculated path loss matrices check box. You will then be able to select the propagation model for which ACP will pre-calculate path attentuation. 4. Under Propagation Models, select the check boxes in each column to define how ACP will interact with that propagation model. Not all parameters are available for all propagation models:

Tip:

By default, all available propagation models are displayed. By selecting the Show only used propagation models check box, ACP will only display the propagation models that are actually used.

Antenna masking method: The Antenna masking method indicates whether ACP can use this propagation model natively, or whether ACP uses its own default method. The information in this column can not be edited.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1087

Atoll User Manual Use precalculated path loss: Select the check box in the Use precalculated path loss column corresponding to every propagation model that is not supported natively by ACP or that can not be replaced using ACPs internal default method. Use clutter height: Select the check box in the Use clutter height column if you want ACP to take clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on top of clutter: Select the check box in the Receiver on top of clutter column if you want the receiver height to be sum of the clutter height and the receiver height. This option can be used, for example, to model receivers on top of buildings. Use radial method: Select the check box in the Use radial method column if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

5. Click OK. Important: When you use precalculated path loss matrices, they must be stored externally. For information on storing path loss matrices externally, see "Setting the Storage Location of Path Loss Matrices" on page 171. 6. In the table on the Reconfiguration tab, select the check box in the Precalculated Path Loss Matrices column for each entry in the Tx Name column that uses a propagation model that is not natively supported by ACP (see Figure 10.577).

Figure 10.577: Using precalculated path loss matrices

Importing Network Reconfiguration Parameters

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. To import reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the desired tab. 3. Right-click the table and select Export as Text from the context menu. The Save As dialogue appears. 4. Enter a name in the File name box and click Save. The file will be saved as a tab-delimited text file. 5. Open the text file in another application, for example, in a spreadsheet application, and make the modifications desired. 6. Save the file as a text file and return to Atoll. 7. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear. 8. Under Advanced, click the Import Facility tab. 9. Click the Import from File button. The Open dialogue appears. 10. Browse to the file and click Open. The Import Data dialogue appears (see Figure 10.578).

1088

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.578: Importing site data into the Reconfiguration tab 11. Under Format Parameters, enter the number of the first row with data in the First Imported Row box, select the data Separator, and select the Decimal Symbol used in the file. 12. If you want only the cells in the imported list to be used on the Reconfiguration tab, select the Use Only Cells in List check box. The Use check box will be cleared for all cells that are not in the imported file and they will not be affected by reconfiguration options. 13. In the table, ensure that the column names from the imported file (the Source file) match the column names on the Reconfiguration tab (Destination). You can change the Destination column by clicking the column name and selecting the name from the list. Note: Any values in the imported file for current values can not be imported.

14. Click the Import button to import the file and replace the settings in the Reconfiguration tab.

10.4.3.2.5

Defining Site Selection Parameters

The Reconfiguration tab allows you to select which sites can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly select sites for reconfiguration. In this section, the following are explained: "Selecting Sites for Addition or Removal" on page 1089 "Creating Candidate Sites" on page 1091 "Selecting Sites for Reconfiguration" on page 1092.

Selecting Sites for Addition or Removal

You can use the Reconfiguration tab to select the sites that will be added or removed to improve existing or new networks. To set site selection parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab (see Figure 10.579).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1089

Atoll User Manual

Figure 10.579: Site selection 3. Select the Current Site Selection check box to enable site selection. You can then define how sites will be added or removed. 4. In the table, define how each site will be treated during site selection: a. Select the Locked check box for each site that is not to be affected by site selection.

Tip:

If you have many sites that you do not want to be affected by site selection, you can select and lock them with the Advanced section. For more information on the options in the Advanced section, see "Selecting Sites for Reconfiguration" on page 1092.

b. Select the Status for each site that is not locked: Important: Only active sites are loaded by ACP. If you want inactive sites to be taken into account during site selection, you must set them as active first in Atoll. When you commit the results of the ACP run, all sites and sectors disabled by the ACP will be set to inactive in Atoll. Existing: An "Existing" site is considered as being active in the initial network. ACP will remove an existing site if the Site Removable check box has been checked and if removing the site will improve network quality. If the Sectors Removable check box has been checked, one or more sectors might be removed if removing them will improve network quality. Candidate: A "Candidate" site is considered as being inactive in the initial network. ACP will add the site during the optimisation process if adding the site will improve network quality. If the Sectors Removable check box has been checked, only one or more sectors might be added if adding them will improve network quality. You can define candidate sites by clicking the New Candidate Setup button. For more information on defining candidate sites, see "Creating Candidate Sites" on page 1091. c. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality. d. Select the Site Removable check box for each site that can be removed to improve network quality. e. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group. Note: If a site group has no sites belonging to it, it is automatically deleted.

1090

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks You can create a new group for candidate sites if desired. To create a group: i. Under Group, click the field and select New from the list. The New Site Group dialogue appears (see Figure 10.580).

ii. Enter a Group Name and define the minimum and maximum number of sites from this group (from 0 to 1000) that must be respected by ACP during optimisation (Minimum Site Occurrence and Maximum Site Occurrence, respectively). If there is no minimum or maximum that ACP must respect, leave the field blank. iii. Click OK to create the group and return to the Site Selection tab.

Figure 10.580: Creating a new site group f. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality.

g. Select the Site Removable check box for each site that can be removed to improve network quality. h. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group. Note: If a site group has no sites belonging to it, it is automatically deleted.

You can create a new group for candidate sites if desired. To create a group:

Creating Candidate Sites

The ACP enables you to create a list of candidate sites that can be added to the network to improve quality. For each candidate, you can specify both the location and the station template the candidate site would be based on if the ACP adds it to the network. As well, the ACP can optimise candidate sites when they are added to the network. During optimisation, the ACP will choose first from the sites defined as candidates on the Sites tab and then from the list of candidate sites. To create or edit candidate sites: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab. 3. On the Sites tab, click the New Candidate Setup button. The New Candidate Setup dialogue appears (see Figure 10.581).

Figure 10.581: New Candidate Setup dialogue

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1091

Atoll User Manual 4. Under Zone Configuration, define, if desired, how candidate sites will be treated for each zone: Zone: Select the zone (computation, focus, or hot spot zone defined on the Optimisation tab) from the list. The ACP will add the candidate site according to the quality objectives defined on the Optimisation tab. Default Station Template: Select the station template that any candidate site the ACP adds in the selected zone will be based on. Note: The ACP can optimise each candidate site based on a template. You can set the optimisation parameters for each template by clicking the Template Reconfiguration button. For information on the options, see "Setting Transmitter Reconfiguration Parameters" on page 1085.

Default Group: Select the group that the candidate site will belong to by default. Radio Layer: If there is more than one radio layer, select the radio layer the candidate site will be added to.

5. Under New Candidate List, define the individual candidate sites. For each candidate site set the following: Name: Enter a name for the candidate site. Location: Click the Browse button ( ) to define the location of the candidate site. You can define the location either as a set of co-ordinates or you can select an existing site from a list. Station Template: Select the station template the candidate site will be based on. This selection overrides the selection made under Zone Configuration. Group: Select the group the candidate site will belong to. This selection overrides the selection made under Zone Configuration. Height: The 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 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. Radio Layer: Select the radio layer the candidate site will be added to. This selection overrides the selection made under Zone Configuration.

6. If desired, select the Try to use multi-band antenna when possible check box. The ACP will attempt to use linked transmitters on candidate sites if possible. 7. Click the Action button to update the list of new candidates by selecting one of the following options: Clear List: Select Clear List to delete all current entries in the New Candidate List. Import from File: Select Import from File to import a list of candidate sites, defined as XY coordinates. Import from Current Sites Defined as Location Only: Select Import from Current Sites Defined as Location Only to import as candidate sites sites in the current document that have no transmitters. The sites imported are those in the reconfiguration zone(s) selected on the Optimisation tab. The defined reconfiguration zone(s) is displayed at the top of the Reconfiguration tab as well. Update Candidate Height from Clutter Height: Select Update Candidate Height from Clutter Height to define the height of all candidate sites for each clutter class.

Selecting Sites for Reconfiguration

You can use the Advanced area of the Reconfiguration tab to select sites. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on page 1083. To select sites: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab. 3. Select the Site Selection check box. 4. Click Advanced to display the Advanced area (see Figure 10.582).

1092

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.582: The Advanced section 5. Select the Global Change tab. 6. Select the sites: For entire table: Select For entire table if you want to select all sites in the table. 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 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. Note: This option is only available in co-planning projects with more than one technology.

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. Note: If you want to lock the selected sites, you can select the Set "Locked" check box and click Apply. The locked sites will not be affected by the site addition or removal options.

10.4.3.2.6

Defining Antenna Groups

You can use the Antenna tab to define antenna groups according to their physical characteristics, as well as grouping patterns according to their antenna pattern and defining multi-band antennas. The antenna groups are necessary to apply the antenna type or electrical tilt reconfiguration options defined on the Reconfiguration tab. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on page 1083. 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. In this section, the following are explained: "Creating and Grouping Antennas by Pattern" on page 1094 "Grouping Antennas Automatically" on page 1095 "Defining Multi-band Antennas" on page 1095 "Creating Antenna Groups" on page 1096.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1093

Atoll User Manual

Creating and Grouping Antennas by Pattern

Atoll enables you to create physical antennas by grouping several instances of antennas by their pattern. By setting an option in the ACP.ini file, you can also optimise the additional electrical downtilt (AEDT) of antennas. When you have set this option, you can select which antennas for which you will optimise the AEDT and the range of values that Atoll can chose from during the optimisation process. For information on setting options in the ACP.ini file, see the Administrator Manual. To group antennas by their pattern: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 10.583). The Antenna tab displays all antennas in the Antenna Pattern Table and the groups under Physical Antenna.

Figure 10.583: Antenna tab 3. Click the New button to create a new group under Physical Antenna. You can change the name of the new group or of any group by right-clicking the group name twice under Physical Antenna, selecting Rename from the context menu, and entering the new name. You can delete one group by selecting it under Physical Antenna and clicking the Delete button. You can delete all groups by clicking the Delete All button. 4. Assign antennas to a group to create physical antennas or to associate antenna patterns to define a radiation diagramme of a group of antennas with several variations of electrical tilt: a. Select the group under Physical Antenna. b. Select the antenna under Antenna Pattern Table and click the right arrow between the columns ( ) to assign it to the selected group. Antennas under Antenna Pattern Table that have been assigned to a group are indicated with an icon ( ). You can assign the same antenna to more than one group. You can remove an antenna from a group by selecting it in the group under Physical Antenna and clicking the left arrow between the columns ( Note: ).

When you have grouped the antennas, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antennas will then be grouped automatically according to this definition.

5. If you are also optimising additional electrical downtilt, select the check box in the Use AEDT column corresponding to each antenna for which you want to optimise the additional electrical downtilt and define the limits Atoll must respect by entering values in the Min. AEDT and Max. AEDT for each antenna to be optimised.

1094

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.584: The Antenna Pattern Table with AEDT enabled

Grouping Antennas Automatically

You can group antennas automatically using a regular expression, or "regex." The regular expression is retained from one Atoll session to the next. Therefore, once you have set the regular expression for the given antenna naming convention, you will not have to set again for the next Atoll session. The default regex pattern is overwritten when you change it. You can return to the default regular expression by clearing the text box and clicking OK. You can change the default regular expression by editing the appropriate entry in the ACP.ini file. For more information on the options available in the ACP.ini file, see the Administrator Manual. Important: It is recommended to identify both the antenna type and the electrical tilt in the antenna name in Atoll and to separate the antenna type and electrical tilt with a special character, for example, "_". This will make it easier to group antenna groups automatically using a regular expression. To group antenna automatically: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 10.583 on page 1094). 3. Under Automatic Creation, enter a regular expression, or "regex," in the text box.

Tip:

Clicking the tooltip button ( expressions.

) displays a tooltip with an explanation of common regular

4. Click the Build from expression button to create antenna groups according to the defined regular expression. Note: When you have created the antenna groups, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antenna groups are then automatically created according to this definition.

Defining Multi-band Antennas

When you have grouped antennas according to their physical characteristics as explained in "Creating and Grouping Antennas by Pattern" on page 1094 and "Grouping Antennas Automatically" on page 1095, they are displayed on the Radome tab of the Antenna tab, grouped according to their frequency band. You can merge these groups to create groups of antennas that are multi-band antennas. To define multi-band antennas: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Radome tab (see Figure 10.583 on page 1094).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1095

Atoll User Manual

Figure 10.585: Creating multi-band antennas 3. Create multi-band antennas by merging two or more antenna groups: a. Select two or more antenna groups by holding CTRL and clicking the antenna groups in the Radome Table. b. Click the Merge button. The antenna groups are now merged and will appear on the Antenna Groups tab. You can break the merged antenna groups up by selecting them in the Radome Table and clicking the Unmerge button, or by clicking Unmerge All. If you click Unmerge All, all merged antenna groups will be broken up. 4. Under Automatic Creation, enter a regular expression, or "regex," in the text box.

Creating Antenna Groups

ACP creates antenna groups based on common their frequency band, but you can create antenna groups based on other common characteristics. The antenna groups are used especially to chose between a directive antenna (of 35 degrees) and a less directive one (of 65 degrees). However, in most circumstances, one antenna group corresponds to one antenna radome. To group antennas: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Antenna Groups tab (see Figure 10.583 on page 1094). On the Antenna Groups tab, there is already one group called "Default" in the Antenna Groups pane of the tab. The "Default" group is created automatically by ACP and contains all the antenna patterns available for a given frequency.

1096

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.586: Creating antenna groups 3. Click the New button to create a new group under Antenna Groups. You can change the name of the new group or of any group by right-clicking the group name twice under Antenna Groups, selecting Rename from the context menu, and entering the new name. You can delete one group by selecting it under Antenna Groups and clicking the Delete button. You can delete all groups by clicking the Delete All button. 4. Assign antennas to groups according to their physical characteristics: a. Select the group under Antenna Groups. b. Select the antenna under Radome Table and click the right arrow between the columns ( ) to assign it to the selected group. Antennas under Radome Table that have been assigned to a group are indicated with an icon ( ). You can assign the same antenna to more than one group. You can remove an antenna from a group by selecting it in the group under Antenna Groups and clicking the left arrow between the columns ( Note: ).

When you have created the antenna groups, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antenna groups are then automatically created according to this definition.

10.4.3.2.7

Adding Comments to the Optimisation Setup

You can enter comments about the current optimisation setup on the Comments tab. To add comments: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Comments tab and add your comments.

10.4.3.2.8

Setting Advanced Parameters

The Advanced tab displays the traffic parameters that ACP uses to optimise the Atoll project. You can use the Advanced tab to modify this Atoll data. The Advanced tab is not displayed by default. For information on displaying the advanced parameters, see "Configuring the Default Settings" on page 1072. To set advanced parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1075. 2. Click the Advanced tab. 3. In the left column, click the Expand button ( ) to expand the Parameters folder. 4. In the Parameters folder, select Services. In the Services section, the service-related parameters of the Atoll document are displayed.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1097

Atoll User Manual 5. Under Services, define the body loss for each of the services defined in the Atoll document. 6. In the Parameters folder, select Terminals. In the Terminals section, the terminal-related parameters of the Atoll document are displayed. In a co-planning document, there will be a Terminals folder for each technology. 7. Under Terminals, define the Antenna Gain, the Loss, and the Noise Factor for each terminal. 8. In the Parameters folder, select Clutter Classes. In the Clutter Classes section, the clutter-related parameters of the Atoll document that affect optimisation are displayed. 9. Under Clutter Classes, you can set the following parameters for each clutter class: Height: You can set the Height for each clutter class. Indoor Loss (dB): You can set the Indoor Loss (dB) for each clutter class. The indoor loss is used to calculate shadowing losses on the path loss, as related to the cell edge coverage probability. Model Standard Deviation (dB): You can set the Model Standard Deviation (dB) for each clutter class. The model standard deviation is used to calculate shadowing losses on the path loss, as related to the cell edge coverage probability. C/I Standard Deviation (dB): You can set the Ec/Io Standard Deviation (dB) for each clutter class. The CI standard deviation is used to calculate shadowing losses on the C/I values, as related to the cell edge coverage probability. SU-MIMO Gain Factor: You can set the SU-MIMO Gain Factor for each clutter class. The SU-MIMO gain factor is used to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs in the MIMO tab of reception equipment. Additional STTD/MRC Gain Offset DL (dB): You can set the Additional STTD/MRC Gain Offset DL (dB) for each clutter class. The additional STTD/MRC gain offset DL is added to the users downlink C/(I+N), if the user and the cell support STTD/MRC. Additional STTD/MRC Gain Offset UL (dB): You can set the Additional STTD/MRC Gain Offset UL (dB) for each clutter class. The additional STTD/MRC gain offset UL is added to the users uplink C/(I+N), if the user and the cell support STTD/MRC. Is Indoor: You can define the clutter class as being inside by selecting the Is Indoor check box. You can set default values for all clutter classes for each of these parameters except for height.

Note:

10.4.4

Running an Optimisation Setup

When you have finished defining the optimisation parameters as described in "Defining Optimisation Parameters" on page 1076, you can run the optimisation setup, either immediately by clicking the Run button. You can also save the defined optimisation setup by clicking the Create Setup button and then running the optimisation at a later point. To run a saved optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 3. Right-click the setup folder that you want to run in the ACP - Automatic Cell Planning folder. The context menu appears. 4. Select Run from the context menu. The optimisation setup runs. As the optimisation setup runs, ACP displays the current status of the process (see Figure 10.587) allowing you to observe the progress. You can pause the optimisation if you desire or stop the optimisation early, The Optimisation dialogue has two tabs: Graphs: The Graphs tab displays a graph with the iterations on the X axis and the optimisation objectives (RSCP, EcIo, network quality, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 10.587). The values displayed are indicated with a legend. Quality Maps: The Quality Maps tab displays coverage quality maps for RSCP (Ec) and EcIo improvement. The maps display the computation zone with the network improvement performed to that point. If you based this optimisation on a coverage prediction (see "Setting Objective Parameters" on page 1079), the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default (see "Changing the Display Properties of ACP Maps" on page 1112) or by using a configuration file (see "Configuring the Default Settings" on page 1072).

1098

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.587: The network coverage improvement graphs and maps When the optimisation has finished, the results are stored in the optimisation folder on the Data tab of the Explorer window. By default, Atoll calls the optimisation folder a "Setup" folder. Each setup folder contains one or more optimisation processes. Each optimisation process folder contains the results of that optimisation. For information on viewing optimisation results, see "Viewing Optimisation Results" on page 1100.

Figure 10.588: An optimisation run in the Explorer window Note: You can perform an optimisation on a network that has already been optimised. After running the first optimisation and committing the results, you can create and run a second optimisation, with different parameters on the optimised network.

10.4.5

Working with Optimisations in the Explorer Window

Atoll offers you several options for working with the optimisation that you can access using the context menu on the Data tab of the Explorer window. To work with the optimisation: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 10.589).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1099

Atoll User Manual

Figure 10.589: Options available in the context menu 5. Select one of the following from the context menu: Properties: Selecting Properties from the context menu opens the optimisations Properties dialogue. You can modify all of the optimisation parameters except for the selection of traffic maps (for information on the optimisation parameters, see "Defining Optimisation Parameters" on page 1076). If you want to base an optimisation on different traffic maps, you must create a new optimisation (for information on creating a new optimisation, see "Creating an Optimisation Setup" on page 1075). Run: Selecting Run runs the optimisation setup. The results will be contained in a new optimisation folder in the setup folder. Caution: If you have changed some data in Atoll, for example, if you added transmitters or change some of the transmitter settings, the data that optimisation results are based on may differ from the current Atoll data. If you run a optimisation based on settings made before the changes, it will not take the changed data into consideration. ACP normally detects changes in the Atoll document data and can lock a group if it is impossible to run an optimisation that is coherent with existing data. ACP can lock a group if, for example, when you commit optimisation results after the path losses have been recalculated and are no longer consistent with the data used to run the optimisation. When this happens you will either have to: Create a new optimisation as explained in "Creating a New Optimisation Setup" on page 1075. Duplicate an existing optimisation which will create a new optimisation with the same configuration but with updated parameters. Roll back the previously committed parameters as explained in "The Commit Tab" on page 1107.

Delete: Selecting Delete deletes the defined optimisation setup and any results. Storing optimisation results and the group configuration increase the size of the Atoll file. Deleting unused setups in the ACP - Automatic Cell Planning folder will decrease the size of the Atoll file.

Load Configuration: Selecting Load Configuration displays the Open dialogue. You can then select a PRJ file based on the settings of a different optimisation. When you load a configuration based on a different Atoll document, only the settings that are not specific to that document are loaded. Save Configuration: Selecting Save Configuration displays the Save As dialogue. You can then save the optimisation settings in a PRJ file. You can then use this PRJ file to quickly configure an optimisation.

Tip:

Saving a configuration is a quick way to save the settings you have made in an external file. you can then easily create new configurations using these same settings as a basis without having to recreate them.

Duplicate: Selecting Duplicate displays the ACP Duplicate Options dialogue. You can then duplicate the either the ACP-generated data of selected optimisation setup or all of the data of the setup. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid.

10.4.6

Viewing Optimisation Results

Once you have run the calibrated optimisation as explained in "Running an Optimisation Setup" on page 1098, the results are stored in the optimisation folder on the Data tab of the Explorer window. You can view the results in the optimisations Properties dialogue or in the map window. In this section, the following are explained: "Viewing Optimisation Results in the Properties Dialogue" on page 1101 "Viewing Optimisation Results in the Map Window" on page 1107 "Viewing Optimisation Results Using the Histogram" on page 1113.

1100

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.4.6.1

Viewing Optimisation Results in the Properties Dialogue

You can view the results of the optimisation run in its Properties dialogue in the ACP - Automatic Cell Planning folder. To view the results of the optimisation in its Properties dialogue: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view.

4. Right-click the optimisation. The context menu appears. 5. Select Properties from the context menu. The optimisations Properties dialogue appears. The optimisation results are on individual tabs of the Properties dialogue (with an extra tab, the General tab, that allows you to change the name of the optimisation results): Statistics: The Statistics tab displays a synthesised view of the optimisation results of the quality figures (preamble coverage quality and preamble CINR quality). For more information on the Statistics tab, see "The Statistics Tab" on page 1101. Sectors: The Sectors tab displays a table with the reconfigured cells in green, sites and sectors which have been added or removed, and the coverage quality, the CINR quality, and the preamble power per cell before and after optimisation. For more information on the Statistics tab, see "The Sectors Tab" on page 1102. Graph: The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (preamble coverage quality, preamble CINR quality, and global cost, if you have selected to take cost into consideration) on the Y axis. The values displayed are indicated with a legend. For more information on the Graph tab, see "The Graph Tab" on page 1104. Quality: The Quality tab displays the computation zone with coverage quality maps for preamble coverage before and after optimisation. For more information on the Quality tab, see "The Quality Tab" on page 1105. Change Details: The Change Details tab enables you to analyse the improvement caused by each reconfiguration option. For more information on the Change Details tab, see "The Change Details Tab" on page 1106. Commit: The Commit tab enables you to commit the set of selected changes. For more information on the Commit tab, see "The Commit Tab" on page 1107.

10.4.6.1.1

The Statistics Tab

The Statistics tab displays a synthesized view of the optimisation results of the quality figures (preamble coverage quality and preamble CINR quality).

Figure 10.590: The Statistics tab For the preamble coverage quality and CINR quality, both the initial and final figures are given, as well as the absolute improvement. These figures are given both for the computation zone and the focus zone. If you defined weights for each zone on the Objectives tab of the dialogue used to define the optimisation (see "Setting Objective Parameters" on page 1079), ACP indicates that the results are weighted.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1101

Atoll User Manual You can see more detailed information by clicking the links (see Figure 10.591): Show Change Statistics: The change statistics showing the reconfiguration and site selection statistics. Show Detailed Hot Spot/Clutter Results: The detailed quality figures on each hot spot and by each clutter class. Show Input: The input settings of this optimisation.

Figure 10.591: The Statistics tab - detailed information You can export the results by clicking the Export button. The Save As dialogue that appears allows you to select the format in which you want to save the results: XLS, TXT, HTML, or XML.

10.4.6.1.2

The Sectors Tab

The Sectors tab displays a table with all the cells in the network with the following information: Cells which have been reconfigured are displayed in green (i.e., if they have had their antenna type, antenna height, azimuth, mechanical tilt, or preamble power reconfigured). Sites and sectors which have been added or removed. The preamble coverage quality and CINR quality before and after optimisation. The quality figures are measured on the best server area of each cell. Antenna type, height, azimuth, mechanical tilt, and preamble power initial and final values for each cell.

1102

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.592: The Sectors tab The cell results are displayed in a table. You can access options such as sorting, exporting data using the context menu (see Figure 10.593) sort, column hiding, export, etc.

Figure 10.593: Options available for data in the Sectors tab

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1103

Atoll User Manual

10.4.6.1.3

The Graph Tab

The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (WiMAX coverage, WiMAX CINR, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 10.594). The values displayed are indicated with a legend.

Figure 10.594: The Graph tab The tool bar allows you to: Zoom and span the graph Export to a BMP image file or simple text file Print the graph Show the values along the curves.

Figure 10.595: The Graph tab with the values displayed on the selected point

1104

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.4.6.1.4

The Quality Tab

The Quality tab displays the computation zone with coverage quality maps for preamble coverage and preamble CINR before and after optimisation. You can define the area displayed in the coverage quality maps by selecting the zone (computation, focus, or hot spot) from the list above the maps.

Figure 10.596: Coverage maps on the Quality tab The maps are displayed with a range of values displayed on the right. If you based this optimisation on a coverage prediction (see "Setting Objective Parameters" on page 1079), the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default (see "Changing the Display Properties of ACP Maps" on page 1112) or by using a configuration file (see "Configuring the Default Settings" on page 1072). This range can be modified using the Map Properties dialogue accessed through the tool bar (see Figure 10.597).

Figure 10.597: Defining the display properties of the coverage maps In addition to the map, a histogram is provided for quick evaluation of the improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the Generate Report tool in Atoll which only uses uniform weighting. Note: The default colour range used for display can be changed using the acp.ini preference configuration file. For information on the acp.ini file options, see the Administrator Manual.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1105

Atoll User Manual

10.4.6.1.5

The Change Details Tab

In addition of the map, a histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the Generate Report tool in Atoll which only uses uniform weighting. Note: The default colour range used for display can be changed using the acp.ini preference configuration file. For information on the acp.ini file options, see the Administrator Manual.

Figure 10.598: The Change Details tab You can select a subset of all changes using a slider and view the corresponding performance improvement on the graph. This can enable you to achieve two goals: To select a subset of changes to be implemented. For example, you might find that implementing only one-third of the recommended changes will provide 80% of the benefit. You could then chose to commit only those changes to the Atoll document. To find the optimal order in which to apply these changes in the field, while at the same time avoiding less than optimal performance, or even degrading the performance, during the implementation phase.

Before selecting a subset of recommended changes, it is important to understand that ACP calculates the set of recommendations globally and that these changes are interdependent. During the finalisation step, ACP calculates the ordered list of changes displayed on the Change Details tab by starting from the initial network configuration and iteratively selecting the change that will have the most effect on the network. If you 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 proposed configuration. Important: The data displayed on the other tabs takes all the proposed changes into consideration. If you select only a subset of the proposed changes on the Change Details tab, the statistics displayed on other tabs do not change. When you commit the optimisation changes, ACP will only commit the proposed changes selected on the Change Details tab. For information on committing the optimisation changes, see "The Commit Tab" on page 1107.

1106

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.4.6.1.6

The Commit Tab

This dialogue enables you to commit the set of selected changes (preamble power, antenna, azimuth, tilt, or site selection) to the Atoll document or to roll the network back to its initial state. The Commit tab automatically takes into account the changes selected on the Change Details tab; the Use check box is cleared for any change that was deselected on the Change Details tab.

Figure 10.599: The Commit tab You can select one of the following: Commit: Clicking the Commit button will update the Atoll document with the changes displayed on the Commit tab. Once you have committed the changes, you can recalculate the path losses and use any of the functions available in Atoll, including coverage predictions and simulations. After you perform any such calculations, remember to click the Roll Back to Initial State button to return to the original network settings. Roll Back to Initial State: Clicking the Roll Back to Initial State button will revert the Atoll network to its state before the optimisation was run.

When you click either the Commit button or the Roll Back to Initial State button, information about the commit or rollback process is displayed in the Atoll Event Viewer.

The Effects of Committing or Rolling Back Changes on Existing Setups

When you commit the optimisation results, all existing configuration setups are locked because the network state on which the configuration setup was based is not coherent with the current path losses. ACP automatically detects any incoherence and prevents you from running an optimisation on incoherent data. ACP will unlock the optimisation setups when it becomes possible, for example, when you roll back the data to restore the Atoll state to be coherent with the network state on which the configuration setup was based. It is important to remember that you can commit or roll back other optimisation results even when the setup is locked.

10.4.6.2

Viewing Optimisation Results in the Map Window

ACP can display optimisation results in the form of maps in the map window. This allows you to view the results and facilitates analysis. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default or by using a configuration file. To view the results of the optimisation in the map window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view.

4. Right-click the optimisation. The context menu appears. 5. Select New Map from the context menu. The ACP Map Types dialogue appears (see Figure 10.601).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1107

Atoll User Manual

Figure 10.600: Displaying a new map based on ACP results The maps available in the ACP Map Types dialogue are organised by category. 6. Select the category of maps or click the Expand button ( egory or map. ) to expand the category and then select the sub-cat-

7. Click OK to create the maps. The maps are created and inserted into the folder of the setup containing the optimisation results (see Figure 10.601).

Figure 10.601: The map types correspond to the available results You can display a map by selecting its check box in the folder of the setup containing the optimisation results. The display properties can be changed for a single map or for all maps. For information on the display properties for ACP maps, see "Changing the Display Properties of ACP Maps" on page 1112. The following sections provide more information on the maps: "The Quality Analysis Maps" on page 1108 "The Coverage Analysis Maps" on page 1109 "The Change Analysis Maps" on page 1110 "Best Server Analysis" on page 1111 "Comparing Maps" on page 1111 "Changing the Display Properties of ACP Maps" on page 1112 "Exporting ACP Coverage Maps" on page 1113.

10.4.6.2.1

The Quality Analysis Maps

The quality analysis maps enable you to display the signal quality maps in the Atoll map window. These maps are the same as those displayed on the Quality tab of the optimisations Properties dialogue. The quality analysis maps are the equivalent of maps created by different Atoll coverage predictions: The preamble coverage maps correspond to the Atoll coverage by CI level in WiMAX. For more information, see "Making a Coverage Prediction by C/(I+N) Level" on page 1012. The overlapping zones maps correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 996.

Making these maps available within ACP enables you to quickly validate the optimisation results without having to commit the results and then calculate a coverage prediction in Atoll. The ACP maps display results very similar to those that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before basing

1108

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks any decision to commit the optimisation results on the maps produced by ACP, you should keep the following recommendations in mind: You should verify the results with a different Atoll coverage prediction, such as the pilot pollution prediction. ACP generated maps are generated using the entire set of proposed changes. They do not take into account the change subset defined on the Change Details tab. Multiple carriers are not supported by ACP; the maps are only provided for the requested carrier. Even after committing the optimisation results, differences can remain between the ACP maps and the maps resulting from Atoll coverage predictions.

You can view the exact preamble CINR value on any pixel by letting the pointer rest over the pixel. The preamble CINR value is then displayed in a tooltip. For the overlapping zones map, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Configuring the Default Settings" on page 1072) or by setting the CellOverlap parameter in the acp.ini file.

Figure 10.602: Examples of an overlapping zones map (left) and a preamble CINR variation map (right) For each network quality study, ACP offers a map showing the initial network state, the final network state, and a map showing the changes between the initial and final state.

10.4.6.2.2

The Coverage Analysis Maps

The coverage analysis maps display the coverage status according to the defined threshold used in the optimisation (for both RSCP and EcIo). You can use the coverage analysis maps to quickly see the area where the coverage requirements have been fulfilled. In addition, the thresholds used for clutter and hot spot zones are taken into account. There are two types of coverage analysis maps: Initial and Final Coverage: The initial and final transmitter coverage maps display the areas where there is transmitter coverage and CINR coverage improvement. Coverage Improvement: The transmitter and CINR coverage improvement maps show how the coverage has been improved or degraded by the optimisation.

Figure 10.603: Example of final transmitter coverage/CINR coverage improvement (left) and CINR coverage improvement (right) You can define how the coverage analysis maps will be displayed. To define the coverage analysis map display: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 1107, right-click the Coverage Analysis folder. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears (see Figure 10.604).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1109

Atoll User Manual

Figure 10.604: Defining display and threshold properties 3. Select the Display tab. On the Display tab, you can select the colour used to display initial CINR coverage improvement, final CINR coverage improvement, and both. As well, you can use the slider to adjust the Transparency. 4. Select the Thresholds tab. On the Thresholds tab, you can set the thresholds to be used for the map for the preamble CINR coverage. You can use the same thresholds as you used when you calculated the optimisation, or you can set a different threshold.

10.4.6.2.3

The Change Analysis Maps

The change analysis maps allow you to analyse the changes recommended by the ACP. The change attributes are displayed on the map using a best server map, because the types of changes that ACP recommends are all related to individual cells. The best server map used is usually the initial best server map but you can use the final best server map for new sites (i.e., sites that have been added during optimisation). The following maps are available: Reconfiguration Types: In the Reconfiguration Types folder, there is a separate map for each reconfiguration option displaying the changes to the network: azimuth, mechanical tilt, and antenna. The changes are displayed for the best server zone. The maps can be displayed individually to display each reconfiguration option separately or together to display all reconfiguration options. Sector Selection Types: In the Sector Selection Types folder, there are maps to display which sites have been added or removed. These maps are only available if the site selection was activated during optimisation. Change Order: The Change Order map displays the order of changes (as displayed on the Change Details tab of the optimisations Properties dialogue). You can define the colours used to display the order of changes by right-clicking the Change Order map in the Data tab, selecting Properties from the context menu and then changing the colours on the Display tab. By displaying the Change Order map, you can see where the most important changes to be made to the network are located. Change of Electrical Tilt, Mechanical Tilt, Azimuth, Height, and Preamble Power: These maps show the variation of the given parameter. They can be used to see where in the network this reconfiguration option was changed. Note: The electrical tilt values are calculated using the vertical antenna pattern. The Change of Electrical Tilt map is made available even when the change was to the antenna type.

Figure 10.605: Example of antenna type change (left) and electrical tilt change (right)

1110

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.4.6.2.4

Best Server Analysis

The best server analysis maps contain maps enabling you to analyse cell-related parameters as related to the best server. The following maps are available: Initial and Final Electrical and Mechanical Tilt Values: These maps show the tilt values on the initial and final network. They can be used, for example, to identify areas with strong tilt values. Initial and Final Antenna Height: These maps show the initial and final antenna heights. Initial and Final Transmitter and CINR Coverage: These maps show the percentage of the best server area which is covered according to the defined threshold. The values displayed are the same as those on the Sectors tab of the optimisations Properties dialogue. You can use these maps to quickly identify the cells which potentially have poor quality. Initial and Final Overlapping Ratio: These maps show the percentage of the best server area with overlapping coverage greater than "1," i.e., with several received signals over the defined threshold.

10.4.6.2.5

Comparing Maps
You can compare the results displayed on one map with the results of another map from the same optimisation or from a different optimisation. To compare a map with a map from the same optimisation: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 1107, right-click the map you want to compare. The context menu appears. 2. From the context menu, select Compare With and then select one of the maps in the submenu. A new map is created in the Data tab and the results of the comparison are displayed in the map window. 3. ACP creates a new map in the Data tab and displays it in the map window with the pixels that are displayed on both maps or only on a single map.

Figure 10.606: Comparing two optimisation maps To compare a map with a map from a different map type or with a map from a different optimisation: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 1107, right-click the map you want to compare. The context menu appears. 2. From the context menu, select Compare With > Others. The ACP Compare Map dialogue appears (see Figure 10.607). By default, the ACP Compare Map dialogue displays only maps from the same optimisation as the map you want to compare.

Figure 10.607: The ACP Compare Map dialogue

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1111

Atoll User Manual 3. Define the maps you choose from: Show studies from Predictions folder: Select the Show studies from Predictions folder check box if you want to be able to compare with a map from a coverage prediction you have already created and calculated. Show maps from all ACP setups: Select the Show maps from all ACP setups check box if you want to be able to compare with a map from a different optimisation. Show only maps of same type: Select the Show only maps of same type check box if you want to restrict the maps displayed to maps displaying comparable information.

4. Select the map with which you want to compare the first one and click OK. ACP creates a new map in the Data tab and displays it in the map window with the pixels that are displayed on both maps or only on a single map.

Tip:

By first defining a display interval of "1" in both maps and then comparing them, the resulting comparison map will have more meaningful results. For information on defining "Changing the Display Properties of ACP Maps" on page 1112.

10.4.6.2.6

Changing the Display Properties of ACP Maps

You can define how ACP maps are displayed in the Atoll map window. You can define the colours used as well as the ranges of values on the Display tab of each maps Properties dialogue. As well, ACP allows you to display the value on each pixel in the form of a tooltip. To define the display of an ACP map: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 1107, right-click the map whose display you want to define. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears (see Figure 10.608).

Figure 10.608: Setting the display properties for a map 3. Select the Display tab. 4. On the Display tab, you can define the following settings: Colours: For each range of values, you can click the colour button and select the colour that will be used to represent that range. Min. and Max.: You can define the minimum and maximum values that will define that range. Transparency: You can define the transparency of the map using the slider. Add to legend: You can display the range of values of the optimisation map by selecting the Add to legend. check box. Actions: You can modify the ranges of values by clicking the Actions button and selecting one of the following: Select All: Select Select All to select all the ranges on the display tab. Anything you select after that from the Actions menu (for example, Delete) will be applied to the selected ranges. Delete: Select Delete to delete the selected range or ranges. Insert Before: Select Insert Before to insert a new range before the selected range. Insert After: Select Insert After to insert a new range after the selected range Shading: Select Shading to open the Shading dialogue where you can define all the ranges by setting the first value, the last value, and the step between values, as well as the colour used for the first value and the colour used for the last value. ACP will shade the ranges in between the first and last value with a range of colours going from the first colour to the last.

1112

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Save as Default: Select Save as Default to set the current settings on the display tab to the default settings. These settings can then be used for all maps of the same kind. Load from Default: Select Load from Default to change the current settings to those set as the default using Save as Default. Reset to Default: Select Reset to Default to change the current settings back to the ACP defaults. You can also use Reset to Default to return to the ACP defaults when you have created user-defined defaults using Save as Default.

You can display the value on a pixel by resting the pointer on the pixel in the map window. The value on that pixel will be displayed in a tooltip (see Figure 10.609).

Figure 10.609: Tool tip displaying ACP results on selected point

10.4.6.2.7

Exporting ACP Coverage Maps

ACP enables you to export the optimisation coverage maps as BMP files. Before you can export an optimisation coverage map, you must first select the map and define its appearance as explained in "Viewing Optimisation Results in the Map Window" on page 1107. To export an optimisation coverage map: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( 4. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation map you want to export. ) to expand the optimisation.

5. Right-click the map. The context menu appears. 6. Select Export the Coverage from the context menu. The Save As dialogue appears. 7. Enter a File name for the exported coverage map and select the format from the Save as type list. 8. Click Save. The exported coverage map is saved in the selected format. Depending on the file format selected from the Save as type list, Atoll creates an additional file in the same location containing geo-referencing information: BMP file: Atoll creates a BPW file. ArcView grid (TXT) file: Atoll creates a BPW file. BIL file: Atoll creates a HDR file. GRD or GRC file: Atoll creates a TAB file. PNG file: Atoll creates a PGW file. TIF file: Atoll creates a TFW file.

9. Atoll also creates a BPW file in the same location containing geo-referencing information.

10.4.6.3

Viewing Optimisation Results Using the Histogram

ACP can display optimisation results in the form of a histogram. The histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be used for the histogram, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default or by using a configuration file. To view the results of the optimisation using a histogram: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( 4. Click the Expand button ( Note: ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view. ) to expand the folder of the optimisation.

Depending on the type of optimisation results you want to view, you might need to expand additional folders.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1113

Atoll User Manual 5. Right-click the optimisation results. The context menu appears. 6. Select Histogram from the context menu. The histogram appears in a separate window with a legend on the right side.

10.5

Verifying Network Capacity

An important step in the process of creating a WiMAX network is verifying the capacity of the network. This is done using measurements of the strength of the preamble and traffic signals and C/(I+N) in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: "Importing a Drive Test Data Path" on page 1114 "Displaying Drive Test Data" on page 1116 "Defining the Display of a Drive Test Data Path" on page 1117 "Network Verification" on page 1117 "Exporting a Drive Test Data Path" on page 1122 "Extracting CW Measurements from Drive Test Data" on page 1122 "Printing and Exporting the Drive Test Data Window" on page 1122.

10.5.1

Importing a Drive Test Data Path

In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In WiMAX networks, a cell can be identified by its BSID (6-byte MAC address) or its preamble index. Therefore, you must indicate during the import process which column contains the BSID or the preamble indexes of cells.

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. Click the Data tab in the Explorer window. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the file or files you want to open. You can import one or several files. Note: If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import.

5. Click Open. The Import of Measurement Files dialogue appears. Note: Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue.

6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Configuration, select an import configuration from the Configuration list. b. Continue with step 10.

1114

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Notes: When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. In case several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual. 7. Click the General tab. On the General tab, you can set the following parameters: Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document. 8. Click the Setup tab (see Figure 10.610).

Figure 10.610: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click Setup to link file columns and internal Atoll fields. The Drive Test Data Configuration dialogue appears. c. 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. Note: 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 WiMAX 802.16d drive test data:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1115

Atoll User Manual i. In the BSID Identifier box, enter a string that must be found in the column name identifying 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 WiMAX 802.16e drive test data: i. Select Preamble Index Identifier, if you are importing data using preamble indexes as cell identifiers.

ii. In the Preamble Index Identifier box, enter a string found in the column name identifying 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. iii. Select BSID Identifier, if you are importing data using BSID as cell identifiers. iv. In the BSID Identifier box, enter a string found in the column name identifying 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. f. Click OK. Important: If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Configuration dialogue, Atoll should recognize all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>". 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.

9. If you wish 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 Configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atolls installation folder. 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. Notes: 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 button ( ) in front of the file in the Setup part to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Setup 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 drive test data are imported into the current Atoll document.

10.5.2

Displaying Drive Test Data

When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see the information at that location. To display information about a single drive test data point: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Select the display check box of 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 more information. Atoll displays an arrow pointing towards the serving cell (see Figure 10.612 on page 1120) in the same colour as the transmitter.

1116

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.5.3

Defining the Display of a Drive Test Data Path

You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to define labels, tool tips and the legend. To display the Display tab of a drive test data paths Properties dialogue: 1. Click the Data tab in the Explorer window. 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. The drive test data paths properties dialogue appears. 5. Click the Display tab. Each point can be displayed by a unique attribute or according to: a text or integer attribute (discrete value) a numerical value (value interval).

In addition, you can display points by more than one criterion at a time using the Advanced option in the Display Type list. When you select Advanced from the Display Type list, the Shadings dialogue opens in which you can define the following display for each single point of the measurement path: a symbol according to any attribute a symbol colour according to any attribute a symbol size according to any attribute

You can, for example, display a signal level in a certain colour, choose a symbol type for Transmitter 1 (a circle, triangle, cross, etc.) and a symbol size according to the altitude. Notes: 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 Display if the Fast Display check box has been selected. You can sort drive test data paths in alphabetical order on the Data tab of the Explorer window by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can export the display settings of a drive test data path in a configuration file to make them available for future use. You can export the display settings or import display settings by clicking the Actions button on the Display tab of the drive test data paths Properties dialogue and selecting Export or Import from the menu.

10.5.4

Network Verification
The imported drive test data is used to verify the WiMAX network. To improve the relevance of the data, Atoll allows you to filter out incompatible or inaccurate points. You can then compare the drive test measurements with coverage predictions. To compare drive test data with coverage predictions, you overlay coverage predictions calculated by Atoll with the drive test data path displayed using the same parameter as that used to calculate the coverage prediction. In this section, the following are explained: "Filtering Incompatible Points Along Drive Test Data Paths" on page 1117. "Creating Coverage Predictions from Drive Test Data Paths" on page 1119. "Displaying Statistics Over a Drive Test Data Path" on page 1119. "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1120. "Analysing Data Variations Along the Path" on page 1120.

10.5.4.1

Filtering Incompatible Points Along Drive Test Data Paths

When using a drive test data path, some measured points may present values that are too far outside the median values to be useful. As well, test paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from a more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1117

Atoll User Manual Only one Drive Test Data path: Click the Expand button ( text menu appears. ) to expand the Drive Test Data folder. The con-

3. Select Filter from the context menu. The Drive Test Data Filter dialogue 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. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. The context menu appears. 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 Drive Test Data Filter dialogue appears. 4. Click More. The Filter dialogue appears. 5. Click the Filter tab: a. Select a Field from the list. b. Under Values to Include, you will find all the values represented in the selected field. Select the check boxes next to the values you want to include in the filter. Click Clear All to clear all check boxes. 6. Click the Advanced tab: a. In the Column row, select the name of the column to be filtered on from the list. Select as many columns as you want (see Figure 10.611).

Figure 10.611: The Filter dialogue - Advanced tab b. Underneath the name of each column, 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

Data are kept in the table only if

value equal to X (X may be a number or characters) value not equal to X (X may be a number or characters) numerical value is less than X numerical value is greater than X numerical value is less than or equal to X numerical value is greater than or equal to X text objects which contain X text objects which end with X

1118

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Formula
X*

Data are kept in the table only if

text objects which start with X

7. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering" on page 75. 8. Click OK to apply the filter and close the dialogue. Note: The Refresh Geo Data option available in the context menu of drive test data paths enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones.

10.5.4.2

Creating Coverage Predictions from Drive Test Data Paths

You can create the following coverage predictions for all transmitters on each point of a drive test data path: Point Signal Level Coverage by Signal Level

To create a coverage prediction along a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. 5. Under Standard Studies, select one of the following coverage predictions and click OK: Coverage by Signal Level: Click the Condition tab. At the top of the Condition 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 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. On the Condition 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 1007. 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.

Preamble C/(I+N) (DL): Click the Condition tab. -

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 Studies from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calculations in Atoll). You can display the information in these new columns in the Drive Test Data window. For more information on the Drive Test Data window, see "Analysing Data Variations Along the Path" on page 1120.

10.5.4.3

Displaying Statistics Over a Drive Test Data Path

Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific Drive Test Data path: 1. Click the Data tab in the Explorer window. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1119

Atoll User Manual 4. Select Display Statistics from the context menu. The Measurement and Prediction Fields Selection dialogue appears. 5. Select one or more transmitters from the For the 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.

10.5.4.4

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. Click the Data tab in the Explorer window. 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 dialogue appears. 5. Select a transmitter from the On the Transmitter list. 6. Click the For the Fields list. The list opens. 7. Select the check box beside the field you want 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.

10.5.4.5

Analysing Data Variations Along the Path

In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point. To analyse data variations using the Drive Test Data window. 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 10.612).

Figure 10.612: The Drive Test Data window

1120

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 5. Click the Display button at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 10.613).

Figure 10.613: The Drive Test Data window 6. In the Display Parameters dialogue: Select the check box next to each field you want to display in the Drive Test Data window. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue. Note: 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 window. 7. You can display the data in the drive test data path in the following ways: Click the values in the Drive Test Data window. Click the points on the drive test data path in the map window.

The drive test data path appears in the map window as an arrow pointing towards the best server (see Figure 10.612 on page 1120) in the same colour as the transmitter. 8. 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 dialogue. You select the value to be displayed from the right-hand list at the top of the Drive Test Data window. The values are displayed in the colour defined in the Display Parameters dialogue. 9. You can change the zoom level of the Drive Test Data window display in the Drive Test Data window in the following ways: Zoom in or out: i. Right-click the Drive Test Data window.

ii. Select Zoom In or Zoom Out from the context menu. Select the data to zoom in on: i. Right-click the Drive Test Data window on one end of the range of data you want to zoom in on.

ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data window on the other end of the range of data you want to zoom in on. iv. Select Last Zoom Point from the context menu. The Drive Test Data window zooms in on the data between the first zoom point and the last zoom point. 10. Click the data in the Drive Test Data window to display the selected point in the map window. Atoll will recentre the map window on the selected point if it is not presently visible.

Tip:

If you open the table for the drive test data you are displaying in the Drive Test Data window, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data window (see Figure 10.612 on page 1120).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1121

Atoll User Manual

10.5.5

Exporting a Drive Test Data Path

You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.

10.5.6

Extracting CW Measurements from Drive Test Data

You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears. 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the Transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the For the Fields list. 6. Under CW Measurement Creation Parameters: a. Enter the Min. Number of Points to Extract per Measurement Path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured Signal Levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.

10.5.7

Printing and Exporting the Drive Test Data Window

You can print or export the contents of the Drive Test Data window using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to print or export. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 10.612 on page 1120). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 1120. 6. Right-click the Drive Test Data window. The context menu appears. To export the Drive Test Data window: a. Select Copy from the context menu. b. Open the document into which you want to paste the contents of the Drive Test Data window. c. Paste the contents of the Drive Test Data window into the new document. To print the Drive Test Data window: a. Select Print from the context menu. The Print dialogue appears. b. Click OK to print the contents of the Drive Test Data window.

1122

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.6

Co-planning WiMAX Networks with Other Networks

Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a WiMAX and a GSM network for the same area in Atoll, and then work with Atolls co-planning features to study the mutual impacts of the two networks. Important: Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other networks Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In addition, you can optimise the settings of the two networks using Atolls Automatic Cell Planning (ACP) module. In this section, the following are explained: "Switching to Co-planning Mode" on page 1123. "Working with Coverage Predictions in a Co-Planning Project" on page 1124. "Performing Inter-Technology Neighbour Allocation" on page 1128. "Creating a WiMAX Sector From a Sector in the Other Network" on page 1137. "Using ACP in a Co-planning Project" on page 1137. "Ending Co-planning Mode" on page 1139.

10.6.1

Switching to Co-planning Mode

Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a WiMAX Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, The WiMAX document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Important: Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems. To switch to co-planning mode: 1. Open the main document. Select File > Open or File > New > From an Existing Database.

2. Link the other document with the open main document. a. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document. b. Select File > Link With. The Link With dialogue appears. c. Select the document to be linked. d. Click Open. The selected document is opened in the same Atoll session as the main document and the two documents are linked. The Explorer window of the main document now contains a folder named Transmitters in [linked document], where [linked document] is the name of the linked document and another folder named Predictions in [linked document]. Note: 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1123

Atoll User Manual Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.

Displaying Both Networks in the Same Atoll Document

After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 1123, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the Explorer window of the linked document to the Explorer window of the main document (e.g., you can display GSM sites and measurement paths in a WiMAX document). To display sites from the linked document in the main document: 1. Click the linked documents map window. The linked documents map window becomes active and the Explorer window shows the contents of the linked document. 2. Click the Data tab of the Explorer window. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In > [main document] from the context menu, where [main document] is the name of the main document. 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 rightclicking 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 82. You can also set the tool tips to enable you to distinguish the objects and data displayed on the map. For more information on tool tips, see "Defining the Object Type Tip Text" on page 36. In order to more easily view differences between the networks, you can also change the order of the folders or items in the Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers Using the Explorer" on page 28. Figure 10.614 shows an example of WiMAX transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in a tool tip.

Figure 10.614: GSM and WiMAX Transmitters displayed on the map

10.6.2

Working with Coverage Predictions in a Co-Planning Project

Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate cover-

1124

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks age predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: "Updating Coverage Predictions" on page 1125 "Analysing Coverage Predictions" on page 1125.

10.6.2.1

Updating Coverage Predictions

You can access the properties of the coverage predictions in the linked Predictions folder in the main documents Explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button ( ) in the toolbar.

When you click the Calculate button, Atollfirst calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 185. If you want, you can make Atoll recalculate all path loss matrices, including valid ones, before calculating unlocked coverage predictions in the main and linked Predictions folders. To force Atoll to recalculate all path loss matrices before calculating coverage predictions: Click the Force Calculate button ( ) in the toolbar.

When you click the Force Calculate button, Atoll first removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions defined in the main and linked Predictions folders. Note: 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.6.2.2

Analysing Coverage Predictions

In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tooltips to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which studies to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following are explained: "Co-Planning Coverage Analysis Process" on page 1125 "Displaying the Legend Window" on page 1126 "Comparing Coverage Prediction Results Using Tooltips" on page 1126 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 1127 "Studying Differences Between Coverage Areas" on page 1127.

10.6.2.2.1

Co-Planning Coverage Analysis Process

The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1125

Atoll User Manual

Note:

In a co-planning environment, many sites share the same antennas, using one mast for both technologies. When transmitter, remote antenna, or repeater antennas have the same co-ordinates and the same value set for the SHAREDMAST field in both coplanning documents, Atoll assumes that the antennas are shared. Atoll then automatically synchronises changes made to shared antenna parameters in one coplanning document in the other document. The shared antenna parameters include the site location (X and Y coordinates), the antenna's position relative to the site (Dx, Dy), antenna height, azimuth and mechanical tilt. The SHAREDMAST field is not available by default and must be added in order for the synchronization mechanism to operate. For information on setting up shared antenna parameter synchronisation, see the Administrator Manual.

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 (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the main document. For more information, see "Making a Coverage Prediction by Transmitter" on page 995 and "Making a Coverage Prediction by Signal Level" on page 994. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tool tip contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage predictions Properties dialogue. 4. Make the two new coverage predictions in the linked document accessible in the main document as described in "Displaying Both Networks in the Same Atoll Document" on page 1124. 5. Optimise the main network by changing parameters such as antenna azimuth and tilt or the pilot power. You can use a tool such as the Atoll ACP to optimise the network. Changes made to the shared antenna parameters will be automatically propagated to the linked document. 6. Calculate the coverage predictions in the main document again to compare the effects of the changes you made with the linked coverage predictions. For information on comparing coverage predictions, see "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 1127 and "Studying Differences Between Coverage Areas" on page 1127. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.

10.6.2.2.2

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

10.6.2.2.3

Comparing Coverage Prediction Results Using Tooltips

You can compare coverage predictions by by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltip. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Co-Planning Coverage Analysis Process" on page 1125). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 10.523). The tooltip for the working document is on top and the tooltip for the linked document, with the linked document identified by name is on the bottom.

1126

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.615: Comparing coverage prediction results using tooltips

10.6.2.2.4

Comparing Coverage Areas by Overlaying Coverage Predictions

You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is dislayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 32. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is dislayed on the map. 11. Right-click the coverage prediction. The context menu appears. 12. Select Properties from the context menu. The coverage prediction Properties dialogue 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 "Working with Layers Using the Explorer" on page 28.

10.6.2.2.5

Studying Differences Between Coverage Areas

You can compare coverage predictions to find differences in coverage areas. To compare coverage predictions: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Right-click the coverage prediction of the main document you want to compare. The context menu appears. 5. Select Compare With > [linked coverage prediction] from the context menu, where [linked coverage prediction] is the linked coverage prediction you want to compare with the coverage prediction of the main document. The Comparison Properties dialogue opens. 6. Select the display parameters of the comparison and add a comment if you want. 7. Click OK. The two coverage predictions are compared and a comparison coverage prediction is added to the main documents Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 1002.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1127

Atoll User Manual

10.6.3

Performing Inter-Technology Neighbour Allocation

The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between a WiMAX and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to WiMAX cells In this section, the following are explained: "Setting Inter-Technology Exceptional Pairs" on page 1128 "Configuring Importance Factors for Inter-Technology Neighbours" on page 1130 "Allocating Inter-Technology Neighbours Automatically" on page 1130 "Displaying Inter-Technology Neighbours on the Map" on page 1131 "Allocating and Deleting Inter-Technology Neighbours per Cell" on page 1132 "Calculating the Importance of Existing Inter-technology Neighbours" on page 1135 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 1136.

In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Co-planning Mode" on page 1123.

10.6.3.1

Setting Inter-Technology Exceptional Pairs

You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Exceptional Pairs from the context menu. The Exceptional Pairs of Inter-technology Neighbours table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. d. Atoll fills the Number and Distance (m) fields automatically. In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector). You can access a cells inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cells Properties dialogue: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Double-click the row corresponding to the cell whose properties you want to access. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitters Properties dialogue.

Displaying Inter-Technology Exceptional Pairs on the Map

You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select which exceptional pair links to display: Outwards Non-Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document.

1128

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Inwards Non-Symmetric: Selecting this option displays an exceptional pair link for each transmitter/cell in the linked document that has an exceptional pair defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Forced Neighbours or Forbidden Neighbours from the menu. The exceptional pair of a cell will be displayed when you select a transmitter. 8. Click the Visual Management button ( ) in the Radio toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Visual Management button again. 9. Click a transmitter on the map to show its exceptional pair links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map.

Adding and Removing Inter-Technology Exceptional Pairs on the Map

You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-Technology Exceptional Pairs on the Map" on page 1128. To add a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set an exceptional pair. Atoll adds both transmitters to the list of inter-technology exceptional pairs of the other transmitter. To remove a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes both transmitters from the list of inter-technology exceptional pairs of the other transmitter. To add an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set an exceptional pair. Atoll adds the reference transmitter to the list of inter-technology exceptional pairs of the other transmitter. To remove an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the reference transmitter from the list of inter-technology exceptional pairs of the other transmitter. To add an inwards forced or forbidden exceptional pair: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric exceptional pair relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation. If there is no existing exceptional pair relation between the two transmitters, first create a symmetric exceptional pair relation between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation.

To remove an inwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the transmitter from the inter-technology exceptional pairs list of the other transmitter.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1129

Atoll User Manual

Note:

When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

10.6.3.2

Configuring Importance Factors for Inter-Technology Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. Note: In a GSM project, you must select Neighbours > Configure Importance from the Transmitters folders context menu.

4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when performing automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Inter-Technology Neighbours Automatically" on page 1130.

5. Click OK.

10.6.3.3

Allocating Inter-Technology Neighbours Automatically

Atoll can automatically determine handover relations between networks of different technologies, for example, WiMAX and GSM. In this case, inter-technology handovers from WiMAX to GSM may occur when the WiMAX coverage is not continuous. The networks overall coverage is extended by a WiMAX-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database. To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 5. Click the Inter-technology Neighbours tab. 6. Define the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. 7. Define the maximum number of inter-technology neighbours that can be allocated to a cell in the Max Number of Neighbours box. This value can be either set here for all the cells, or specified for each cell in the Cells table. 8. Clear the Use Overlapping Coverage check box in order to base the neighbour allocation on distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour allocation on coverage conditions. a. Click the Define button to change the coverage conditions for the cells in the main document. The WiMAX Coverage Conditions dialogue appears. In the WiMAX Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the preamble signal level of the best server. The preamble signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document.

1130

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. e. In the % Min. Covered Area box, enter the minimum percentage of the cells coverage area that the neighbours coverage area should also cover to be considered as a neighbour. 9. Under Calculation Options, define the following: Force co-site as neighbours: Selecting the Force co-site as neighbours check box will include the co-site transmitters/cells in the neighbour list of the WiMAX cell. The check box is automatically selected when the neighbour allocation is based on distance. Force exceptional pairs: Selecting the Force exceptional pairs check box will apply the inter-technology exceptional pair criteria on the neighbours list of the WiMAX cell. Delete existing neighbours: Selecting the Delete existing neighbours check box will delete all existing neighbours in the neighbours list and perform a clean neighbour allocation. If the Delete existing neighbours check box is not selected, Atoll keeps the existing neighbours in the list.

10. Click the Calculate button to start calculations. 11. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the names of the neighbours, the number of neighbours of each cell, and the reason they are included in the neighbours list. The reasons include:

Reason
Exceptional Pair Co-site Distance % of covered area and overlapping area Existing

Description
Neighbour relation is defined as an exceptional pair. The neighbour is located at the same site as the reference cell. The neighbour is within the maximum distance from the reference cell. Neighbour relation that fulfils coverage conditions. The neighbour relation existed before running the automatic allocation.

When
Force exceptional pairs is selected Force co-site as neighbours is selected Use Coverage Overlapping is not selected Use Coverage Overlapping is selected Reset is not selected

12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

13. Click the Commit button. The allocated neighbours are saved in the Intra-technology Neighbours tab of each cell. 14. Click Close.

10.6.3.4

Displaying Inter-Technology Neighbours on the Map

You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1131

Atoll User Manual To display neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select the neighbour links to display: Outwards Non-Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Neighbours as the type of neighbour links to display. 8. Click the Visual Management button ( ) in the Radio toolbar. Neighbours are now displayed on the map. Neighbours and displayed until you click the Visual Management button again. 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.

10.6.3.5

Allocating and Deleting Inter-Technology Neighbours per Cell

Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Intertechnology Neighbours table. This section explains the following: "Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1132. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 1133. "Allocating and Removing Inter-Technology Neighbours on the Map" on page 1134.

Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter

1132

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Properties Dialogue
To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Cells tab of the transmitters Properties dialogue: 1. On the main documents map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. 6. If desired, you can enter the Maximum Number of Neighbours. 7. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, and sets the Type to "manual." 8. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 9. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 11. Click OK. In GSM, the inter-technology neighbours tab is available in each transmitters Properties dialogue.

Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table

To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Neighbours from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. To allocate an inter-technology neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Type to "manual." 7. To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. ), select a reference cell in the Cell column.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1133

Atoll User Manual 8. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. 9. To take all exceptionnal pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either forced neighbours or forbidden neighbours using the Exceptional Pairs of Inter-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu.

10. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 11. To delete several symmetric neighbour relations: a. Click in the left margin of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. a. Right-click the Neighbours table. The context menu appears. b. Select Delete Link and Symmetric Relation from the context menu. 12. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector).

Allocating and Removing Inter-Technology Neighbours on the Map

You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-Technology Neighbours on the Map" on page 1131. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. T remove an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the list of inter-technology neighbours of the other transmitter. To add an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. There can be two cases: If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

1134

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the inter-technology neighbours list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

10.6.3.6

Calculating the Importance of Existing Inter-technology Neighbours

After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing inter-technology neighbours: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. Note: In a GSM project, you must select Neighbours > Calculate Importance from the Transmitters folders context menu.

5. Select the Inter-technology Neighbours tab. 6. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance. 7. Clear the Use Overlapping Coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour importance calculation on coverage conditions. 8. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for cells in the main document. The WiMAX Coverage Conditions dialogue appears. In the WiMAX Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the preamble signal level of the best server. The preamble signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1135

Atoll User Manual 9. If you cleared the Use Overlapping Coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. Note: You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

10. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 5. Cause: The reason Atoll has calculated the value in the Importance column. Co-site Symmetry Coverage

Distance: The distance in kilometres between the reference cell and the neighbour.

11. Click Close. The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

10.6.3.7

Checking the Consistency of the Inter-technology Neighbour Plan

You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab.s 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want 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 the Full Lists check box if you want 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 the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax: |CELL|

Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

1136

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 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: Note: |CELL| |NUMBER| |MAX NUMBER| If the field Max number of inter-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

10.6.4

Creating a WiMAX Sector From a Sector in the Other Network

You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main documents map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new WiMAX transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder of the main document. The context menu appears. 4. Select Apply Current Configuration from the context menu.

Figure 10.616: New sector Before and after applying the configuration

10.6.5

Using ACP in a Co-planning Project

Atoll ACP enables you to automatically calculate the optimal network settings in terms of network coverage and capacity in co-planning projects where networks using different technologies, for example, WiMAX and GSM, must both be taken into consideration.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1137

Atoll User Manual When you run an optimisation setup in a co-planning environment, you can display the sites and transmitters of both networks in the document in which you will run the optimisation process, as explained in "Switching to Co-planning Mode" on page 1123. While this step is not necessary in order to create a co-planning optimisation setup, it will enable you to visually analyse the changes to both networks in the same document. Afterwards you can create the new optimisation setup, but when creating an optimisation setup in a co-planning environment, you can not run it immediately; you must first import the other network into the ACP setup. This section explains how to use ACP to optimise network settings in a co-planning project: "Creating a New Co-planning Optimisation Setup" on page 1138 "Importing the Other Network into the Setup" on page 1138.

10.6.5.1

Creating a New Co-planning Optimisation Setup

Once you have displayed both networks in the main document as explained in "Switching to Co-planning Mode" on page 1123, you can create the new co-planning optimisation setup. To create a new co-planning optimisation setup: 1. Click the main documents map window. 2. Click the Data tab in the Explorer window. 3. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 4. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation process. For information on the parameters available, see "Defining Optimisation Parameters" on page 1076. 5. After defining the optimisation setup, click the Create Setup button to save the defined optimisation. The optimisation setup has now been created. The next step is to add the GSM network to the ACP optimisation setup you have just created.

10.6.5.2

Importing the Other Network into the Setup

Once you have created the co-planning optimisation setup, you must import the GSM network. To import the linked network: 1. Click the main documents map window. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 1138. The context menu appears. 5. Select Import Project from the context menu and select the name of the GSM document you want to import into the newly created setup.

ACP displays a dialogue enabling you to define which traffic will be used for the document you are importing. 6. Under Traffic generated from, select one of the following: Uniform traffic: Select Uniform traffic if the traffic in the document you are importing is uniform. Maps based on traffic densities: If the traffic is to be generated from traffic density maps, select Maps based on traffic densities and define the following parameters: When importing a GSM project: Under Traffic parameters, define whether traffic weighting should be applied to Cell Dominance or the BCCH or both by selecting the appropriate check boxes. When importing a WiMAX project: Under Traffic parameters, define whether traffic weighting should be applied to the Preamble CINR or the Preamble Coverage or both by selecting the appropriate check boxes. When importing either a GSM project or a WiMAX project: Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Terminal, and select a Traffic Density File by clicking the Browse button ( ).

1138

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Following traffic maps: Select Following traffic maps if you have traffic maps available and then select the check boxes corresponding to the traffic maps you want to use.

7. Click OK. The setup has been modified to include the linked network. You can modify the parameters for the optimisation setup by right-clicking it on the Data tab of the Explorer window and selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation Parameters" on page 1076. After defining the co-planning optimisation setup: Click the Run button to run the optimisation immediately. For information on running the optimisation, see "Running an Optimisation Setup" on page 1098. For information on the optimisation results, see "Viewing Optimisation Results" on page 1100. Click the Create Setup button to save the defined optimisation to be run later.

10.6.6

Ending Co-planning Mode

once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents. To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select File > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.

10.7

Advanced Configuration
The following sections describe different advanced parameters and options available in the WiMAX module that are used in coverage predictions as well as Monte Carlo simulations. In this section, the following advanced configuration options are explained: "Defining Frequency Bands" on page 1139. "The Global Transmitter Parameters" on page 1140. "Defining Frame Configurations" on page 1143. "Defining WiMAX Radio Bearers" on page 1145. "Defining WiMAX Quality Indicators" on page 1145. "Defining WiMAX Equipment" on page 1146. "Defining WiMAX Schedulers" on page 1148. "Defining Smart Antenna Equipment" on page 1152. "Multiple Input Multiple Output Systems" on page 1153. "Defining the Minimum Signal to Thermal Noise Threshold" on page 1154. "Modelling Shadowing" on page 1154. "Modelling Inter-Technology Interference" on page 1155.

10.7.1

Defining Frequency Bands

To define frequency bands: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Bands from the context menu. 4. In the table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each frequency band, enter: Name: Enter a name for the frequency band, for example, "3.3 GHz - 1.5 MHz." Each WiMAX frequency band has a specific channel bandwidth. Mentioning the channel bandwidth in the frequency band name is a good approach. This name will appear in other dialogues when you select a frequency band. Channel Width (MHz): Enter the channel bandwidth for each channel 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1139

Atoll User Manual

Note:

The relationship between the frequency band (spectrum), the channel width, and the channel numbers can be defined as: Frequency Band Width = Channel Bandwidth x (Last Channel + 1 - First Channel) So, if you have a frequency band of 15 MHz, and you are deploying your network with 1.5 MHz allocated to each cell, you can find the First and Last Channel numbers by: Last Channel - First Channel = (Frequency Band Width/Channel Bandwidth) - 1 If you plan to keep the First Channel number = 0, for our example: Last Channel = (15 MHz/1.5 MHz) - 1 = 9

Excluded Channels: Enter the channel numbers which do not belong to the frequency band. 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. Sampling Factor: Enter the sampling factor for converting the channel bandwidth into the sampling frequency. Duplexing Method: Select the duplexing method used in the frequency band from the list.

5. When you have finished adding frequency bands, click Close. You can also access the properties dialogue of each individual frequency band by clicking the Properties button.

10.7.2

The Global Transmitter Parameters

Atoll allows you to set network level parameters which are common to all the transmitters and cells in the network. These parameters are used in coverage predictions as well as during Monte Carlo simulations by the radio resource management and scheduling algorithms. This section explains the options available on the Global Parameters tab of the Transmitters Properties dialogue, and explains how to access the tab: "The Options on the Global Parameters Tab" on page 1140. "Modifying Global Transmitter Parameters" on page 1142.

10.7.2.1

The Options on the Global Parameters Tab

The global WiMAX parameters include: Frame duration: The frame length in milliseconds. You can choose from a list of frame durations defined in the IEEE 802.16 specifications. 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. The cyclic prefix is the method used by 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. 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, ULMAP, 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. This is the reason why the fixed overheads are available in terms of symbol duration (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 subframe sizes, after the fixed overheads have been removed from the subframe size. 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 cover the entire frame duration but in different frequency bands. In TDD however, the downlink and uplink subframes share the same frequency channel and use parts of the same frame 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 automatically considered to be equal to the remaining part of the frame. In WiMAX 802.16e documents, 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.

1140

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Note:

The exact number of symbol durations in one frame depends on various parameters (channel bandwidth, frame duration, cyclic prefix lengths, sampling factor, etc.). 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, i.e., these are portions of the frame which cannot be used for data transfer. You can enter TTG and RTG times in milliseconds. Serving (reference) cell layer selection method: The reference cell layer selection method is used to determine the reference 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 reference cell is determined according to the selected method: Random: When calculating coverage predictions and in calculations on subscriber lists, the cell of the lowest layer is selected as the serving (reference) cell. In Monte Carlo simulations, a random cell is selected as the serving (reference) cell. Distributive: When calculating coverage predictions and in calculations on subscriber lists, the cell of the lowest layer is selected as the serving (reference) 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 lowest cell layer, the 2nd mobile to the second lowest cell layer, and so on. Min DL Traffic Load: (Not implemented yet) The cell with the lowest downlink traffic load is selected as the serving (reference) cell. If more than one cell has the same lowest downlink traffic load, the first cell among all such cells is selected. During Monte Carlo simulations, as the cell traffic loads might vary, the serving cell for mobiles might also change. Min UL Traffic Load: (Not implemented yet) The cell with the lowest uplink traffic load is selected as the serving (reference) cell. If more than one cell has the same lowest uplink traffic load, the first cell among all such cells is selected. During Monte Carlo simulations, as the cell traffic loads may vary, the serving cell for mobiles may also change.

The Min DL Traffic Load and Min UL Traffic Load options model load balancing between cells. In coverage predictions, the probe mobile selects the least loaded cell. In other words, it tries to keep the traffic load balanced between cells of the transmitter by connecting to the least loaded cell instead of loading the already loaded cells even more. When using either the Random or the Distributive cell layer selection method, the reference cell once assigned to a mobile does not change during Monte Carlo simulations. 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. 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.

The following parameters are only available in WiMAX 802.16e documents (i.e., documents based on the WiMAX 802.16e project template). 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 dialogue. For more information on the permutation zone quality threshold, see "Defining Frame Configurations" on page 1143.

The following parameters are only available in WiMAX 802.16d documents (based on the WiMAX 802.16d project template). Number of subchannels per channel: A channel can be divided into a number of subchannels. You can set the number of these subchannels at the network level in Atoll. Number of subcarriers per channel: The entire channel contains a number of subcarriers which compose 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 computed 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1141

Atoll User Manual

Note:

The term subcarrier is synonymous with tone.

Figure 10.617 depicts a WiMAX frame with the described parameters marked.

Figure 10.617: WiMAX Frame

10.7.2.2

Modifying Global Transmitter Parameters

You can change global transmitter parameters on the Global Parameters tab of the Transmitters Properties dialogue. To set the network level parameters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Global Parameters tab. In this tab you can set the frame structure parameters. Frame Structure: In this section (see Figure 10.618), you can modify the following: the Frame Duration of WiMAX frame, the Cyclic Prefix Ratio, the fixed and variable overheads for the uplink and the downlink subframes, and, for TDD networks, the downlink-to-uplink subframe ratio (DL:UL Ratio) either as a percentage or (WiMAX 802.16e only) as a fraction of the number of available symbol durations in one frame, and the transmission and reception time guards (TTG and RTG). The DL:UL ratio entered as a fraction must include the symbol duration(s) used by the preamble or any other fixed-duration 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. 5. Click the Advanced button. The Advanced Parameters dialogue appears. 6. In the Advanced Parameters dialogue, you can set: Serving Cell Layer Selection: In this section, you can choose the serving cell layer selection Method. Uplink Power Control: In this section, you can enter the uplink power control Margin. Adaptive MIMO Switching: In this section, you can choose the adaptive MIMO switching Criterion. Permutation Zone Selection: In this section, you can choose the permutation zone selection Criterion.

1142

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.618: Common Global Parameters The following section is only available in WiMAX 802.16d documents (i.e., documents based on the WiMAX 802.16d project template). Channel Configuration: In this section, you can enter the following: the number of subchannels per channel, the total number of subcarriers per channel, the number of used subcarriers per channel and the number of data subcarriers per channel.

Figure 10.619: WiMAX 802.16d-specific Global Parameters 7. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.

10.7.3

Defining Frame Configurations

Frame configurations and permutation zones are only available in WiMAX 802.16e documents (based on the WiMAX 802.16e project template). The SOFDMA frame configuration model uses different numbers of subcarriers for different channel bandwidths. As well, there can be up to 8 different permutation zones in the downlink subframe and 3 in the uplink subframe. Each permutation zone can use a different subchannel allocation mode, and may have different numbers of used and data subcarriers. The Frame Configurations table in Atoll models the channel and frame configuration of a cell. To create a new frame configuration: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frame Configurations from the context menu. The Frame Configurations table appears. 4. In the Frame Configurations table, each row describes a frame configuration. For the new frame configuration, enter: Name: The name of the frame configuration. Total Number of Subcarriers: The total number of subcarriers per channel. Segmentation Support: Select the Segmentation Support check box if the first PUSC permutation zone in the downlink is segmented. Number of Preamble Subcarriers: The number of subcarriers used for the transmitting the preamble. This is the number of subcarriers used when the preamble is not segmented. For a segmented frame configuration, the number of subcarriers used by the segmented preamble are determined automatically from this value during calculations.

5. Double-click the frame configuration row in the table once the new frame configuration has been added to the table. The frame configurations Properties dialogue opens (see Figure 10.620). 6. Under the General tab, you can modify the parameters that you set previously. 7. Under the Permutation Zones tab, you have the following parameters: Zone Number: The permutation zone number. Active: Whether the permutation zone is active or not. Only active permutation zones are considered in calculations.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1143

Atoll User Manual Subchannel Allocation Mode: The subchannel allocation mode used by the permutation zone. You can select from PUSC DL, PUSC, FUSC, OFUSC, AMC, TUSC1, and TUSC2 for the downlink subframe, and from PUSC UL, OPUSC, and AMC for the uplink subframe. Number of Used Subcarriers: The number of subcarriers used for transmission. This number includes the pilot and data subcarriers. Number of Data Subcarriers: The number of subcarriers used for data transfer. Number of Subchannels per Channel: The number of subchannels in the channel. Subframe: Whether the permutation zone belongs to the downlink or the uplink subframe. Quality Threshold: The minimum preamble C/N or C/(I+N) required for a user to be allocated the permutation zone. Note: Make sure that the permutation zone quality threshold values respect the traffic power reduction defined for the cell, and whether the frame configuration supports segmentation or not. The quality threshold for a permutation zone is calculated in one of two ways: For any permutation zone of a frame configuration that does not support segmentation, or for the segmented permutation zone in a frame configuration that supports segmentation, the quality threshold is calculated as follows: Quality Threshold (Preamble C/N) = Required Traffic C/N + Traffic Power Reduction For a non-segmented permutation zone in a frame configuration that supports segmentation, the quality threshold is calculated as follows: Quality Threshold (Preamble C/N) = Required Traffic C/N + Traffic Power Reduction + Power Concentration Gain Where the power concentration gain is equal to Preamble 1 10 Log ---------------------- = 10 Log ( 3 ) = 4.77 dB , with f Segment being the preamble Preamble f Segment segmenting factor signifying that a segmented preamble uses 1/3rd of the used subcarriers in the channel. For example, if the required traffic C/N is 15 dB and the traffic power reduction is 3 dB, the quality threshold for the segmented permutation zone in this case would be 18 dB, and for a non-segmented permutation zone would be 22.77 dB. Max Speed: The maximum vehicular speed supported 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, SU-MIMO, MU-MIMO, or AMS) at a time. Specific calculations will be performed (and gains will be 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. Max Distance: The maximum distance from the base station covered by the permutation zone. Subchannel Groups (Segment 0): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned to the segments 0. Subchannel Groups (Segment 1): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned to the segments 1. Subchannel Groups (Segment 2): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned to the segments 2.

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. To see examples of how to setup cells with and without segmentation, and how to setup cells with PUSC, FUSC, and permutation zones of other subchannel allocation modes, see "Tips and Tricks" on page 1157.

1144

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.620: Permutation Zones

10.7.4

Defining WiMAX Radio Bearers

WiMAX radio bearers carry the data in the uplink as well as in the downlink. Note: In the Atoll WiMAX module, a "bearer" refers to a combination of MCS, i.e., modulation, and coding schemes.

The WiMAX Bearers table lists the radio bearers available in Atoll by default. You can add, remove, and modify bearer properties, if you wish. To define WiMAX bearers: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > WiMAX Bearers from the context menu. The WiMAX Bearers table appears. 4. In the table, enter one bearer per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each WiMAX bearer, enter: 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 WiMAX equipment. Name: Enter a name for the bearer, for example, "16QAM3/4." This name will appear in other dialogues 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 1160. 5. Click the Close button ( ) to close the WiMAX Bearers table.

10.7.5

Defining WiMAX Quality Indicators

Quality indicators depict the coverage quality at different locations. The Quality Indicators table lists the quality indicators available in Atoll by default. You can add, remove and modify quality indicators, if you wish. To define quality indicators: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Quality Indicators from the context menu. The Quality Indicators table appears. 4. In the table, enter one quality indicator per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each quality indicator, enter: Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in other dialogues 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. ) to close the Quality Indicators table.

5. Click the Close button (

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1145

Atoll User Manual

10.7.6

Defining WiMAX Equipment

WiMAX equipment model the reception characteristics of cells and user terminals. Bearer selection thresholds and channel quality indicator graphs are defined in WiMAX equipment. To create a new piece of WiMAX equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Equipment > WiMAX Equipment from the context menu. The WiMAX Equipment table appears. 4. In the WiMAX Equipment table, each row describes a piece of equipment. For the new piece of equipment you are creating, enter its name. 5. Double-click the equipment entry in the WiMAX Equipment table once your new equipment has been added to the table. The equipments Properties dialogue opens. The Properties dialogue has the following tabs: Bearer Selection Thresholds: In this tab (see Figure 10.621), 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 carrierto-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 1145 and "Modelling Mobility Types" on page 1008, respectively.

Figure 10.621: WiMAX Equipment - Bearer Selection Thresholds i. Click the Best Bearer Thresholds button to open the C/(I+N) Thresholds (dB) dialogue (see Figure 10.622).

ii. Enter the graph values. iii. Click OK.

Figure 10.622: C/(I+N) Thresholds (dB) dialogue For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresholds" on page 1158. For converting receiver equipment sensitivity values (dBm) into bearer selection thresholds, see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1159. Quality Graphs: On this tab (see Figure 10.623), you can modify the Quality Indicator Graphs for different bearers for different mobility types. These graphs depict the behaviour of various quality indicators under different radio conditions. For more information on bearers, quality indicators, and mobility types, see "Defining

1146

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks WiMAX Radio Bearers" on page 1145, "Defining WiMAX Quality Indicators" on page 1145, and "Modelling Mobility Types" on page 1008, respectively.

Figure 10.623: WiMAX Equipment - Quality Indicator Graphs i. Click the Quality Graph button to open the Quality Graph dialogue (see Figure 10.624).

ii. Enter the graph values. iii. Click OK.

Figure 10.624: Quality Indicator Graph dialogue MIMO: On this tab (see Figure 10.625), you can modify the SU-MIMO and STTD/MRC gains for different bearers, mobility types, subchannel allocation modes (WiMAX 802.16e), BLER values, and numbers of transmission and reception antennas. The capacity gain due to spatial multiplexing is the increase in channel capacity compared to a SISO system. For more information on bearers and mobility types, see "Defining WiMAX Radio Bearers" on page 1145 and "Modelling Mobility Types" on page 1008, respectively. For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on page 1153.

Note:

No MIMO gain (STTD/MRC, SU-MIMO, and MU-MIMO) is applied if N Ant = N Ant = 1 .

TX

RX

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1147

Atoll User Manual

Figure 10.625: WiMAX Equipment - MIMO gains i. Enter the STTD/MRC Gain for a combination of Subchannel Allocation Mode (WiMAX 802.16e), Mobility, Radio Bearer Index, Max BLER, Number of Transmission Antennas, and Number of Reception Antennas.

ii. Click the Max SU-MIMO Gain Graphs button to open the Max SU-MIMO Gain dialogue for a combination of Subchannel Allocation Mode (WiMAX 802.16e), Mobility, Radio Bearer Index, Max BLER, Number of Transmission Antennas, and Number of Reception Antennas (see Figure 10.626). iii. Enter the graph values. iv. Click OK. You can define the STTD/MRC and SU-MIMO gains for a specific combination of subchannel allocation mode, mobility type, bearer, and BLER, as well as the default gains for "All" subchannel allocation modes, "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.

Figure 10.626: Max SU-MIMO Gain dialogue 6. Click OK. The Properties dialogue closes. The settings are stored. 7. Click the Close button ( ) to close the WiMAX Equipment table.

10.7.7

Defining WiMAX Schedulers

In Atoll, schedulers perform the selection of users for resource allocation, the radio resource allocation and management according to the QoS classes of the services being accessed by the selected users. WiMAX has the following QoS classes:

1148

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

QoS Class
UGS ErtPS rtPS nrtPS Best Effort

Priority
Highest : : : Lowest

Throughput Demands
Min Throughput Demand = Max Throughput Demand Min Throughput Demand Max Throughput Demand Min Throughput Demand Max Throughput Demand Min Throughput Demand Max Throughput Demand Min Throughput Demand = 0 Max Throughput Demand

The scheduling process is composed of the following three steps: 1. Selection of users for resource allocation: The Max Number of Users defined for each cell is the maximum number of users that the cells scheduler can work with simultaneously. At the start of the scheduling process, the scheduler 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 until there are no more resources to allocate. 2. Resource allocation for supporting the Min Throughput Demands: The first four QoS classes have a minimum throughput demand requirement. This is the minimum data rate that a service of one of these QoS classes 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, to users of these QoS classes in the order of priority. The final service priority is determined based on the QoS class as well as the Priority parameter defined for the service. For example, if there are two services of each QoS class with different priorities, the order of resource allocation will be as follows: i. Users of a service with QoS class = UGS, Service priority = 1

ii. Users of a service with QoS class = UGS, Service priority = 0 iii. Users of a service with QoS class = ErtPS, Service priority = 1 iv. Users of a service with QoS class = ErtPS, Service priority = 0 v. Users of a service with QoS class = rtPS, Service priority = 1 vi. Users of a service with QoS class = rtPS, Service priority = 0 vii. Users of a service with QoS class = nrtPS, Service priority = 1 viii. Users of a service with QoS class = nrtPS, Service priority = 0 In order to be connected, users who are active in downlink and uplink must be able to get their minimum throughput in both directions. If a user who is 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. 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 -- % of resources available for QoS Class i = ---------------------------------- 100 i N 1 i --

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1149

Atoll User Manual 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 def Bias QoS termined from the QoS Class Bias Factor f Bias as follows: = 1 + ---------- . 100
QoS

Note:

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, f Bias = 90 gives = 0.1 which allocates (approximately): 0.1 % resources to ErtPS; 0.9 % resources to rtPS; 9 % resources to nrtPS; 90 % resources to Best Effort. f Bias = 9900 gives = 100 which allocates (approximately): 90 % resources to ErtPS; 9 % resources to rtPS; 0.9 % resources to nrtPS; 0.1 % resources to Best Effort.
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 all the resources they require. The end result of this scheduling method is that the aggregate 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 schedulers available in Atoll by default. You can add, remove, and modify scheduler properties, if you wish. To define WiMAX schedulers: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Schedulers from the context menu. The Schedulers table appears. 4. In the table, enter one scheduler per row. For information on working with data tables, see "Working with Data Tables" on page 53. 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 voice-type services. Target Throughput for Data Services: Select the throughput that the scheduler will target to satisfy for all data-type 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 WiMAX 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 WiMAX 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 WiMAX equipment. Uplink Bandwidth Allocation Target (WiMAX 802.16e): Select the goal of the uplink subchannelisation (bandwidth allocation). - Full Bandwidth: All the subchannels are used for the uplink C/(I+N) calculations, i.e., 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. The definition of the lowest bearer depends on the Bearer Selection Criterion, i.e., lowest index, lowest peak MAC throughput, or lowest effective MAC throughput. - 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. In WiMAX 802.16d, subchannelisation is performed in order to maintain the connection in uplink. However, the reduction in the number of used subchannels is not carried out one by one. The number of uplink subchannels is reduced from 16 to 8, to 4, to 2, and to 1.

1150

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 5. Click the Close button ( ) to close the Schedulers table.

10.7.8

Smart Antenna Systems

Smart antenna systems use digital signal processing with more than one antenna element in order to locate and track various types of signals to dynamically minimize interference and maximize the useful signal reception. Different types of smart antenna techniques exist, including beam-switching, beam-steering, beam-forming, etc. Adaptive antenna systems are capable of using adaptive algorithms to cancel out interfering signals. Atoll includes two smart antenna models. The conventional beamformer performs beamforming in downlink and uplink. The optimum beamformer performs beamforming in downlink, and beamforming and interference cancellation in the uplink using an MMSE (Minimum Mean Square Error) algorithm. Smart antennas dynamically calculate and apply the smart antenna weights on each antenna element in order to create beams in the direction of served users. In uplink, the Minimum Mean Square Error algorithm models the effect of null steering towards interfering mobiles. The antenna patterns created for downlink transmission have a main beam pointed in the direction of the useful signal. For the optimum beamformer, in the uplink, in addition to the main beam pointed in the direction of the useful signal, there can 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 interference is not stationary but moving, the antenna patterns are adjusted so that the nulls remain in the direction of the moving interference. A system using adaptive antennas adjusts the weighting on each antenna element so as to achieve such a pattern. Atolls smart antenna models support linear adaptive array systems. TDD WiMAX networks are more suitable for smart antennas than FDD because the uplink and downlink channel characteristics are similar, and information gathered from a mobile in the uplink can be directly used for downlink estimations by the base station. Atolls WiMAX BWA module includes the following smart antenna modelling types: "Optimum Beamformer" on page 1151. "Conventional Beamformer" on page 1151.

The following section explains how to work with smart antenna equipment in Atoll: "Defining Smart Antenna Equipment" on page 1152.

10.7.8.1

Optimum Beamformer
The optimum beamformer works by forming beams in the downlink in the direction of the served mobiles, and cancelling uplink interference from mobiles by using the Minimum Mean Square Error adaptive algorithm. The following paragraphs explain how the model is used in Monte Carlo simulations and in coverage prediction calculations. Modelling in Monte Carlo Simulations: In the downlink, 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 and the downlink CINR calculated by taking into account the effects of beamforming. In the uplink, the powers received from served mobiles include the beamforming gains in their directions. For taking into account the interfering mobiles, an inverse noise correlation matrix is calculated for each cell. Interference cancellation is modelled using the MMSE adaptive algorithm. For each pair of interfered and interfering users, the received interference and its direction are memorised. At the end of a simulation, this results in an angular distribution of the uplink noise rise calculated from the inverse noise correlation matrix. The smart antenna simulation results include the angular distribution of the transmitted power spectral density (downlink) and the angular distribution of the noise rise (uplink) for each cell. These results are then used to carry out CINR-based coverage predictions for base stations using smart antennas. Modelling in Coverage Predictions: The smart antenna results from Monte Carlo simulations are used in coverage predictions. In downlink, 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. In uplink, beamforming is performed to calculate the smart antenna gain towards each pixel of the studied cell dynamically in order to determine the received power. The interference is read from the angular distribution of the uplink noise rise (simulation result) calculated for the studied cell.

10.7.8.2

Conventional Beamformer
The conventional beamformer works by forming beams in the downlink and uplink in the direction of the served mobiles. This section explains how the model is used in Monte Carlo simulations and in coverage prediction calculations. Modelling in Monte Carlo Simulations: In the downlink, 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1151

Atoll User Manual mobile being served. Beamforming is performed in interfered as well as interfering cells and the downlink CINR calculated by taking into account the effects of beamforming. In the uplink, the powers received from served mobiles include the beamforming gains in their directions. To take into account the interfering mobiles, an inverse noise correlation matrix is calculated for each cell. For each pair of interfered and interfering users, the received interference and its direction are memorised. At the end of a simulation, this results in an angular distribution of the uplink noise rise calculated from the inverse noise correlation matrix. The smart antenna simulation results include the angular distribution of the transmitted power spectral density (downlink) and the angular distribution of the noise rise (uplink) for each cell. These results are then used to carry out CINR-based coverage predictions for base stations using smart antennas. Modelling in Coverage Predictions: The smart antenna results of Monte Carlo simulations are used in coverage predictions. In downlink, 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. In uplink, beamforming is performed to calculate the smart antenna gain towards each pixel of the studied cell dynamically in order to determine the received power. The interference is read from the angular distribution of the uplink noise rise (simulation result) calculated for the studied cell.

10.7.8.3

Defining Smart Antenna Equipment

Smart antenna equipment model adaptive antenna systems with more than one antenna element. Atoll WiMAX BWA module includes two smart antenna models, a conventional beamformer and an MMSE-based (Minimum Mean Square Error) optimum beamformer. For more information on these smart antenna models in Atoll, see the Technical Reference Guide To create a smart antenna equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Equipment > Smart Antenna Equipment from the context menu. The Smart Antenna Equipment table appears. 4. In the Smart Antenna Equipment table, each row describes a piece of smart antenna equipment. For information on working with data tables, see "Working with Data Tables" on page 53. For the new smart antenna equipment, enter: Name: Enter a name for the smart antenna equipment. Antenna Model: Select Optimum Beamformer or Conventional Beamformer from the list. Main Antenna Model: Select the main antenna model to be used with the smart antenna equipment. The list contains the antennas available in the Antennas folder. When you assign the smart antenna equipment to a transmitter, you can choose to replace the current main antenna model with this model.

5. Click the Properties button. The smart antenna properties dialogue appears. In the smart antenna properties dialogue you can modify the smart antenna equipment properties. You can also modify the properties of the model. To modify the properties: a. Click the Parameters button. The smart antenna models properties dialogue appears. b. Click the General tab. On the General tab, you can change the default Name of the smart antenna model. c. Click the Properties tab (see Figure 10.627). 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.

Figure 10.627: Smart antenna model properties d. Click OK. The smart antenna model properties are saved. 6. Click OK. The smart antenna equipment properties are saved. 7. When you have finished adding smart antenna equipment, click Close.

1152

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

10.7.9

Multiple Input Multiple Output Systems

Multiple Input Multiple Output (MIMO) systems use different transmission and reception diversity techniques. MIMO diversity systems can roughly be divided into the following types, all of which are modelled in Atoll:

Space-Time Transmit Diversity and Maximum Ratio Combining

STTD uses more than one transmission antenna to send more than one copy of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining, MRC) at the receiver to extract the useful signal. Because the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, STTD improves the C/(I+N) at the receiver. It is often used for the regions of a cell that have bad C/(I+N) conditions. STTD is also known as STC (Space Time Coding) and STBC (Space-Time Block Codes). In Atoll, you can set whether a cell (WiMAX 802.16d) or a permutation zone (WiMAX 802.16e) supports STTD/MRC by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 972) or frame configuration properties (see "Defining Frame Configurations" on page 1143). STTD/MRC gains on downlink and uplink can be defined in the WiMAX equipment for different numbers of transmission and reception antennas, mobility types, bearers, subchannel allocation modes (WiMAX 802.16e), and maximum BLER. For more information on uplink and downlink STTD/ MRC gains, see "Defining WiMAX Equipment" on page 1146. Additional gain values can be defined per clutter class. For information on setting the additional STTD/MRC uplink and downlink gains for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 121. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell (uplink or downlink permutation zone in WiMAX 802.16e) that supports STTD/MRC, will benefit from the downlink and uplink STTD/MRC C/(I+N) gains.

Single-User MIMO or Spatial Multiplexing

SU-MIMO uses more than one transmission antenna to send different signals (data streams) on each antenna. The receiver can also have more than one antenna to receive different signals. Using spatial multiplexing with M transmission and N reception antennas, the throughput over the transmitter-receiver link can be theoretically increased M or N times, depending on which is smaller. 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 simply MIMO. In Atoll, you can set whether a cell (WiMAX 802.16d) or a permutation zone (WiMAX 802.16e) supports SU-MIMO by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 972) or frame configuration properties (see "Defining Frame Configurations" on page 1143), respectively. SU-MIMO capacity gains can be defined in the WiMAX equipment for different numbers of transmission and reception antennas, mobility types, bearers, subchannel allocation modes (WiMAX 802.16e), and maximum BLER. For more information on SU-MIMO gains, see "Defining WiMAX Equipment" on page 1146. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell (uplink and downlink permutation zones in WiMAX 802.16e) that supports 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 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 121. 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 C (I + N) TX RX Where CC MIMO = Min ( N Ant, N Ant ) Log 2 1 + ------------------------------------------ is the channel capacity at a given C/(I+N) for a MIMO TX RX Min ( N Ant, N Ant ) system 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.
TX RX

Adaptive MIMO Switch

Adaptive MIMO switch is a technique for switching from SU-MIMO to STTD/MRC as the preamble signal conditions get worse than a given threshold. AMS can be used in cells to provide SU-MIMO gains to users that have better preamble CN conditions than a given AMS threshold, and STTD/MRC gains to users that have worse preamble CN or C/(I+N) conditions than the threshold. AMS provides the optimum solution using STTD/MRC and SU-MIMO features to their best.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1153

Atoll User Manual During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell (uplink and downlink permutation zones in WiMAX 802.16e) that supports AMS, will benefit from the gain to be applied, STTD/MRC or SU-MIMO, depending on the users preamble C/N or C/(I+N) and the AMS threshold defined in the cell properties. STTD/MRC gain is applied to the users traffic C/(I+N) if the users preamble C/N or C/(I+N) is less than the AMS threshold, and SU-MIMO is used if the preamble C/N or C/(I+N) is higher than the AMS threshold.

Multi-User MIMO or Collaborative MIMO

MU-MIMO (Multi-User MIMO) or Collaborative MIMO is a technique for spatially multiplexing more than one user who has good enough radio conditions at his location. This technique is used in uplink so that a cell with more than one reception antenna can receive uplink transmissions from two different users over the same frequency-time allocation. This technique provides considerable capacity gains in uplink, and can be used with single-antenna user equipment, i.e., it does not require more than one antenna at the user equipment as opposed to SU-MIMO, which only provides considerable gains with more than one antenna at the user equipment. In Atoll, you can set whether a cell (WiMAX 802.16d) or an uplink permutation zone (WiMAX 802.16e) supports MU-MIMO in uplink by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 972) or frame configuration properties (see "Defining Frame Configurations" on page 1143), respectively. MU-MIMO capacity gains result from the scheduling and the RRM process. Using MU-MIMO, schedulers are able to allocate resources over two spatially multiplexed parallel frames in the same frequency-time resource allocation plane. MU-MIMO can only work under good radio conditions and if the cell has more than one reception antenna. Therefore, the preamble C/N must be higher than the MU-MIMO threshold defined by cell in order for the scheduler to be able to multiplex users in uplink. During the calculation of Monte Carlo simulations in Atoll, each new user connected to the first antenna creates virtual resources available on the second antenna. These virtual resources can then be allocated to a second user connected to the second antenna without increasing the overall load of the cell. This way, each new mobile consumes the virtual resources made available be the previous mobile, and might create new virtual resources available on the other antenna. The MU-MIMO capacity gain resulting from this uplink collaborative multiplexing is simply the ratio of the traffic loads of all the mobiles connected to both parallel frames in uplink to the uplink traffic load of the cell. MU-MIMO is only possible for mobiles that support MIMO and at which the preamble C/N is greater than the MU-MIMO threshold defined for their serving cell. The MU-MIMO capacity gain can be defined per cell by the user or it can be an output of Monte Carlo simulations. This gain is used during the calculation of uplink throughput coverage predictions. The channel throughput is multiplied by this gain for pixels where MU-MIMO is used as the diversity mode.

10.7.10

Defining the Minimum Signal to Thermal Noise Threshold

In Atoll, you can define a limit on the received signal level with respect to the thermal noise level. This value is used by Atoll to limit the input of interferers in calculations. The performance of C/(I+N)-based coverage predictions, interference matrices calculations, and Monte Carlo simulatinos can be improved by setting a high value of the minimum signal to thermal noise threshold. This value is used as a filter criterion on interferers. Atoll will discard all interferers with a signal to thermal noise level lower than this value. To define the minimum signal to thermal noise threshold: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Predictions tab. 5. Under Calculation Limitation, enter a Min C/N Threshold in dB. 6. Click OK.

10.7.11

Modelling Shadowing
Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be better and in 50% of the measured cases, the result will be worse. Atoll uses a model standard deviation for the clutter class with the defined cell edge coverage probability to model the effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. 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 WiMAX 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 121.

1154

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Shadowing can be taken into consideration when Atoll calculates the signal level and C/(I+N) for: A point analysis (see "Making a Point Analysis to Study the Profile" on page 984) A coverage prediction (see "Studying Signal Level Coverage" on page 985).

Atoll always takes shadowing into consideration when calculating a Monte Carlo-based WiMAX simulation. 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 WiMAX coverage predictions. You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter Class" on page 1155.

10.7.11.1

Displaying the Shadowing Margins per Clutter Class

To display the shadowing margins per clutter class: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears (see Figure 10.628). 4. You can set the following parameters: Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin: From 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.

5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.

Figure 10.628: The Shadowing Margins dialogue

10.7.12

Modelling Inter-Technology Interference

Analyses of WiMAX networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a WiMAX network. Atoll can take into account interference from co-existing networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modeled in Atoll: Interference received by mobiles on the downlink: Interference can be received by mobiles in a 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) may be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (CDMA, TDMA, OFDM). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-Technology IRFs" on page 1156. Interference from external mobiles (also called uplink-to-downlink interference) may be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your 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 into account in all downlink interference-based calculations. For more information on the Intertechnology DL Noise Rise, see "Cell Description" on page 972.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1155

Atoll User Manual

Figure 10.629: Interference received by mobiles on the downlink 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-uplink interference) may 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-uplink interference) may be created by the use of same or nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possible to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the Inter-technology UL Noise Rise definable for each cell in the WiMAX network. This noise rise is taken into account in uplink interference-based calculations in the simulation. It is not considered in predictions. For more information on the Inter-technology UL Noise Rise, see "Cell Description" on page 972.

Figure 10.630: Interference received by cells on the uplink

10.7.12.1

Defining Inter-Technology IRFs

Interference received from external base stations on mobiles of your WiMAX 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 An IRF depends on: The interfering technology (TDMA, CDMA, and OFDM) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).

IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your WiMAX document, i.e., when Atoll is in co-planning mode. For more information on how to switch to co-planning mode, see "Switching to Co-planning Mode" on page 1123. To define the inter-technology IRFs in the victim network: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Inter-technology IRFs from the context menu. The Inter-technology Interference Reduction Factors table appears. 4. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: Technology: Select the technology used by the interfering network.

1156

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks Interferer Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfering network. This channel width must be consistent with that used in the linked document. Victim Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfered network. This channel width must be consistent with that used in the main document. Reduction Factors (dB): Click the cell corresponding to the Reduction Factors (dB) column and the current row in the table. The Reduction Factors (dB) dialogue appears. Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document.

Notes: Reduction values must be positive. Undefined reduction factors are assumed to be very high values. Click OK. The interference reduction factors are stored.

You can, if you wish, link more than one Atoll document with your main document following the procedure described in "Switching to Co-planning Mode" on page 1123. If the linked documents model networks using different technologies, you can define the interference reduction factors in your main document for all these technologies, and Atollwill calculate interference from all the external base stations in all the linked documents.

10.8

Tips and Tricks

The following tips and tricks are described below: "Obtaining User Throughputs for All the Subscribers of a Subscriber List" on page 1157. "Working With User Densities Instead of User Profiles" on page 1158. "Restricting Coverage Predictions to LOS Areas Only" on page 1158. "Limiting the Coverage Range of Transmitters in Order to Avoid Uplink-to-Downlink Interference in TDD Networks" on page 1158. "Bearer Selection Thresholds" on page 1158. "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1159. "Relation Between Bearer Efficiency And Spectral Efficiency" on page 1160. "Determining Approximate Required DL:UL Ratio for a TDD Network" on page 1160. "Working With Frame Configurations, Permutation Zones, and Segmentation: Examples" on page 1160. "Modelling VoIP Codecs" on page 1164. "Modelling Different Types of AMC Subchannels" on page 1165. "Modelling the Co-existence of Networks" on page 1166.

Obtaining User Throughputs for All the Subscribers of a Subscriber List

Important: This procedure is only recommended if you have a correct subscriber list and have complete knowledge of the services they use. Atoll generates a realistic user distribution containing active users only during Monte Carlo simulations. The status of these users is determined through the users service usage parameters defined in the user profile. In Atoll, all the subscribers have a user profile assigned to them. During Monte Carlo simulations based on subscriber lists, Atoll determines active users from all the users in the subscriber list. If you perform calculations on subscriber lists, Atoll calculates the channel throughputs and not the user throughputs as resource allocation is not performed in these calculations. However in the simulations, RRM and resource allocation is carried out user throughputs can be determined. If you want to determine user level throughputs for all the subscribers in a subscriber list, you can run a simulation on this subscriber list after modifying the user profiles assigned to all the subscribers such that all the subscribers have an activity probability of 100 %. 1. Create a subscriber list with subscribers having an activity probability of 100%: a. Create as many user profiles as there are services used by the subscribers in the list. b. Assign only one service to each user profile. c. Assign the following service usage parameters to the user profiles that you create: i. For Voice services, set: Calls/Hour = 1. Duration (sec.) = 3600.

ii. For Data services: Calls/Hour = 1. UL Volume (KBytes) = UL Average Throughput x 3600/8. DL Volume (KBytes) = DL Average Throughput x 3600/8. Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average requested throughputs, respectively, of the service mentioned in the user profile.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1157

Atoll User Manual d. Assign these user profiles to subscribers in the subscriber list. 2. Create a simulation based on this subscriber list only. The simulation results will contain all the subscribers in the subscriber list with their respective user throughputs determined by Atoll after the scheduling process.

Working With User Densities Instead of User Profiles

If you do not currently have reliable LTE multi-service traffic, you can provide Atoll with user density information per service, for example, traffic data from adapted GSM Erlang maps. In this case, you do not have to create user profiles. As well, Atoll does not have to determine the user activity probabilities to create traffic scenarios during simulations. The distribution of traffic during simulations will only depend on the user densities per service. If you know the user densities for each service, you can set user activity probabilities to 100 % in your LTE document, as shown below: 1. For Voice services, set: Calls/Hour = 1. Duration (sec.) = 3600.

2. For Data services: Calls/Hour = 1. UL Volume (KBytes) = UL Average Throughput x 3600/8. DL Volume (KBytes) = DL Average Throughput x 3600/8. Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average requested throughputs, respectively, of the service defined in the user profile. 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 the exact number of active users and their services generated during the simulations beforehand. This procedure should only be used when appropriate traffic data is not available.

Restricting Coverage Predictions to LOS Areas Only

In WiMAX, and especially in IEEE 802.16d networks, it might be interesting to study the areas with LOS coverage only and other areas separately. You can restrict the coverage to LOS areas only if you are using the Standard Propagation Model. To restrict coverage to LOS areas, you have to enter a very high value for the parameter K4 in the properties of the Standard Propagation Model.

Limiting the Coverage Range of Transmitters in Order to Avoid Uplink-to-Downlink Interference in TDD Networks
You can define a maximum coverage range for all the transmitters in your network by entering a valid range as the Max Range parameter. To define the Max Range parameter: 1. Right-click the Predictions folder. The context menu appears. 2. Select Properties from the context menu. The Predictions folders properties dialogue appears. 3. Select the System tab. 4. Select the Max Range check box. The Max Range field in enabled. 5. Enter the Max Range of the network. 6. Click OK. In TDD networks, the TTG and RTG parameters, available in the Global Parameters tab of the Transmitters folders properties dialogue, 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 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 Where TTG and RTG are values in milliseconds, Max Range is in meters, and the Min() function returns the lower of the two values given to it in the parentheses. So, the maximum system range for TTG = 0.105 ms and RTG = 0.06 ms will be 9 km.

Bearer Selection Thresholds

The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll have been extracted and estimated from the NS2 simulator results available with the WiMAX Forum (see Figure 10.631 and Figure 10.632). These values correspond to to an ideal (AWGN) radio channel, and are too optimistic compared to real radio channels. It is recommended to use more realistic values when available.

1158

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.631: Link Adaptation in WiMAX 802.16d

Figure 10.632: Link Adaptation in WiMAX 802.16e The spectral efficiency is the number of useful data bits that can be transmitted using any modulation and coding scheme per Hz, the transition points between any two modulation and coding schemes give the default bearer selection thresholds in Atoll, and the normalised values from the slopes of the graphs, that represent the reduction in the spectral efficiency, give the block error rate.

Calculating Bearer Selection Thresholds From Receiver Sensitivity Values

You can convert the receiver sensitivity values, that are listed in the specifications of your equipment, into bearer selection thresholds using the following conversion method: n BW N Used CNR = RS + 114 NF 10 Log ----------------------------------------- + 10 Log ( R ) L Imp 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. In the above explanation, the term receiver refers to the base station in uplink and to the mobile/user equipment in the downlink.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1159

Atoll User Manual

Relation Between Bearer Efficiency And Spectral Efficiency

Spectral efficiency of a modulation and coding scheme is defined as the number of useful bits that can be transmitted each second over a channel of 1 Hz bandwidth. Spectral efficiency is hence given in terms of bps/Hz. In Atoll, the efficiency of bearers (modulation and coding schemes) are defined in the Bearers table. The bearer efficiency is given in terms of bits/symbol. Remember that in Atoll a symbol refers to the data transmission unit which is 1 symbol duration long and 1 subcarrier width wide, as shown in Figure 10.633.

Figure 10.633: Symbol The concept of bearer efficiency is similar to spectral efficiency. The only difference is in the units used to define the two entities. Here is a simple example that compares spectral efficiency and bearer efficiency, and shows that the two are the same. Spectral efficiency is given by: SE = ( 1 BLER ) r Log 2 ( M ) 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 1 802.16e is F = 10.94 kHz , from which we can calculate the useful symbol duration as well: T U = ------- = 91.4 sec . F In one second, there can be 1 sec 91.4 sec = 10940 symbol durations. If 10940 symbols are transmitted using QPSK1/2, this gives us a data rate of 10940 Symbols/sec 1 bits/Symbol = 10940 bps , which is the data rate achievable using one subcarrier of 10.94 kHz. We can find the spectral efficiency by normalizing the data rate 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.

Determining Approximate Required DL:UL Ratio for a TDD Network

In TDD networks, the durations of the downlink and uplink subframes have to be properly set in order to optimally satisfy the traffic demands in both downlink and uplink. You can use the simulation results to calculate the approximate value of the DL:UL Ratio required for your network under the given traffic scenario of the simulation. The DL:UL Ratio can be calculated by taking the ratio of the sum of the downlink traffic loads of all the cells and the sums of all the downlink and uplink traffic loads of all the cells. The downlink and uplink traffic loads of all the cells are listed in the Cells tab of the simulations results dialogue.

DL:UL Ratio = -----------------------------------------------------------------DL UL TL + TL

All Cells

TL All Cells

DL

All Cells

You can then set this value of DL:UL Ratio in the Global Parameters tab of the Transmitters folders properties dialogue, for optimising your networks resource usage.

Working With Frame Configurations, Permutation Zones, and Segmentation: Examples

In the following examples, we assume that: You are working on a document with existing base stations. One 5 MHz channel, with channel number 0, defined in the frequency band, that can be allocated to sectors. The frame configuration that can be used is FFT Size 512 with 512 total subcarriers.

There can be different scenarios for this implementation: 1. Without segmentation, i.e., a frequency reuse plan of N=1. a. Set up the frame configuration: i. Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 1143.

ii. Verify that the Segmentation Support check box is not selected for FFT Size 512.

1160

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears. iv. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL). v. Click OK. vi. Close the Frame Configurations tables. b. Set up the cells: i. Right-click the Transmitters folder. The context menu appears.

ii. Select Cells > Open Table from the context menu. The Cells table appears. iii. In the Cells table, enter: Channel Number: 0 Frame Configuration: FFT Size 512

iv. Close the Cells table. c. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as explained in "Making a Coverage Prediction by C/(I+N) Level" on page 1012 and "Making a Coverage by Throughput" on page 1016, respectively. In this case, the same 5 MHz channel is allocated to the three sectors of each 3-sector site. The sectors receive co-channel interference according to the downlink traffic loads of the interferers. The traffic C/(I+N) and throughput coverage predictions would be as shown in Figure 10.634 and Figure 10.635.

Figure 10.634: Downlink Traffic C/(I+N) Coverage Prediction - PUSC Without Segmentation

Figure 10.635: Downlink Channel Throughput Coverage Prediction - PUSC Without Segmentation

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1161

Atoll User Manual 2. With a segmented PUSC permutation zone, i.e., 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 1143.

ii. Select the Segmentation Support 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) and 8 (PUSC UL). v. Click OK. vi. Close the Frame Configurations tables. b. Set up the cells: i. Right-click the Transmitters folder. The context menu appears.

ii. Select Cells > Open Table from the context menu. The Cells table appears. iii. In the Cells table, enter: 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%

iv. Close the Cells table. c. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as explained in "Making a Coverage Prediction by C/(I+N) Level" on page 1012 and "Making a Coverage by Throughput" on page 1016, 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. The traffic C/(I+N) and throughput coverage predictions would be as shown in Figure 10.636 and Figure 10.637.

Figure 10.636: Downlink Traffic C/(I+N) Coverage Prediction - PUSC With Segmentation

1162

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks

Figure 10.637: Downlink Channel Throughput Coverage Prediction - PUSC With Segmentation 3. With a segmented PUSC permutation zone and one or more non-segmented zones, i.e., 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 1143.

ii. Select the Segmentation Support 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. The context menu appears.

ii. Select Cells > Open Table from the context menu. The Cells table appears. iii. In the Cells table, enter the following values: 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.

iv. Close the Cells table. c. Allocate different segmentation usage ratios to the cells: Enter different segmentation usage ratios manually in the Cells table, or calculate the segmentation usage ratios for all the cells using a Monte Carlo simulation as follows: Create or import a traffic map, as explained in "Creating a Traffic Map" on page 1042, to be used as input to the Monte Carlo simulator. Create a new Monte Carlo simulation as explained in "Creating Simulations" on page 1056. Open the simulation results, and commit the results to the Cells table as explained in "Updating Cell Load Values With Simulation Results" on page 1067. d. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as explained in "Making a Coverage Prediction by C/(I+N) Level" on page 1012 and "Making a Coverage by Throughput" on page 1016, 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 10.638 and Figure 10.639.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1163

Atoll User Manual

Figure 10.638: Downlink Traffic C/(I+N) Coverage Prediction - Segmented PUSC + FUSC

Figure 10.639: 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.

Modelling VoIP Codecs

VoIP codecs are application-layer elements in the OSI system model. Atoll models application throughputs using a throughput offset and a scaling factor with respect to the MAC layer throughputs. You can model different VoIP codecs by creating a new service for each VoIP codec, and setting the target throughput to the Application Throughput for the scheduler used. Here are two examples of the most common VoIP codecs, and how they can be modelled in Atoll: G.711 VoIP Codec The actual voice data rate needed by the G.711 codec is 64 kbps, but with the lower layer headers and other added bits, the needed MAC data rate could be between 66.4 and 107.2 kbps. In this example, we show how to model the codec with header bits that lead to 85.6 kbps MAC data rate. a. Create a new service with the following parameters: Name: VoIP (G.711) Type: Voice QoS Class: UGS Min Throughput Demand (DL) and Min Throughput Demand (UL): 64 kbps Average Requested Throughput (DL) and Average Requested Throughput (UL): 64 kbps Scaling Factor: 74.77 % Offset: 0 kbps

1164

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 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 MAC throughput. G.729 VoIP Codec The actual voice data rate needed by the G.729 codec is 8 kbps, but with the lower layer headers and other added bits, the needed MAC data rate could be between 9.6 and 29.6 kbps. In this example, we show how to model the codec with header bits that lead to 29.6 kbps required data rate. a. Create a new service with the following parameters: Name: VoIP (G.729) Type: Voice QoS Class: UGS Min Throughput Demand (DL) and Min Throughput Demand (UL): 8 kbps Average Requested Throughput (DL) and Average Requested Throughput (UL): 8 kbps Scaling Factor: 27.03 % Offset: 0 kbps

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.

Modelling Different Types of AMC Subchannels

AMC subchannels are composed of bins, i.e., groups of 9 adjacent subcarriers. The following four types of AMC subchannels exist:

Type
1 2 3 4

Name
6x1 (Default) 3x2 2x3 1x6

Number of Bins in 1 Subchannel

6 3 2 1

Number of Subcarriers in 1 Subchannel

6 x 9 = 54 3 x 9 = 27 2 x 9 = 18 1x9=9

Length (Number of Symbol Durations)

1 2 3 6

Total Number of Modulation Symbols in One Slot

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.

Figure 10.640: AMC Subchannel Types 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1165

Atoll User Manual 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.

Modelling the Co-existence of Networks

In Atoll, you can study the effect of interference received by your network from other WiMAX networks. The interfering WiMAX network can be a different part of your own network, or a network belonging to another operator. To study interference from co-existing networks: 1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a Group of Base Stations" on page 982. 2. For the interfering networks transmitters, set the Transmitter Type to Extra-Network (Interferer Only) as explained in "Transmitter Description" on page 970. During calculations, Atoll will consider the transmitters of type Extra-Network (Interferer Only) when calculating interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interference. Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network. If the interfering network is a part of your own network, this information would be readily available. However, if the interfering network belongs to another operator, the information available might not be accurate. Moreover, for other operators networks, and if the interfering networks use OFDM but are not WiMAX networks,, you will have to create specific frame configurations to assign to the cells of the interfering network. The number of subcarriers used in these frame configurations would depend on the channel bandwidth on which transmitter is interfering. For more information on frame configuration parameters, see "Defining Frame Configurations" on page 1143.

10.9

Glossary of WiMAX Terms

Understanding the following terms and there use in Atoll is very helpful in understanding the WiMAX module: User: A general term that can also designate a subscriber, mobile, and receiver. Subscriber: Users with fixed geographical coordinates. 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. 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 data rate 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. 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 UL instead of the uplink noise rise is the uplink load factor: L UL = ------------------------ . Usually, the uplink load factor is kept I UL + N UL as a linear value (in %) 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 I+N 1 N I ----------- = --------------------- => ----------- = ----------- ----------- => ----------- = 1 ----------- => ----------- = 1 ----------- => ----------- = --------------------I+N I+N I+N I+N I+N I+N I+N N I I+N I+N 1 ----------I+N

1166

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 10: WiMAX BWA Networks 1 => NR = ----------1L The following table shows the relation between interference, load factor, and noise rise.

Interference (I)
0 =N =9xN = 99 x N

Load Factor (%)

0 50 90 99

Noise Rise
1 2 10 100

Noise Rise (dB)

0 3.01 10 20

The reason why uplink interference is expressed in terms of noise rise (in dB) in Atoll instead of load factor (in %) is that the load factor varies somewhat exponentially with the increase in interference. Symbol: A symbol is the smallest resource unit that can be allocated to a user in WiMAX networks. 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): The entire channel contains a number of subcarriers which compose 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 time-domain composition of the frame is simpler in WiMAX 802.16d than in 802.16e. In WiMAX 802.16d networks, the frame configuration does not depend on the channel width and can be defined in the Global Parameters tab of the Transmitters folders properties dialogue as explained in "The Options on the Global Parameters Tab" on page 1140. In WiMAX 802.16e, 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 1143. 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 in downlink 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 setting the preamble index parameter correctly. 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 "Tips and Tricks" on page 1157. Primary and Secondary Subchannel Groups: The primary subchannel groups (0, 2, and 4) and secondary subchannel groups (1, 3, and 5) are mapped to subchannel numbers as follows:

Total Number of Subcarriers

Subchannel Group
0 1 2

Subchannel Range
0 N/A 1

Total Number of Subcarriers

Subchannel Group
0 1 2

Subchannel Range
0-5 6-9 10-15 16-19 20-25 26-29

128 3 4 5 N/A 2 N/A

1024 3 4 5

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1167

Atoll User Manual

Total Number of Subcarriers

Subchannel Group
0 1 2

Subchannel Range
0-4 N/A 5-9

Total Number of Subcarriers

Subchannel Group
0 1 2

Subchannel Range
0-11 12-19 20-31 32-39 40-51 52-59

512 3 4 5 N/A 10-14 N/A

2048 3 4 5

Resources: In Atoll, the term "resource" is used to refer to the average number of slots, expressed in % (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.

1168

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11
LTE Networks

RF Planning & Optimisation Software

Atoll

Chapter 11: LTE Networks

11

LTE Networks
LTE (Long Term Evolution) refers to the set of 3GPP (3rd Generation Partnership Project) Release 8 and Release 9 specifications which 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 the eUTRA (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. Atoll enables you to design LTE broadband wireless access networks. Atoll can be used to predict radio coverage, manage mobile and fixed subscriber data, and evaluate network capacity. Atoll LTE also supports MIMO. Atoll enables you to 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 or subscriber data. Atoll uses these user distributions as input for the simulations. You can create coverage predictions to study the following parameters: The reference signal level received from cells The effective reference signal level The effective SS, PBCH, PDSCH, PDCCH, and PUSCH and PUCCH signal levels The carrier-to-interference-and-noise ratio for the reference signals, SS, PBCH, PDSCH, PDCCH, and PUSCH The radio bearer coverage The channel throughput and cell capacity per pixel, and the aggregate throughput per cell.

Coverage predictions that depend on the networks 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 EGPRS, CDMA2000 1xRTT, CDMA2000 1xEV-DO, UMTS HSPA, and LTE networks can be planned in the same Atoll session.

Tip:

Before working with the Atoll LTE module for the first time, it is highly recommended to go through the "Glossary of LTE Terms" on page 1357. This will help you get accustomed to the terminology used by the 3GPP and in Atoll.

11.1

Designing an LTE Network

Figure 11.641 depicts the process of creating and planning an LTE network. The steps involved in planning an LTE network are described below. The numbers refer to Figure 11.641. 1. Open an existing radio-planning document or create a new one ( 1 ). You can open an existing Atoll document by selecting File > Open. You can create a new Atoll document as explained in Chapter 2: Starting an Atoll Project.

2. Configure the network by adding network elements and changing parameters ( 2 ). You can add and modify the following elements of base stations: "Creating or Modifying a Site" on page 1178. "Creating or Modifying a Transmitter" on page 1179. "Creating or Modifying a Cell" on page 1179.

You can also add base stations using a base station template (see "Placing a New Base Station Using a Station Template" on page 1180). 3. Carry out basic coverage predictions ( 3 ). "Making a Point Analysis to Study the Profile" on page 1187. "Studying Signal Level Coverage" on page 1189 and "Signal Level Coverage Predictions" on page 1196.

4. Allocate neighbours ( 4 ). "Planning Neighbours" on page 1225.

5. Allocate frequencies ( 5 ). "Planning Frequencies" on page 1235.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1171

Atoll User Manual 6. Allocate physical cell IDs ( 6 ). "Planning Physical Cell IDs" on page 1239.

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 and subscriber lists ( 7a , 7b , and 7c ) (see "Studying Network Capacity" on page 1243). You can define cell load conditions manually either on the Cells tab of each transmitters Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 1179) ( 7d ). 8. Make LTE-specific signal quality coverage predictions using the defined cell load conditions ( 8 ). "LTE Coverage Predictions" on page 1209.

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

7c 7b

7d

10

Figure 11.641: Planning an LTE network - workflow

11.2

Planning and Optimising LTE Base Stations

As described in Chapter 2: Starting an Atoll Project, you can start an Atoll document from a template, with no base stations, or from a database with a set of base stations. As you work on your Atoll document, you will still need to create base stations and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such as the TMA, feeder cables, etc. In 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.

1172

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks In Atoll, you can study a single base station or a group of base stations 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 allowing you to create services, users, user profiles, environments, and terminals. This data can be then used to make studies that depend on network load, such as C/(I+N), LTE radio bearer, and throughput coverage predictions. In this section, the following are explained: "Creating an LTE Base Station" on page 1173. "Creating a Group of Base Stations" on page 1185. "Modifying Sites and Transmitters Directly on the Map" on page 1186. "Display Tips for Base Stations" on page 1186. "Creating a Multi-Band LTE Network" on page 1186. "Setting the Working Area of an Atoll Document" on page 1187. "Studying a Single Base Station" on page 1187. "Studying Base Stations" on page 1190. "Planning Neighbours" on page 1225. "Planning Frequencies" on page 1235. "Planning Physical Cell IDs" on page 1239.

11.2.1

Creating an LTE Base Station

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

11.2.1.1

Definition of a Base Station

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

11.2.1.1.1

Site Description
The parameters of a site can be found in the sites Properties dialogue. The Properties dialogue has two tabs: The General tab (see Figure 11.642): 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.

Tip:

While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.

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 wish. If an altitude is specified here, Atoll will use this value for calculations. Comments: You can enter comments in this field if you want.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1173

Atoll User Manual

Figure 11.642: New Site dialogue

11.2.1.1.2

Transmitter Description
The parameters of a transmitter can be found in the transmitters Properties dialogue. When you create a transmitter, the Properties dialogue has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Properties dialogue has three additional tabs: the Cells tab (see "Cell Description" on page 1176), the Propagation tab (see Chapter 5: Managing Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 32). The General tab: Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names transmitters, see the Administrator Manual. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site on which the transmitter will be located. For information on the site Properties dialogue, see "Site Description" on page 1173. You can click the New button to create a new site on which the transmitter will be located. Under Antenna Position, you can modify the position of the antennas (main and secondary): Relative to Site: Select Relative to Site if you want 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 Coordinates if you want to enter the coordinates of the antenna positions, and enter the x-axis and y-axis coordinates, X and Y, respectively.

The Transmitter tab (see Figure 11.643):

Figure 11.643: Transmitter dialogue - Transmitter tab

1174

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 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 Data tab. Note: 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 transmitter type to Extra-Network (Interferer Only). No coverage for an Interferer Only transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simulations. This feature 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 1357.

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 using the Equipment Specifications dialogue which appears when you click the Equipment button. In the Equipment Specifications dialogue (see Figure 11.644), the equipment you select and the gains and losses you define are used to initialise total transmitter losses in the uplink and downlink: 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 147. 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 147. BTS: You can select base transceiver station (BTS) equipment from the BTS list. You can click the Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defining BTS Equipment" on page 148. Feeder Length: You can enter the feeder length at transmission and reception. Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value you enter must be positive.

Figure 11.644: The Equipment Specifications dialogue Atoll always considers the values in the Real fields in coverage predictions even if they are different from the values in the Computed boxes. The information in the real BTS Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total Losses at transmission and reception and the real BTS 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. The other fields, Azimuth, Mechanical Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1175

Atoll User Manual 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 1349. 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. For information on working with data tables, see "Working with Data Tables" on page 53.

11.2.1.1.3

Cell Description
In Atoll, a cell is defined as an RF channel, with all its characteristics, on a transmitter; the cell is the mechanism by which you can configure a multi-carrier LTE network. When you create a transmitter, Atoll reminds you to create a cell for the transmitter. The parameters of an LTE cell are explained below. While you create a cell, Atoll calculates appropriate values for some fields based on the information you have entered. You can, if you want, modify these values. The properties of an LTE cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned. The Cells tab has the following options: 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 change the 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. Layer: The number of the coverage layer to which the cell belongs. This value is automatically assigned when you create a new cell, but you can modify it afterwards. The layer is used during calculations to select the serving cell. For more information on the cell layer selection options, see "The Global Transmitter Parameters" on page 1342. Frequency Band: The cells frequency band from the Frequency Band list. Channel Number: The number of the channel from the list of available channels. Channel Allocation Status: The status of the current channel allocated to the cell: - Not Allocated: The current channel has neither been allocated automatically nor manually. The AFP considers that a Not Allocated channel is modifiable. - Allocated: The current channel has been allocated automatically or manually. The AFP considers that an Allocated physical cell ID is modifiable but it is not modified unless absolutely necessary. - Locked: The current channel has been allocated automatically or manually. The AFP considers that a Locked channel is not modifiable. 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. PSS ID: The PSS ID corresponding to the current physical cell ID. This value is determined automatically from the physical cell ID. SSS ID: The SSS ID corresponding to the current physical cell ID.This value is determined automatically from the physical cell ID. Physical Cell ID Status: The status of the physical cell ID currently assigned to the cell: - Not Allocated: The current physical cell ID has neither been allocated automatically nor manually. The automatic physical cell ID allocation algorithm considers that a Not Allocated physical cell ID is modifiable. - Allocated: The current physical cell ID has been allocated automatically or manually. The automatic physical cell ID allocation algorithm considers that an Allocated physical cell ID is modifiable but it is not modified by the algorithm unless absolutely necessary. - Locked: The current physical cell ID has been allocated automatically or manually. The automatic physical cell ID allocation algorithm considers that a Locked physical cell ID is not modifiable. Min Reuse Distance: The minimum reuse distance after which the channel assigned to this cell can be assigned to another cell by the AFP. The reuse distance is also used by automatic physical cell ID allocation. The cells physical cell ID can be allocated to another cell outside this reuse distance without any cost. Max Power (dBm): The cells maximum transmission power. If the Reference Signal EPRE is set to Calculated from Max Power and EPRE Offsets in the Global Parameters, the transmission powers corresponding to different channels are calculated using this value plus 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. If the Reference Signal EPRE is set to User-defined, this field is not used, and you can directly enter the RS EPRE in the corresponding field. RS EPRE (dBm): The reference signal EPRE. If the Reference Signal EPRE is set to Calculated from Max Power and EPRE Offsets in the Global Parameters, this value is calculated by Atoll. If the Reference Signal EPRE is set to User-defined, you can enter the RS EPRE. 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. 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.

1176

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 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 have to 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 Reference Signal 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. 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. LTE Equipment: You can select the cells LTE equipment from the LTE Equipment list. For more information, see "Defining LTE Equipment" on page 1345. 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 1347. 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 Frame Configuration: The frame configuration used by the cell when the cells frequency band is TDD. If the networks switching point periodicity is set to "Half Frame", you can select a frame configuration of type DSUUU-DSUUU, DSUUD-DSUUD, DSUDD-DSUDD, or DSUUU-DSUUD. If the networks switching point periodicity is set to "Frame", you can select a frame configuration of type DSUUU-DDDDD, DSUUD-DDDDD, or DSUDD-DDDDD. For more information on TDD switching point periodicity, see "The Global Transmitter Parameters" on page 1342. Diversity Support (DL): The type of antenna diversity technique (None, Transmit Diversity, SU-MIMO, or AMS) supported by the cell in downlink. Diversity Support (UL): The type of antenna diversity technique (None, Receive Diversity, SU-MIMO, AMS, or MU-MIMO) supported by the cell in uplink. Specific calculations will be performed (gains will be applied) for terminals supporting MIMO. AMS & MU-MIMO Threshold (dB): For AMS, it is the reference signal C/N required for switching from Transmit Diversity to SU-MIMO. For MU-MIMO, it is the minimum required reference signal CNR for using MU-MIMO. For more information on Adaptive MIMO switching, see "Multiple Input Multiple Output Systems" on page 1349. 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. 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 fractional 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 nomincal 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. Interference Coordination Support: The type of inter-cell interference coordination (ICIC) technique supported by the cell. You can select Static DL or Static UL. With ICIC, a cell uses a third of the channel bandwidth in its ICIC part of the frame. Which third of the channel bandwidth is used by the cell depends on its PSS ID. Therefore, fractional frequency planning can be performed by carrying out automatic physical cell ID planning. For more information, see "Planning Physical Cell IDs" on page 1239. ICIC Delta Path Loss Threshold (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. Cell edge mobiles are served by the ICIC part of the LTE frame, i.e., the part of the frame that uses a fraction of the channel bandwidth.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1177

Atoll User Manual Traffic Load (DL) (%): The downlink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations. 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. ICIC Ratio (DL) (%): You can set the percentage of the total downlink traffic load that corresponds to the ICIC part of the frame. For example, if the downlink traffic load is 80%, and you set the ICIC ratio to 50%, it means that 40% of the downlink traffic load is on the ICIC part of the frame while the other 40% is on the non-ICIC part. 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. 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. 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 part of the LTE frame that uses a fraction of the channel bandwidth. This noise rise is only used when the ICIC support for the cell includes static UL. This can be userdefined or an output of Monte Carlo simulations. Max UL Noise Rise (dB) (not yet implemented): The upper limit on both uplink noise rise values, i.e., the UL noise rise and the ICIC UL noise rise. This is an input for Monte Carlo simulations. This parameter represents the maximum interference that a cell can tolerate on the uplink. If the difference between this maximum value and the actual noise rise is large, the neighbouring cells might still serve mobiles on the uplink. As this difference becomes small, the neighbouring cells are informed to ask the mobiles they serve on the uplink to reduce their transmission powers. This might lead to a reduction in the number of mobiles served in the uplink in the neighbouring cells. Inter-technology 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 the simulation. 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 1351. Inter-technology DL Noise Rise: This noise rise represents the interference created by mobiles of an external network on the mobiles served by this cell on the downlink. This noise rise will be taken into account in all downlink interference-based calculations involving this cell. For more information on inter-technology interference, see "Modelling Inter-Technology Interference" on page 1351. Max Number of Intra-technology Neighbours: The maximum number of neighbours that the cell can have from the same Atoll document. Max Number of Inter-technology Neighbours: The maximum number of neighbours that the cell can have from other technology documents. Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neighbours by clicking the Browse button ( on page 1225. ). For information on defining neighbours, see "Planning Neighbours"

Tip:

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.

11.2.1.2

Creating or Modifying a Base Station Element

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: "Creating or Modifying a Site" on page 1178 "Creating or Modifying a Transmitter" on page 1179 "Creating or Modifying a Cell" on page 1179

11.2.1.2.1

Creating or Modifying a Site

You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 1173, through the sites Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create or modify a site: If you are creating a new site: a. Click the Data tab in the Explorer window. b. Right-click the Sites folder. The context menu appears. c. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 11.642 on page 1174). If you are modifying the properties of an existing site: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Sites folder.

c. Right-click the site you want to modify. The context menu appears.

1178

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks d. Select Properties from the context menu. The sites Properties dialogue appears. 1. Modify the parameters described in "Site Description" on page 1173. 2. Click OK.

11.2.1.2.2

Creating or Modifying a Transmitter

You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 1174, through the transmitters Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create or modify a transmitter: If you are creating a new transmitter: a. Click the Data tab in the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 11.643). If you are modifying the properties of an existing transmitter: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the Transmitters folder.

c. Right-click the transmitter you want to modify. The context menu appears. d. Select Properties from the context menu. The transmitters Properties dialogue appears. 1. Modify the parameters described in "Transmitter Description" on page 1174. 2. 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 1179.

Tips: 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 right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 59. 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.

11.2.1.2.3

Creating or Modifying a Cell

You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Description" on page 1176, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitters Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Description" on page 1176. 7. Click OK.

Tips: If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 59), or import data into the table (see "Importing Tables from Text Files" on page 63). If you want to add a cell to an existing transmitter on the map, you can add the cell by rightclicking the transmitter and selecting New Cell from the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1179

Atoll User Manual

11.2.1.3

Placing a New Base Station Using a Station Template

In Atoll, a base station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing base stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio toolbar, select a template from the list.

2. Click the New Transmitter or Station button (

) in the Radio toolbar.

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.

Tips:

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 38. 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.

You can also place a series of base stations using a station template. You do this by defining an area on the map where you want to place the base stations. Atoll calculates the placement of each base station according to the defined hexagonal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 1181. To place a series of base stations within a defined area: 1. In the Radio toolbar, select a template from the list (see Figure 11.645). 2. Click the Hexagonal Design button ( ) to the left of the station template list. A hexagonal design is a group of base stations created from the same station template.

Note:

If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this template is not defined. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 1181.

3. Draw a zone delimiting the area where you want to place the series of base stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as sites and transmitters are also created and placed into their respective folders. You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for example, another antenna to a transmitter.

Placing a Station on an Existing Site

When you place a new station using a station template as explained in "Placing a New Base Station Using a Station Template" on page 1180, the site is created at the same time as the station. However, you can also place a new station on an existing site.

1180

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks To place a base station on an existing site: 1. On the Data tab, clear the display check box beside the Hexagonal Design folder. 2. In the Radio toolbar, select a template from the list. 3. Click the New Transmitter or Station button ( ) in the Radio toolbar.

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.

11.2.1.4

Managing Station Templates

Atoll comes with LTE station templates, but you can also create and modify station templates. The tools for working with station templates are on the Radio toolbar (see Figure 11.645).

Figure 11.645: The Radio toolbar In this section, the following are explained: "Creating or Modifying a Station Template" on page 1181 "Copying Data from One Station Template to Another" on page 1184 "Modifying a Field in a Station Template" on page 1184 "Deleting a Station Template" on page 1184.

11.2.1.4.1

Creating or Modifying a Station Template

When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. As well, you can modify the properties of any existing station template. To create or modify a station template: 1. In the Radio toolbar, click the arrow to the right of the station template list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. You can now create a new station template or modify an existing one: To create a new station template: Under Station Templates, select the station template that most closely resembles the station template you want to create and click Add. The Properties dialogue appears. To modify an existing station template: Under Station Templates, select the station template whose properties you want to modify and click Properties. The Properties dialogue appears.

4. Click the General tab of the Properties dialogue. In this tab (see Figure 11.646), you can modify the following: 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: 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. Under Number of Antenna Ports, you can enter the number of antennas used for Transmission and for Reception for MIMO. Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1181

Atoll User Manual

Figure 11.646: Station Template Properties dialogue General tab 5. Click the Transmitter tab. In this tab (see Figure 11.647), if the Active check box is selected, you can modify the following: Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station (BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 1174. The information in the computed Total Losses in transmission and reception boxes is calculated from the information you entered in the Equipment Specifications dialogue (see Figure 11.644 on page 1175). 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 modify the real Total Losses at transmission and reception if you wish. Any value you enter must be positive. The information in the computed BTS Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if you wish. Any value you enter must be positive.

Figure 11.647: Station Template Properties dialogue Transmitter tab 6. Click the LTE tab. On this tab (see Figure 11.648), you can modify the following: Under Power and EPRE Offsets Relative to the Reference Signals EPRE, you can modify the Max Power or RS EPRE, and the EPRE offsets for the SS, PBCH, PDSCH, and PDCCH in SS Offset, PBCH Offset, PDCCH Offset, and PDSCH Offset. You can assign channel and physical cell ID per cell per sector, by clicking the Cell Definition per Sector button. The Cell Definition per Sector dialogue appears. i. Click the Cell Definition per Sector button. The Cell Definition per Sector dialogue appears.

1182

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks ii. Select the Sector for which you want to define cell parameters, i.e., channel number and physical cell ID. iii. Enter the Number of Cell Layers that the selected sector will have. The number of rows in the grid below depends on the number of cell layers that you enter. iv. In the Cell Layer - Channel/Physical Cell ID grid, assign a channel number and a physical cell ID to each cell. v. Carry out the steps above to assign a channel and physical cell ID to each sector. vi. Click OK. Frequency Band, Channel Allocation Status, Physical Cell ID Status, Min Reuse Distance, LTE Equipment, Scheduler, Max Number of Users, TDD Frame Configuration, and Min RSRP. Under Antenna Diversity, you can select the Diversity Support in downlink and in uplink, enter the AMS & MU-MIMO Threshold, and define the default MU-MIMO Capacity Gain. Under Default Loads, you can 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. Under Inter-technology Interference, you can set the DL Noise Rise and the UL Noise Rise. For more information on inter-technology interference, see "Modelling Inter-Technology Interference" on page 1351.

Figure 11.648: Station Template Properties dialogue LTE tab 7. Click the Neighbours tab. In this tab (see Figure 11.649), you can modify the following: Under Max Number of Neighbours, you can set the maximum numbers of Intra-technology and Inter-technology neighbours.

Figure 11.649: Station Template Properties dialogue Neighbours tab 8. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Sites table, or if you have defined an additional field in the Station Template Properties dialogue. 9. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1183

Atoll User Manual

11.2.1.4.2

Copying Data from One Station Template to Another

You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Station Templates from the context menu. The Station Templates table appears. 4. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy from and paste them into the row corresponding to the station template you want to modify.

11.2.1.4.3

Modifying a Field in a Station Template

To modify a field in a station template: 1. In the Radio toolbar, click the arrow to the right of the station template list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Select the template in the Available Templates list. 4. Click the Fields button. 5. In the dialogue that appears, you have the following options: Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Types Data Table" on page 54) for it to appear as an option in the station template properties. To add a new field: i. Click the Add button. The Field Definition dialogue appears.

ii. Enter a Name for the new field. iii. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/ Time, and Currency. If you choose "Text," you can also set the field Size (in characters), and create a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER after each one. iv. Enter, if desired, a Default value for the new field. v. Click OK to close the Field Definition dialogue and save your changes. Delete: To delete a user-defined field: i. Select the user-defined field you want to delete.

ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you close the dialogue. Properties: To modify the properties of a user-defined field: i. Select the user-defined field you want to modify.

ii. Click the Properties button. The Field Definition dialogue appears. iii. Modify any of the properties as desired. iv. Click OK to close the Field Definition dialogue and save your changes. 6. Click OK.

11.2.1.4.4

Deleting a Station Template

To delete a station template: 1. In the Radio toolbar, click the arrow to the right of the station template list. 2. Select Manage Templates from the list. The Station Template Properties dialogue appears. 3. Under Station Templates, select the station template you want to delete and click Delete. The template is deleted. 4. Click OK.

11.2.1.5

Duplicates of an Existing Base Station

You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same site, transmitter, and cell parameter values as the original one. Duplicating a base station allows you to: Quickly create a new base station with the same settings as 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 base stations that have the same characteristics.

1184

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks To duplicate an existing base station: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Sites folder.

3. Right-click the site you want to duplicate. The context menu appears. 4. From the context menu, select one of the following: Select Duplicate > With Neighbours from the context menu, if you want to duplicate the base station with the lists of intra- and inter-technology neighbours of its transmitters. 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.

You can now place the new base station on the map using the mouse. 5. In the map window, move the pointer over the map to where you would like to place the new base station. The exact coordinates of the pointers current location are visible in the Status bar.

Figure 11.650: Placing a new base station

Tips:

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 38. If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact coordinates, allowing you to verify that the location is correct.

6. Click the selected point on the map to place the duplicate base station. A new base station is placed on the map. The site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original base station, preceded by "Copy of." The site, transmitters, and cells of the duplicate base station have the same settings as those of the original base station. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate station. For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 1173.

11.2.2

Creating a Group of Base Stations

You can create base stations individually as explained in "Creating an LTE Base Station" on page 1173, or you can create one or several base stations by using station templates as explained in "Placing a New Base Station Using a Station Template" on page 1180. However, if you have a large project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations. Note: 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 96.

You can import base station data in the following ways: Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. Important: The table you copy 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 59. 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

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1185

Atoll User Manual CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files" on page 61. For information on importing table data, see "Importing Tables from Text Files" on page 63. Note: You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio toolbar. For information, see "Placing a New Base Station Using a Station Template" on page 1180.

11.2.3

Modifying Sites and Transmitters Directly on the Map

In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu on the Data tab of the Explorer window. However, in a complex radio-planning project, it can be difficult to find the data object in the Data tab, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. If there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: "Selecting One of Several Transmitters" on page 31. "Moving a Site Using the Mouse" on page 31. "Moving a Site to a Higher Location" on page 31. "Changing the Azimuth of the Antenna Using the Mouse" on page 31. "Changing the Antenna Position Relative to the Site Using the Mouse" on page 32.

11.2.4

Display Tips for Base Stations

Atoll allows to you to display information about base stations in a number of ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object types data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information in the label will make it harder to distinguish the information you are looking for. For information on defining the label, see "Defining the Object Type Label" on page 35. Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip 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 every field in that object types data table, including from fields that you add. For information on defining the tool tips, see "Defining the Object Type Tip Text" on page 36. 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 "Defining the Display Type" on page 33. 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 "Defining the Display Type" on page 33.

11.2.5

Creating a Multi-Band LTE Network

In Atoll, you can model a multi-band LTE network, for example, a network consisting of 900 MHz and 2.1 GHz, in one document. Creating a multi-band LTE network consists of the following steps: 1. Defining the frequency bands in the document (see "Defining Frequency Bands" on page 1341). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Managing Calculations in Atoll). 3. Assigning a frequency band to each cell and a relevant propagation model to each transmitter (see "Creating or Modifying a Cell" on page 1179 and "Creating or Modifying a Transmitter" on page 1179).

1186

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

11.2.6

Setting the Working Area of an Atoll Document

When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project might cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it would not be necessary. Consequently, you can restrict a coverage prediction to the base stations that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of base stations covered by a coverage prediction, each with its own advantages: Filtering the desired base stations You can simplify the selection of base stations to be studied by using a filter. You can filter base stations according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 84. This enables you to keep only the base stations with the characteristics you want for your calculations. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 74. Setting a computation zone Drawing a computation zone to encompass the base stations to be studied limits the number of base stations to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated calculations in order to see the effects of small changes in the base station configuration, the savings in time may be considerable. Limiting the number of base stations by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot zones. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus zone or hot spot zones are the areas taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 1195. You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.

11.2.7

Studying a Single Base Station

As you create a base station, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of base stations can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the base station you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of base stations once you have optimised the settings for each individual base station. Before studying a base station, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates propagation losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Any coverage prediction you make on a base station uses the propagation model to calculate its results. In this section, the following are explained: "Making a Point Analysis to Study the Profile" on page 1187. "Studying Signal Level Coverage" on page 1189.

11.2.7.1

Making a Point Analysis to Study the Profile

In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a user. Before studying a site, you must assign a propagation model. Atoll uses the propagation model and takes the radio and geographic data into account to calculate losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 1193. You can make a point analysis to: study the reception in real time along a profile between a reference transmitter and a user, study the interference along a profile between a reference transmitter and a user, and evaluate the signal levels coming from the surrounding transmitters at a given point (using existing path loss matrices).

To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1187

Atoll User Manual Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Profile tab. The profile analysis appears in the Profile tab of the Point Analysis Tool window. 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, with a green line indicating the line of sight (LOS). Atoll displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms into account). The main peak is the one that intersects the Fresnel ellipsoid the most. With some propagation models using a 3 knife-edge Deygout diffraction method, the results might display two additional attenuations peaks. The total attenuation is displayed above the main peak. The results of the analysis are displayed at the top of the Profile tab: The received signal strength from the selected transmitter for the cell with the highest reference signal power The propagation model used The shadowing margin and the cell edge coverage probability used for calculating it The distance between the transmitter and the receiver.

You can change the following options at the top of the Profile tab: Transmitter: Select the transmitter from the list. Geographic Profile: Select the Geographic Profile check box if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses. Snap to Subscribers: Select the Snap to Subscribers check box if you want to study the profile between a subscriber and the transmitter. The receiver snaps to the nearest subscriber when you move it. Atoll displays the profile between the transmitter and the receiver with clutter heights, giving terminal and antenna gains and losses. An ellipsoid indicating the Fresnel zone is also displayed. The displayed profile is between the selected transmitter and the subscriber; not between the subscriber and its serving transmitter.

Note:

5. Right-click the Profile tab to choose one of the following commands from the context menu: Properties: Select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. In You can: Change the X and Y coordinates to change the present position of the receiver. If Snap to Subscribers is selected on the Profile tab, define the Receiver Orientation: "To Selected Server" or "To Subscriber Server." - Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Select Signal Level, Path loss, or Total losses from the Result Type list. - You can select the Indoor Coverage check box to add indoor losses. Link Budget: Select Link Budget to display a dialogue with the link budget. Model Details: Select Model Details to display a text document with details on the displayed profile analysis. Model details are only available for the Standard Propagation Model. Displays data, including received signal, shadowing margin, cell edge coverage probability, propagation model used, and transmitter-receiver distance.

You can select a different transmitter.

Fresnel ellipsoid

Line of sight

Attenuation with diffraction

Figure 11.651: Point Analysis Tool - Profile tab 6. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.

1188

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

11.2.7.2

Studying Signal Level Coverage

While you are building your radio-planning project, you might want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single base station. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. For a transmitter with more than one cell, the signal level is calculated for the cell with the highest reference signal power. Note: You can use the same procedure to study the signal level coverage of several base stations by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 69.

To study the signal level coverage of a single base station: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder and select Group By > Sites from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated.

Tip:

If you want to study only sites by their status, you could group them by status.

3. Select the propagation parameters to be used in the coverage prediction: a. Click the Expand button ( ) to expand the Transmitters folder. b. Right-click the group of transmitters you want to study. The context menu appears. c. Select Open Table from the context menu. A table appears with the properties of the selected group of transmitters. d. In the table, you can configure two propagation models: one for the main matrix, with a shorter radius and a higher resolution, and another for the extended matrix, with a longer radius and a lower resolution. By calculating two matrices you can reduce the time of calculation by using a lower resolution for the extended matrix and you can obtain more accurate results by using propagation models best suited for the main and extended matrices. e. In the Main Matrix column: f. Select a Propagation Model. Enter a Radius and Resolution.

If desired, in the Extended Matrix column: Select a Propagation Model. Enter a Radius and Resolution.

g. Close the table. 4. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. The Study Types dialogue lists the coverage prediction types available. They are divided into Standard Studies, supplied with Atoll, and Customised Studies. Unless you have already created some customised studies, the Customised Studies list will be empty. 5. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 6. You can configure the following parameters in the Properties dialogue: General tab: You can change the assigned Name of the coverage prediction, the Resolution, and the storage Folder for the coverage prediction, and add some Comments. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient:

Size of the Coverage Prediction

City Centre City County State Country

Display Resolution
5m 20 m 50 m 100 m According to the size of the country

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1189

Atoll User Manual

Note:

If you create a new coverage prediction using the context menu of either the Transmitters or Predictions folder, you can select the sites using the Group By, Sort, and Filter buttons under Configuration. Because you already selected the target sites, however, only the Filter button is available.

Condition tab: The coverage prediction parameters on the Condition tab allow you to define the signals that will be considered for each pixel (see Figure 11.652). At the top of the Condition tab, you can set the signal level range to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, a longer time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration. 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.

Figure 11.652: Condition settings for a coverage prediction by signal level Display tab: You can modify how the results of the coverage prediction will be displayed. Note: Under Display Type, select "Value Intervals." Under Field, select "Best Signal Level." You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 32. You can create a tooltip with information about the coverage prediction by clicking the Browse button ( ) beside the Tip Text box and selecting the fields you want to display in the tooltip. 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 might make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results.

7. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event 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 on the Data tab. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button ( ) beside the coverage prediction in the Predictions ). ), Atoll only calculates unlocked coverage predictions (

11.2.8

Studying Base Stations

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects the rectangle containing the computation zone. Figure 11.653 gives an example of a computation zone. In Figure 11.653, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be

1190

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction. Site 130 is within the coverage zone but has no active transmitters. Therefore, it will not be taken into consideration either.

Figure 11.653: An example of a computation zone Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main propagation model with a shorter radius (displayed with a blue square in Figure 11.653) and a higher resolution and an extended propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower resolution path loss matrices outside the area covered by the main propagation model. In this section, the following are explained: "Path Loss Matrices" on page 1191. "Assigning a Propagation Model" on page 1193. "The Calculation Process" on page 1195. "Creating a Computation Zone" on page 1195. "Setting Transmitters or Cells as Active" on page 1196. "Signal Level Coverage Predictions" on page 1196. "Analysing a Coverage Prediction" on page 1200. "LTE Coverage Predictions" on page 1209. "Printing and Exporting Coverage Prediction Results" on page 1225.

11.2.8.1

Path Loss Matrices

In addition to the distance between the transmitter and the receiver, path loss is caused by objects in the transmitterreceiver path. In Atoll, the path loss matrices must be calculated before predictions and simulations can be made.

Storing Path Loss Matrices

Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1191

Atoll User Manual will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: One file per transmitter with the extension LOS for its main path loss matrix. A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.

To set the storage location of the path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss matrices and the location for the shared path loss matrices: Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are loading path loss matrices from a shared location, where you store your changes to shared path loss matrices. Click the button beside the 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. Note: Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private Directory.

Caution:

When you save the path loss files externally, the external files are updated as soon as calculations are performed. 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 path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual.

5. Click OK.

Checking the Validity of Path Loss Matrices

Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the following display options: Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.

The Available Results table lists the following information for each displayed path loss matrix: Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a Boolean field indicating whether or not the path loss matrix is valid. Origin of Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed.

5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 11.654) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.

1192

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.654: Path loss matrices statistics

11.2.8.2

Assigning a Propagation Model

In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 1194, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 1194, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 1193, this is the propagation model that will be used for all transmitters, except for those to which you have assigned a propagation model either individually or as part of a group. Important: 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. 3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 170, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following are explained: "Assigning a Propagation Model to All Transmitters" on page 1193. "Assigning a Propagation Model to a Group of Transmitters" on page 1194. "Assigning a Propagation Model to One Transmitter" on page 1194.

For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.

Assigning a Propagation Model to All Transmitters

In Atoll, you can assign a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main Matrix: Select a Propagation Model Enter a Radius and Resolution.

6. If desired, under Extended Matrix: Select a Propagation Model Enter a Radius and Resolution.

7. Click OK. The selected propagation models will be used for all transmitters.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1193

Atoll User Manual

Note:

Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 1194 will override this entry.

Assigning a Propagation Model to a Group of Transmitters

Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. From the Group By submenu of the context menu, select the property by which you want to group the transmitters. The objects in the folder are grouped by that property. Note: You can group transmitters by several properties by using the Group By button on the Properties dialogue. For more information, see "Advanced Grouping" on page 70.

4. Click the Expand button ( ) to expand the Transmitters folder. 5. Right-click the group of transmitters to which you want to assign a main and extended propagation model. The context menu appears. 6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected group. For each transmitter, you can set the propagation model parameters in the following columns: Main Propagation Model Main Calculation Radius (m) Main Resolution (m) Extended Propagation Model Extended Calculation Radius (m) Extended Resolution (m)

7. To enter the same values in one column for all transmitters in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

Assigning a Propagation Model to One Transmitter

If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previously made globally. To define a main and extended propagation model for all transmitters: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main Matrix: Select a Propagation Model. Enter a Radius and Resolution.

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

8. Click OK. The selected propagation models will be used for the selected transmitter.

1194

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Note:

You can also define the propagation models for a transmitter by right-clicking it in the map window and selecting Properties from the context menu.

11.2.8.3

The Calculation Process

When you create a coverage prediction and click the Calculate button ( ), Atoll follows the following process: 1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button ( ). ) beside the coverage prediction 3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( in the Predictions folder. Notes: You can stop any calculations in progress by clicking the Stop Calculations button ( the toolbar. ) in

When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.

11.2.8.4

Creating a Computation Zone

To create a computation zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Computation Zone folder. The context menu appears. 4. Select Draw from the context menu. 5. Draw the computation zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. The computation zone is delimited by a red line. If you clear the computation zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a computation zone with one of the following methods: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and selecting Use as > Computation Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computation Zone folder on the Geo tab and selecting Import from the context menu. Fit to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation Zone folder on the Geo tab and selecting Fit to Map Window from the context menu. Note: You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: Saving the computation zone in the user configuration: For information on exporting the computation zone in the user configuration, see "Exporting a User Configuration" on page 79. Exporting the computation zone: You can export the computation zone by rightclicking the Focus Zone folder on the Data tab of the Explorer window and selecting Export from the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1195

Atoll User Manual

11.2.8.5

Setting Transmitters or Cells as Active

When you make a coverage prediction, Atoll considers all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, before you define a coverage prediction, you must ensure that all the transmitters on the base stations you wish to study have been activated. In the Explorer window, active transmitters are indicated with a red icon ( ) in the Transmitters folder and with the defined colour on the map and inactive transmitters are indicated with an empty icon ( )in the Transmitters folder and on the map. In Atoll, you can also set the cell on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zones context menu. To set an individual transmitter as active: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the Transmitters folder.

3. Right-click the transmitter you want to activate. The context menu appears. 4. Select Active Transmitter from the context menu. The transmitter is now active. To set more than one transmitter as active using the Transmitters context menu: 1. Click the Data tab of the Explorer window. 2. Select the transmitters you want to set as active: To set all transmitters as active, right-click the Transmitters folder. The context menu appears. To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and right-click the group of transmitters you want to set as active. The context menu appears.

3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one transmitter as active using the Transmitters table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitters parameters in a row. 4. For each transmitter that you want to set as active, select the check box in the Active column. To set more than one cell as active using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cells parameters in a row. 4. For each cell that you want to set as active, select the check box in the Active column. To set transmitters as active using a zone: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder.

3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. Note: If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 41.

4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll. 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 Administrator Manual.

11.2.8.6

Signal Level Coverage Predictions

Atoll offers a series of standard coverage predictions based on the measured signal level at each pixel; other factors, such as interference, are not taken into consideration. Coverage predictions specific to LTE are covered in "LTE Coverage Predictions" on page 1209. 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 study (which will appear under the heading Customised Studies in the Study Types dialogue). You can also select Duplicate from the coverage predictions context menu to create a copy. By dupli-

1196

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks cating an existing prediction that has the parameters you want to study, you can create a new coverage prediction more quickly. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the 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 import 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 "Exporting a User Configuration" on page 79. The following standard coverage predictions are explained in this section: "Making a Coverage Prediction by Signal Level" on page 1197 "Making a Coverage Prediction by Transmitter" on page 1198 "Making a Coverage Prediction on Overlapping Zones" on page 1199.

11.2.8.6.1

Making a Coverage Prediction by Signal Level

A coverage prediction by signal level allows you to predict coverage zones by the transmitter signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest reference signal power. To make a coverage prediction by signal level: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 11.655). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, a longer time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration. 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.

Figure 11.655: Condition settings for a coverage prediction by signal level 7. Click the Display tab. If you choose to display the results by best signal level, the coverage prediction results will be in the form of thresholds. If you choose to display the results by signal level, the coverage prediction results will be arranged according to transmitter. For information on adjusting the display, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.656). Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

1197

Atoll User Manual

Figure 11.656: Coverage prediction by signal level

11.2.8.6.2

Making a Coverage Prediction by Transmitter

A coverage prediction by transmitter allows the user to predict coverage zones by transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest reference signal power. To make a coverage prediction by transmitter: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Transmitter and click OK. The Coverage by Transmitter Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 11.657). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" 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. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration. 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.

Figure 11.657: Condition settings for a coverage prediction by transmitter 7. Click the Display tab.

1198

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks For a coverage prediction by transmitter, the Display Type "Discrete Values" based on the Field "Transmitter" is selected by default. Each coverage zone will then be displayed with the same colour as that defined for each transmitter. For information on defining transmitter colours, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.658).

Figure 11.658: Coverage prediction by transmitter

11.2.8.6.3

Making a Coverage Prediction on Overlapping Zones

Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction on overlapping zones on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest reference signal power. To make a coverage prediction on overlapping zones: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Overlapping Zones and click OK. The Overlapping Zones Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 11.659). On the Condition tab, you can define the signals that will be considered for each pixel. At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" 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. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1199

Atoll User Manual

Figure 11.659: Condition settings for a coverage prediction on overlapping zones 7. Click the Display tab. For a coverage prediction on overlapping zones, the Display Type "Value Intervals" based on the Field "Number of Servers" is selected by default. Each overlapping zone will then be displayed in a colour corresponding to the number of servers received per pixel. For information on defining display properties, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.660).

Figure 11.660: Coverage prediction on overlapping zones

11.2.8.7

Analysing a Coverage Prediction

Once you have performed a coverage prediction study, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 1189). If several coverage predictions are visible on the map, it may be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which coverage predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following tools are explained: "Displaying the Legend Window" on page 1201. "Displaying Coverage Prediction Results Using Tooltips" on page 1201. "Using the Point Analysis Reception Tab" on page 1201. "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 1202. "Displaying a Coverage Prediction Report" on page 1203. "Viewing Coverage Prediction Statistics" on page 1204.

1200

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks "Comparing Coverage Predictions: Examples" on page 1205.

11.2.8.7.1

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

11.2.8.7.2

Displaying Coverage Prediction Results Using Tooltips

You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tool tips. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 1189). To get coverage prediction results in the form of tool tips: 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 tooltip appears with the information defined in the Display tab of the coverage prediction properties (see Figure 11.661).

Figure 11.661: Displaying coverage prediction results using tool tips

11.2.8.7.3

Using the Point Analysis Reception Tab

Once you have calculated the coverage prediction, you can use the Point Analysis tool. The Point Analysis window gives you information on reception for any point on the map. The Reception tab gives you information on the reference signal, SS, PBCH, PDSCH, PDCCH, and PUSCH and PUCCH signal levels, C/(I+N), bearers, and throughputs, etc. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. The analysis is based on: The reference signal levels, used to determine the best server for the pixel. The best serving transmitter is determined according to the received reference signal level from the cell with the highest reference signal power. If more than one cell cover the pixel, the one with the lowest layer is selected as the serving (reference) cell. The reference signal C/N, used to determine whether SU-MIMO or transmit or receive diversity is used in case of AMS, and whether MU-MIMO can be used in uplink or not. The PDSCH signal levels, downlink traffic loads, and ICIC ratios for determining the PDSCH C/(I+N), bearer, and throughputs. The PUSCH & PUCCH signal levels and uplink noise rise for determining the PUSCH & PUCCH C/(I+N), bearer, and throughputs.

The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations. You can make a reception analysis to verify a coverage prediction. In this case, before you make the point analysis, ensure the coverage prediction you want to verify is displayed on the map. To make a reception analysis: 1. Click the Point Analysis button ( Figure 11.662). 2. Click the Reception tab. 3. At the top of the Reception tab, select "Cells Table" from Load Conditions. 4. If you are making a reception 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. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue appears. Edit the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class. ) on the toolbar. The Point Analysis Tool window appears (see

c. Click OK to close the Properties dialogue. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

1201

Atoll User Manual 5. Select the signal to be displayed from the Display list. 6. Move the pointer over the map to make a reception analysis for the current location of the pointer. 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 reference signal level. 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. Click the Point Analysis button ( Select the load conditions to use in this analysis from simulations or from the Cells table. ) on the toolbar again to end the point analysis. Select the parameters of the probe user to be studied.

The reference signal reception from the best server (top-most bar) and all interfering cells. Solid bars indicate the signal levels above the minimum RSRP.

The connection status (reference signals, downlink and uplink) for the current point. : Service available : Service unavailable

Figure 11.662: Point Analysis Tool: Reception tab 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). The minimum RSRP. The portion of the bar which is not filled 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 dialogue with additional information with respect to the best server: Reference Signals: Azimuth and tilt of the receiver, total losses, received reference signal power, reference signal C/(I+N), RSRP, RSRQ, RSSI. Downlink: Diversity mode, SS received power, PBCH received power, PDCCH received power, PDSCH received power, SS & PBCH total noise, PDSCH & PDCCH total noise (I+N), SS C/(I+N), PBCH C/(I+N), PDCCH C/(I+N), PDSCH C/(I+N), bearer, channel throughputs, cell capacities, and average user throughputs. Uplink: Diversity mode, received PUSCH & PUCCH power, transmission power, allocated bandwidth, PUSCH & PUCCH total noise (I+N), PUSCH & PUCCH C/(I+N), bearer, channel throughputs, cell capacities, allocated bandwidth throughputs, and average user throughputs. To get all the above information in a single report: a. Right-click the Point Analysis window and select Report from the context menu. The Analysis Report dialogue appears.

11.2.8.7.4

Creating a Focus or Hot Spot Zone for a Coverage Prediction Report

The focus and hot spot zones define the area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spot zones in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones. To define a focus zone or hot spot zone: 1. Click the Geo tab in the Explorer window. 2. Click the Expand button ( ) to expand the Zones folder.

3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. Select Draw from the context menu.

1202

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 5. Draw the focus or hot spot zone: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot zone as follows: Vector Edition toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Edition toolbar to draw the focus or hot spot zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot zone by right-clicking it and selecting Use as > Focus Zone or Use as > New Hot Spot from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot spot zones, you can import the name given to each zone as well. Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map Window from the context menu. Notes: You can save the focus zone or hot spot zones, so that you can use it in a different Atoll document, in the following ways: Saving the focus zone in the user configuration: For information on exporting the focus zone in the user configuration, see "Exporting a User Configuration" on page 79. - Exporting the focus zone or hot spot zones: You can export the focus zone or hot spot zones by right-clicking the Focus Zone or the Hot Spot Zones folder on the Data tab of the Explorer window and selecting Export from the context menu.. You can include population statistics in the focus or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. -

11.2.8.7.5

Displaying a Coverage Prediction Report

Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage predictions Properties dialogue. The coverage prediction report is displayed in a table. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 58. Atoll bases the report on the area covered by the focus zone and hot spot zones; if no focus zone is defined, Atoll will use the computation zone. Using a focus zone enables you to create a report without the border effect. In other words, the results of a coverage prediction are delimited by the computation zone; results close to the border are influenced by fact that no calculations have been made outside the computation zone. Basing a report on a focus zone that is smaller than the computation zone eliminates the border effect. By using a focus zone for the report, you can create a report for a specific number of base stations, instead of creating a report for every site that has been calculated. The focus zone or hot spot zone must be defined before you display a report; it is not necessary to define it before computing coverage. The focus or hot spot zone does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 1202. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down. to move it up or

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1203

Atoll User Manual You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. The Open dialogue appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied. 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the focus zone if available or on the hot spot zones and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 4. 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. You can save the current report format in a configuration: a. Under Configuration, click the Export button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can apply a configuration that you have saved previously: a. Under Configuration, click the Import button. a appears. b. Select the configuration you want to import and click Open. The imported report configuration is applied 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spot zone by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 113. 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 spot zone: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. 2. Display the report as explained above. 3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears. 4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the population map: "Population" (Population): The number of inhabitants covered. "Population" (% Population): The percentage of inhabitants covered. "Population" (Population [total]): The total number of inhabitants inside the zone. to move it up or

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 customers/km, etc.). Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable Versus Non Integrable Data" on page 129.

11.2.8.7.6

Viewing Coverage Prediction Statistics

Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage study colours, interval steps, and shading as defined in the Display tab of the coverage predictions Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area.

1204

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone, you can display the statistics for a specific number of base stations, instead of displaying statistics for every base station that has been calculated. Hot spot zones are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before computing coverage. For information on defining a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 1202. To display the statistics on a coverage prediction: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Predictions folder.

3. Right-click the coverage prediction whose statistics you want to display. The context menu appears. 4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined by the focus zone (see Figure 11.663). Under Histogram Based on Covered Areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Detailed Results section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics Based on Study Conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.

Figure 11.663: Histogram of a coverage prediction by signal level

11.2.8.7.7

Comparing Coverage Predictions: Examples

Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison study coverage in one of the following ways: Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered by both coverage 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 only are green, and pixels covered only by the second prediction are blue).

To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1205

Atoll User Manual 5. Calculate the duplicate coverage prediction. 6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage between them. In this section, the following examples are explained: "Example 1: Studying the Effect of a New Base Station" on page 1206 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 1208.

Example 1: Studying the Effect of a New Base Station

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how you can verify if a newly added base station improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 1197. The results are displayed in Figure 11.664. An area with poor coverage is visible on the right side of the figure.

Figure 11.664: Signal level coverage prediction of existing network A new base station is added, either by creating the base station and adding the transmitters, as explained in "Creating an LTE Base Station" on page 1173, or by placing a station template, as explained in "Placing a New Base Station Using a Station Template" on page 1180. Once the new site has been added, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new base station (see Figure 11.665).

1206

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.665: 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 dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their 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 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 11.666, shows clearly the area covered only by the new base station.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1207

Atoll User Manual

Figure 11.666: Comparison of both signal level coverage predictions

Example 2: Studying the Effect of a Change in Transmitter Tilt

If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, we will look at how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 1198. The results are displayed in Figure 11.667. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated with a red oval in the figure.

Figure 11.667: Coverage prediction by transmitter of existing network You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue. Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original coverage prediction 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 11.668).

1208

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.668: Coverage prediction by transmitter of network after modifications As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change in coverage, you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their 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 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 11.669, shows clearly the increase in coverage due at the change in antenna tilt.

Figure 11.669: Comparison of both transmitter coverage predictions

11.2.8.8

LTE Coverage Predictions

Two types of LTE coverage predictions are available in Atoll: coverage predictions used to analyse the effective signal levels, and coverage predictions used to analyse the signal quality. Effective signal analysis coverage predictions can be used to analyse different signals (reference signals, SS, PBCH, PDSCH, and PDCCH) in the downlink as well as in the uplink once the user-end gains and losses have been considered. These coverage predictions do not depend on the network load conditions.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1209

Atoll User Manual Using signal quality coverage predictions you can study the effective service coverage area and capacity of each cell in the network. These coverage predictions depend on the interference in the network and the cell load conditions. For this reason, the network load must be defined in order to calculate these coverage predictions. For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined service, mobility type, and terminal. The following are explained in the following sections: "Service and User Modelling" on page 1210.

This section explains the coverage predictions available for analysing the effective signal level and signal quality. The following are explained: "Analysing the Effective Signal Levels" on page 1212. "Analysing the Signal Quality" on page 1213.

You can also use the Point Analysis window to study the interference level at a point. Load conditions can be selected for the analysis as well as the characteristics of the user-definable probe receiver, i.e., a terminal, a mobility, and a service: "Analysing Interference Areas Using a Point Analysis" on page 1223.

11.2.8.8.1

Service and User Modelling

Atoll can base its signal quality studies on the DL traffic load and the UL noise rise entered in the Cells table (for more information, see "Setting the Traffic Loads and the UL Noise Rise" on page 1214). Before you can model services, you must define LTE radio bearers. For more information on LTE radio bearers, see "Defining LTE Radio Bearers" on page 1344. In this section, the following are explained: "Modelling Services" on page 1210. "Modelling Mobility Types" on page 1211. "Modelling Terminals" on page 1211.

Modelling Services
Services are the various services available to users. These services can be either voice or data type services. This section explains how to create a service. The following parameters are used in predictions: Throughput scaling factor Throughput offset Body loss

To create or modify a service: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the LTE Parameters folder.

3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. Note: You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.

5. You can edit the fields on the General tab to define the new service. Some fields depend on the type of service you choose. You can change the following parameters. 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 a voice type service during Monte Carlo simulations. 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. Max Throughput Demand: Enter the highest throughput that the service can demand in the uplink and downlink. Min. Throughput Demand: Enter the minimum required throughput that the service should have in order to be available in the uplink and downlink. 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 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.

6. Click OK.

1210

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Modelling Mobility Types

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. 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. To create or modify a mobility type: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the LTE Parameters folder.

3. Right-click the Mobility Types folder. The context menu appears. 4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears. Note: You can modify the properties of an existing mobility type by right-clicking the mobility type in the Mobility Types folder and selecting Properties from the context menu.

5. You can enter or modify the following parameters in the Mobility Types New Element Properties dialogue: Name: Enter a descriptive name for the mobility type. Average Speed: Enter an average speed for the mobility type. This field is for information only; the average speed is not used by any calculation.

6. Click OK.

Modelling 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 onboard navigation device. The following parameters are used in predictions: Antenna LTE equipment Maximum and minimum terminal power Gain and losses Noise figure Supported antenna diversity technique Number of transmission and reception antenna ports for MIMO

To create or modify a terminal: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the LTE Parameters folder.

3. Right-click the Terminals folder. The context menu appears. 4. Select New from the context menu. The Terminals New Element Properties dialogue appears. Note: You can modify the properties of an existing terminal by right-clicking the terminal in the Terminals folder and selecting Properties from the context menu.

5. You can enter or modify the following parameters in the Terminals New Element Properties dialogue: Name: Enter a descriptive name for the terminal. Under Transmission/Reception, Min Power: Enter the minimum transmission power of the terminal. Max Power: Enter the maximum transmission power of the terminal. Noise Figure: Enter the noise figure of the terminal (used to calculate the downlink total noise). Losses: Enter the losses of the terminal. LTE Equipment: Select an LTE equipment from the list of available equipment. For more information on LTE equipment, see "Defining LTE Equipment" on page 1345. Under Antenna, 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 omnidirectional 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. -

Note:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1211

Atoll User Manual Diversity Support: Select whether the terminal type supports MIMO or not. Antenna diversity gains will be applied to MIMO users. Under Number of Antenna Ports, enter the number of antenna ports available in the terminal for Transmission and Reception.

6. Click OK.

11.2.8.8.2

Analysing the Effective Signal Levels

Atoll offers a couple of LTE coverage predictions which can be based on the predicted signal level from the best server and the thermal background noise at each pixel, i.e., received carrier power (C) and the carrier-to-noise ratio (C/N). This section explains the coverage predictions available for analysing the effective signal levels. 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, PDSCH including the PDCCH and the downlink traffic channel, and PUSCH, in the part of the network being studied. Atoll calculates the serving transmitter for each pixel depending on the downlink reference signal level. The serving transmitter is determined according to the received reference signal level from the cell with the highest reference signal power. If more than one cell cover the pixel, the one with the lowest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the effective signal (C or C/N for reference signals, SS, etc.). Pixels are coloured if the display threshold condition is fulfilled (in other words, if the C or C/N is higher than the C or C/N threshold). To make an effective signal analysis coverage prediction: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Effective Signal Analysis (DL) or Effective Signal Analysis (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 11.670). On the Condition tab, you can select a Terminal, a Mobility type, and a Service. The effective signal analysis coverage prediction is always a best server coverage prediction. The Noise Figure defined in the terminal types properties dialogue 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 LTE equipment, see "Modelling Services" on page 1210, "Modelling Terminals" on page 1211, "Modelling Mobility Types" on page 1211, and "Defining LTE Equipment" on page 1345, respectively. 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 for the effective signal analysis calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Figure 11.670: Condition settings for an effective signal analysis coverage prediction 7. Click the Display tab. 8. From the Display Type list, choose one of the following: You can choose between displaying results by Best RSRP (RS EPRE) Level (DL) (dBm), Best Reference Signal Level (DL), Best SS Signal Level (DL), Best PBCH Signal Level (DL), Best PDCCH Signal Level (DL), Best PDSCH Signal Level (DL), Reference Signal C/N Level (DL), SS C/N Level (DL), PBCH C/N Level (DL), PDCCH C/N Level (DL), PDSCH C/N Level (DL), or Delta Path Loss for the Effective Signal Analysis (DL),

1212

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks and by PUSCH & PUCCH Signal Level (UL) or PUSCH & PUCCH C/N Level (UL) for the Effective Signal Analysis (UL). The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 9. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.671 and Figure 11.672).

Figure 11.671: PDSCH C/N coverage prediction

Figure 11.672: PUSCH & PUCCH C/N coverage prediction

11.2.8.8.3

Analysing the Signal Quality

In LTE, the capacity and the effective service coverage areas of cells are influenced by network loads. As the network load increases, the area where a cell provides service decreases. For this reason, network loads must be defined in order to calculate these coverage predictions.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1213

Atoll User Manual Atoll offers a series of coverage predictions which are based on the predicted signal level from the best server and the predicted signal levels from other cells (interference) at each pixel, i.e., carrier-to-interference-and-noise ratio, or C/(I+N). The downlink interference received from different cells of the network is weighted by their respective downlink traffic loads. The measure of uplink interference for each cell is provided by the uplink noise rise. If you have traffic maps, you can do a Monte Carlo simulation to determine the downlink traffic loads and the uplink noise rise values for a generated user distribution. If you do not have traffic maps, Atoll can calculate these coverage predictions using the downlink traffic loads and the uplink noise rise values defined for each cell. In this section, these coverage predictions will be calculated using downlink traffic loads and the uplink noise rise values defined at the cell level. Before making a prediction, you will have to set the downlink traffic loads and the uplink noise rise, and the parameters that define the services and users. These are explained in the following sections: "Setting the Traffic Loads and the UL Noise Rise" on page 1214.

Several signal quality coverage predictions are explained in this section. The following studies are explained: "Making a Coverage by C/(I+N) Level" on page 1214. "Making a Coverage by Best Bearer" on page 1216. "Making a Coverage by Throughput" on page 1218. "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1221. "Making a Coverage by Quality Indicator" on page 1221. "Analysing Interference Areas Using a Point Analysis" on page 1223.

Setting the Traffic Loads and the UL Noise Rise

If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the Cells tab of the transmitters Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all the cells using the Cells table. To set the traffic loads and the uplink noise rise using the Cells table: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Enter a value in the following columns: Traffic Load (DL) (%) ICIC Ratio (DL) (%) UL Noise Rise (dB) ICIC UL Noise Rise (dB)

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 UL Noise Rise (dB). For a definition of the values, see "Cell Description" on page 1176. 5. To enter the same values in one column for all cells in the table: a. Enter the value in the first row in the column. b. Select the entire column. c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells. Note: If you want to copy the contents of the last cell in the selection into all other cells, you can select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working with Data Tables" on page 53.

Making a Coverage by C/(I+N) Level

Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels in the part of the network being studied. Atoll calculates the serving transmitter for each pixel depending on the downlink reference signal level. The serving transmitter is determined according to the received reference signal level from the cell with the highest reference signal power. If more than one cell cover the pixel, the one with the lowest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured if the display threshold condition is fulfilled (in other words, if the C/(I+N) is higher than C/(I+N) threshold). Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference, which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information on frequency bands, see "Defining Frequency Bands" on page 1341. The reference signal C/(I+N) is calculated using the reference signal power. Interference on the reference signals is in part caused by the reference signals from interfering cells and in part by the PDSCH transmission. The SS C/(I+N) is calculated using the SS power. Interference on the SS is caused by the SS transmission from interferering cells, respectively. The PBCH C/(I+N) is calculated using the PBCH power. Interference on the PBCH is caused by the PBCH transmission from interferering cells, respectively. The PDCCH C/(I+N) is calculated using the PDCCH power. Interference on the PDCCH is caused by PDCCH transmission from interfereing cells. The PDSCH C/(I+N) is calculated using the PDSCH power. Interference on the PDSCH is caused by PDSCH transmission from interfereing cells. PDSCH interference depends on

1214

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks the downlink traffic loads and ICIC ratios of interfering cells. The PUSCH & PUCCH C/(I+N) is calculated using the terminal power calculated after power control and the uplink noise rise values stored either in the cell properties or in the selected simulation results. To make a coverage prediction by C/(I+N) level: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 11.673). 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. Note: 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, 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 dialogue 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 LTE equipment, see "Modelling Services" on page 1210, "Modelling Terminals" on page 1211, "Modelling Mobility Types" on page 1211, and "Defining LTE Equipment" on page 1345, respectively. 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 for C(I+N) calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Figure 11.673: Condition settings for a coverage prediction by C/(I+N) level 7. Click the Display tab. You can choose between displaying results by RSRQ Level (DL) (dB), RSSI Level (DL) (dBm), Reference Signal C/(I+N) Level (DL), SS C/(I+N) Level (DL), PBCH C/(I+N) Level (DL), SS & PBCH Total Noise (I+N) (DL), PDCCH C/(I+N) Level (DL), PDSCH C/(I+N) (DL), or PDSCH & PDCCH Total Noise (I+N) (DL) for the Coverage by C/(I+N) Level (DL) and by PUSCH & PUCCH C/(I+N) Level (UL), PUSCH & PUCCH Total Noise (I+N) (UL), Allocated Bandwidth (UL) (No. of Frequency Blocks), PUSCH & PUCCH C/(I+N) Level for 1 Frequency Block (UL), or Transmission Power (UL) (dBm) for the Coverage by C/(I+N) Level (UL). The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 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 1347.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1215

Atoll User Manual 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.674 and Figure 11.675).

Figure 11.674: Coverage prediction by PDSCH C/(I+N)

Figure 11.675: Coverage prediction by PUSCH & PUCCH C/(I+N)

Making a Coverage by Best Bearer

Downlink and uplink best radio bearer coverage predictions calculate and display the best LTE radio bearers based on C(I+N) for each pixel. To make a coverage prediction by best bearer: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears.

1216

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 4. Select Coverage by Best Bearer (DL) or Coverage by Best Bearer (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 11.676). 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. Note: 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, 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 dialogue 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 PDSCH C(I+N) level is performed using the bearer selection thresholds defined in the LTE equipment. This LTE 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. Note: You can make Atoll use only the bearers for which selection thresholds are defined in both the terminals and the cells LTE 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 LTE equipment, see "Modelling Services" on page 1210, "Modelling Terminals" on page 1211, "Modelling Mobility Types" on page 1211, and "Defining LTE Equipment" on page 1345, respectively. 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 for C(I+N) calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Figure 11.676: Condition settings for a coverage prediction on LTE bearers 7. Click the Display tab. You can display results by Best Bearer or Modulation. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.677 and Figure 11.678).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1217

Atoll User Manual

Figure 11.677: Coverage prediction by downlink best bearer

Figure 11.678: Coverage prediction by uplink best bearer

Making a Coverage by Throughput

Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities based on C(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1221. To make a coverage prediction by throughput: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74.

1218

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 6. Click the Condition tab (see Figure 11.679). 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. Note: 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, 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 dialogue 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 PDSCH C(I+N) level is performed using the bearer selection thresholds defined in the LTE equipment. This LTE 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. The mobility is used to indicate the bearer selection threshold graph to use. The service is used for the application throughput parameters defined in the service Properties dialogue. Note: You can make Atoll use only the bearers for which selection thresholds are defined in both the terminals and the cells LTE 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 LTE equipment, see "Modelling Services" on page 1210, "Modelling Terminals" on page 1211, "Modelling Mobility Types" on page 1211, and "Defining LTE Equipment" on page 1345, respectively. 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 for C(I+N) calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Figure 11.679: Condition settings for a throughput coverage prediction 7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. You can set parameters to display the following results: Channel throughputs: To display channel throughputs, select "Peak RLC Channel Throughput," "Effective RLC Channel Throughput," or "Application Channel Throughput" from the Field list. Cell capacities: To display cell capacities, select "Peak RLC Cell Capacity," "Effective RLC Cell Capacity," or "Application Cell Capacity" from the Field list. Average user throughputs: To display throughputs averaged per user, select "Peak RLC Throughput Averaged per User," "Effective RLC Throughput Averaged per User," or "Application Throughput Averaged per User" from the Field list. Allocated bandwidth throughputs in uplink: To display allocated bandwidth throughputs in uplink, select "Peak RLC Allocated Bandwidth Throughput," "Effective RLC Allocated Bandwidth Throughput," or "Application Allocated Bandwidth Throughput" from the Field list.

The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1219

Atoll User Manual 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 assigned to cells. 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 RLC channel throughputs. 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 LTE equipment defined in the selected terminal for downlink or the LTE 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. 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 average 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 average user throughput is calculated by dividing the allocated bandwidth throughput by the number of uplink users of the serving cell. 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 "The Global Transmitter Parameters" on page 1342. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.

Figure 11.680: Coverage prediction by downlink channel throughput

1220

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.681: Coverage prediction by uplink channel throughput

Making an Aggregate Throughput Coverage Prediction Using Simulation Results

Atoll calculates the aggregate peak RLC, effective RLC, and application cell throughputs during Monte Carlo simulations. The aggregate cell throughputs are the sums of the cells user throughputs. You can create a coverage prediction that calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its aggregate throughput. To create an aggregate throughput coverage prediction: 1. Create and run a Monte Carlo simulation. For more information on creating Monte Carlo simulations, see "Calculating and Displaying Traffic Simulations" on page 1256. 2. Create a coverage prediction by throughput as explained in "Making a Coverage by Throughput" on page 1218, with the following exceptions: a. On the Condition tab, select a simulation or group of simulations from the Load Conditions list. The coverage prediction will display the results based on the selected simulation or on the average results of the selected group of simulations. b. On the Display tab, you can display results by Peak RLC Aggregate Throughput, Effective RLC Aggregate Throughput, or Aggregate Application Throughput. The coverage prediction results will be in the form of thresholds. For information on defining the display, see "Display Properties of Objects" on page 32. 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 1269.

Making a Coverage by Quality Indicator

Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators (BLER, BER, etc.) based on the best LTE radio bearers and on C(I+N) for each pixel. To make a coverage prediction by quality indicator: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select New from the context menu. The Study Types dialogue appears. 4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK. The coverage predictions Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 184. Under Configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 74. 6. Click the Condition tab (see Figure 11.676). 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1221

Atoll User Manual

Note:

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, 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 types properties dialogue 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 PDSCH C(I+N) level is performed using the bearer selection thresholds defined in the LTE equipment, and the quality indicator graphs from the LTE equipment are used to determine the values of the selected quality indicator on each pixel. This LTE 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. Note: You can make Atoll use only the bearers for which selection thresholds are defined in both the terminals and the cells LTE 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 LTE equipment, see "Modelling Services" on page 1210, "Modelling Terminals" on page 1211, "Modelling Mobility Types" on page 1211, and "Defining LTE Equipment" on page 1345, respectively. 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 for C(I+N) calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor Coverage into consideration.

Figure 11.682: Condition settings for a coverage prediction by quality indicators 7. 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 1344. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 32. 8. Once you have created the coverage prediction, you can run it immediately or you can save it and run it later: Run: Click Run to save the defined coverage prediction and run it immediately OK: Click OK to save the defined coverage prediction without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.683 and Figure 11.684).

1222

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.683: Coverage prediction by downlink BLER

Figure 11.684: Coverage prediction by uplink BLER

11.2.8.8.4

Analysing Interference Areas Using a Point Analysis

In Atoll, you can study the interferers of a transmitter using the Point Analysis tool. To study interference areas using a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes ( ) in the Radio toolbar. The Point Analysis Tool window appears and the

) to represent the receiver.

3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.

4. Click the Interference tab. The Interference tab displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar indicating the total noise (I+N) experienced by the receiver, and bars representing the interference received from

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1223

Atoll User Manual each interferer. The information displayed in the bar graph depends on the selections made at the top of the Interference tab: Load Conditions: Select the load conditions Atoll will use to calculate interference: the settings defined in the Cells table, the load conditions from a traffic density map, or the load conditions from a simulation. Display: Select whether Atoll should display the interference on the RS, the SS, the PDSCH, or on the RS per RE. Select a Terminal, Service, and Mobility.

Figure 11.685 gives an example of the Interference tab. The signal level of the transmitter, Site0_1 (0), is -113.67 dB and is indicated by a red bar. The black bar indicates the total noise (I+N) experienced by the receiver (-103.55 dB). The interferer is responsible for -117.30 dB (blue). The displayed bars are all filled. However, if the bar corresponding to an interferer is 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. If you let the pointer rest on a bar, details are displayed in the tooltip: 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.

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 tooltip.

Figure 11.685: Point Analysis Tool - Interference tab 5. You can change the following options at the top of the Interference tab: Sort by Interference: You can select the Sort by Interference check box if you want Atoll to display the interfers by the effective interference received. Intra-technology: You can select the Intra-technology check box if you want Atoll to display the intra-technology interference.

6. Right-click the Interference tab and select Properties to display the Analysis Properties dialogue. This dialogue is available from the context menu on all tabs of the Point Analysis Tool window. 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. You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.

To get the details about the best server and all the interferers in the form of a report: a. Right-click the Point Analysis window and select Report from the context menu. The Analysis Report dialogue appears. 7. Click the Results tab. The Results tab displays, for each cell received, the cells name, its distance from the receiver, its physical cell ID status, as well as the received signal and received signal interference and the RSRP for all cells. Additionally, the interference is displayed for all cells except the best server. 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 in tool tips for these arrows. 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 received signal. 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 tooltip. 8. You can select a Terminal, Service, and Mobility at the top of the Results tab.

1224

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

11.2.8.9

Printing and Exporting Coverage Prediction Results

Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. 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 65. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 46. 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 49.

11.2.9

Planning Neighbours
You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you set. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbours only to the cells within the computation zone. The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo tab in the Explorer window is selected. Usually, you will allocate neighbours globally during the beginning of a radio planning project. Afterwards, you will allocate neighbours to base stations or transmitters as you add them. You can use automatic allocation on all cells in the document, or you can define a group of cells either by using a focus zone or by grouping transmitters in the Explorer window. For information on creating a focus zone, see "Using a Focus Zone or Hot Spot Zones" on page 43. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 69. Atoll supports the following neighbour types in an LTE network: Intra-technology neighbours: Intra-technology neighbours are cells defined as neighbours that also use LTE. Inter-technology neighbours: Inter-technology neighbours are cells defined as neighbours that use a technology other than LTE.

In this section, the following are explained: "Importing Neighbours" on page 1225 "Defining Exceptional Pairs" on page 1225 "Configuring Importance Factors for Neighbours" on page 1226 "Allocating Neighbours Automatically" on page 1226 "Checking Automatic Allocation Results" on page 1228 "Allocating and Deleting Neighbours per Cell" on page 1231 "Calculating the Importance of Existing Neighbours" on page 1233 "Checking the Consistency of the Neighbour Plan" on page 1234 "Exporting Neighbours" on page 1235.

11.2.9.1

Importing Neighbours
You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Data tab of the Explorer window. b. Right-click the Transmitters folder. The context menu appears. c. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 63.

11.2.9.2

Defining Exceptional Pairs

In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs can be taken into consideration when you manually allocate neighbours.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1225

Atoll User Manual To define exceptional pairs of neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Right-click the cell for which you want to define neighbour constraints. The context menu appears. 5. Select Record Properties from the context menu. The cells Properties dialogue appears. 6. Click the Intra-technology Neighbours tab. 7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( a. Select the cell from the list in the Neighbours column. b. In the Status column, select one of the following: Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell. ):

8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table by right-clicking the Transmitters folder and selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.

11.2.9.3

Configuring Importance Factors for Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible intra-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. On the intra-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency Factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 1226. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 1226.

5. Click OK.

11.2.9.4

Allocating Neighbours Automatically

Atoll can automatically allocate neighbours in an LTE network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. To allocate LTE neighbours automatically: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Automatic Neighbour Allocation tab. 5. You can set the following parameters: Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour. Max. No. of Neighbours: Set the maximum number of neighbours that can be allocated to a cell. This value can be either set here for all the cells, or specified for each cell in the Cells table. Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation.

1226

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Min RSRP: Select the Min RSRP check box if you want to set a global value for the Min RSRP. If you set a global Min RSRP value here, Atoll will either use this value or the per-cell Min RSRP value, whichever is higher. - RSRP Margin: Enter the margin, with respect to the best server coverage area of the reference cell (cell A), at which the handover process ends (see Figure 11.686). The higher the value entered for the RSRP Margin, the longer the list of candidate neighbours. The area between the best server coverage and the RSRP Margin constitutes the area within which Atoll will search for neighbours. - Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. - Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations. % Min. Covered Area: Enter the minimum surface area, in percentage, that a possible neighbour cells coverage area must overlap the reference cells coverage area. -

6. Select the desired calculation parameters: Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want cells located on the same site as the reference cell to be automatically considered as neighbours. Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell is the best server, or where the possible neighbour cell is the second best server (respecting the handover margin). Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neighbour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from the list of neighbours of the reference cell. Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see "Defining Exceptional Pairs" on page 1225. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.

Figure 11.686: The handover area between the reference cell and the possible neighbour 7. Click the Importance Weighting button to set the relative importance of possible neighbours: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 6., set the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell. Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 6., set the minimum and maximum importance of a possible neighbour cell being located on the same site as reference cell.

8. Click Calculate. Atoll begins the process of allocating neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Deleting existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

1227

Atoll User Manual Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance as calculated with the options selected in step 7. Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to the reference cell, as identified in the Cell column. The possible reasons are: Co-site Adjacency Symmetry Coverage Existing

Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell is best server or second best server.

9. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

10. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neighbours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue. Notes: A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint on the forbidden neighbour will be ignored by the algorithm because the neighbour already exists. When the options Force exceptional pairs and Force symmetry are selected, Atoll considers the constraints between exceptional pairs in both directions in order to respect symmetry. On the other hand, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event Viewer. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Exporting a User Configuration" on page 79.

11.2.9.4.1

Allocating Neighbours to a New Base Station

When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects the coverage area of the cells of the new base station. To allocate neighbours to a new base station: 1. On the Data tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects" on page 69. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 1226.

11.2.9.5

Checking Automatic Allocation Results

You can verify the results of automatic neighbour allocation in the following ways: "Displaying Neighbour Relations on the Map" on page 1229.

1228

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks "Displaying the Coverage of Each Neighbour of a Cell" on page 1230.

11.2.9.5.1

Displaying Neighbour Relations on the Map

You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

2. Select Display Options from the context menu. The Visual Management dialogue appears. 3. Under Intra-technology Neighbours, select the Display Links check box. 4. Click the Browse button ( ) beside the Display Links check box.

5. The Intra-technology Neighbour Display dialogue appears. 6. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a unique colour. Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours table, or according to the neighbour frequency band. Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to the importance, as determined by the weighting factors.

Tip:

You can display the number of handoff attempts for each cell-neighbour pair by first 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 along with "Value Intervals" as the Display Type. For information on adding a new field to a table, see "Adding a Field to an Object Types Data Table" on page 54.

Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you can display or hide neighbour link display types individually. For information on changing display properties, see "Display Properties of Objects" on page 32. 7. Select the Add to Legend check box to add the displayed neighbour links to the legend. 8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each neighbour link. 9. Click OK to save your settings. 10. Under Advanced, select which neighbour links to display: Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations where the selected cell is the reference cell and where the neighbour relation is not symmetric. Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations where the selected cell is neighbour and where the neighbour relation is not symmetric. Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the selected cell and the neighbour.

11. Click OK to save your settings. 12. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 14. Click the Visual Management button ( ) in the Radio toolbar.

15. Click a transmitter on the map to display the neighbour relations. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). Atoll displays the following information (see Figure 11.687) for the selected cell: The symmetric neighbour relations of the selected (reference) cell are indicated by a line. The outward neighbour relations are indicated by a line with an arrow pointing to the neighbour (e.g. see Site1_2(0)) in Figure 11.687.). The inward neighbour relations are indicated by a line with an arrow pointing to the selected cell (e.g. see Site9_3(0)) in Figure 11.687.).

In Figure 11.687, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is coloured as the reference transmitter as it is neighbour of Site9_3(0) here.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1229

Atoll User Manual

Figure 11.687: Neighbours of Site 22_3(0) - Display According to the Neighbour In Figure 11.688, neighbour links are displayed according to the frequency of the neighbour. Here, all neighbour relations are symmetric.

Figure 11.688: Neighbours of Site 22_3(0) - Display According to The Neighbour Frequency Note: You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

11.2.9.5.2

Displaying the Coverage of Each Neighbour of a Cell

By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cells neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a "Coverage by Transmitter" prediction, with the Display Type set to "Discrete Values" and the Field set to "Transmitter" (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 1198). 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

3. Select Display Options from the context menu. The Neighbourhood Display dialogue appears. 4. Under Intra-technology Neighbours, select the Display Coverage Areas check box. 5. Click the Browse button ( ) beside the Display Coverage Areas check box.

6. The Intra-technology Neighbour Display dialogue appears. 7. From the Display Type list, choose one of the following: Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neighbours with a unique colour.

1230

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology Neighbours table. Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cells neighbours according to the importance, as determined by the weighting factors.

8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the tooltip. This information will be displayed on each coverage area. 9. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. The menu appears.

10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 11. Click the Visual Management button ( ) in the Radio toolbar.

12. Click a transmitter on the map to display the coverage of each neighbour. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). 13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( Radio toolbar. ) in the

11.2.9.6

Allocating and Deleting Neighbours per Cell

Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of a transmitters Properties dialogue. This section explains the following: "Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1231. "Allocating or Deleting Neighbours Using the Neighbours Table" on page 1232. "Allocating or Deleting Neighbours on the Map" on page 1232.

Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete LTE neighbours using the Cells tab of the transmitters Properties dialogue: 1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, click the Browse button ( 5. Click the Intra-technology Neighbours tab. 6. If desired, you can enter the maximum number of neighbours. 7. Allocate or delete a neighbour. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table when you have finished creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 8. Click OK. ) beside Neighbours. The cells Properties dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1231

Atoll User Manual

Allocating or Deleting Neighbours Using the Neighbours Table

To allocate or delete LTE neighbours using the Neighbours table: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table appears. Note: For information on working with data tables, see "Working with Data Tables" on page 53.

4. Allocate or delete a neighbour. To allocate a new neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. To take into consideration all exceptionnal pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either some forced neighbours or some forbidden neighbours using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu. ), select a reference cell in the Cell column.

To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. To delete several symmetric neighbour relations: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour.

Allocating or Deleting Neighbours on the Map

You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 1229.

1232

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters to the intra-technology neighbours list. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitters from the intra-technology neighbours. To add an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the intra-technology neighbour list of the transmitter. To remove an outward neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the intra-technology neighbours list of the transmitter. To add an inward neighbour relation: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the intra-technology neighbours list of the reference transmitter. Notes: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.

11.2.9.7

Calculating the Importance of Existing Neighbours

After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 1226): Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference transmitters when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.

5. Coverage Conditions: Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1233

Atoll User Manual Min RSRP: Select the Min RSRP check box if you want to set a global value for the Min RSRP. If you set a global Min RSRP value here, Atoll will either use this value or the per-cell Min RSRP value, whichever is higher. RSRP Margin: Enter the margin, with respect to the best server coverage area of the reference cell (cell A), at which the handover process ends. Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

6. Click OK to save your modifications and close the Coverage Conditions dialogue. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. Notes: You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

7. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 4. Cause: The reason Atoll has allocated value in the Importance column. Co-site Adjacency Symmetry Coverage

Coverage: The amount of reference transmitters coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neighbour transmitter is best server or second best server. Distance: The distance in kilometres between the reference cell and the neighbour.

The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

11.2.9.8

Checking the Consistency of the Neighbour Plan

You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Intra-technology Neighbours tab. 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want 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 the Full Lists check box if you want 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 the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours.

1234

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Distance Between Neighbours: Select the Distance Between Neighbours > check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax: |CELL|

Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax: Note: |CELL| |NUMBER| |MAX NUMBER| If the field Max number of intra-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

11.2.9.9

Exporting Neighbours
The neighbour data of an Atoll document is stored in a series of tables. You can export the neighbour data to use it in another application or in another Atoll document. To export neighbour data: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours and then select the neighbour table containing the data you want to export from the context menu: Intra-Technology Neighbours: This table contains the data for the intra-technology neighbours in the current Atoll document. Inter-Technology Neighbours: This table contains the data for the inter-technology neighbours in the current Atoll document. Intra-technology Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document. Inter-technology Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs (forced and forbidden) in the current Atoll document.

4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files" on page 61.

11.2.10

Planning Frequencies
You can assign frequencies, i.e., frequency bands and channel numbers, manually to cells or use the Automatic Frequency Planning (AFP) tool to automatically allocate channels to cells. The AFP allocates channels to cells automatically such that the overall interference in the network is minimised. Once allocation is completed, you can analyse the frequency plan by creating and comparing C/(I+N) coverage predictions, and view the frequency allocation on the map. The procedure for planning frequencies is: Allocating frequencies "Automatically Allocating Frequencies to Cells" on page 1236.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1235

Atoll User Manual "Allocating Frequencies to Cells Manually" on page 1237. "Using the Search Tool to Display Frequency Allocation" on page 1237. "Displaying Frequency Allocation Using Transmitter Display Settings" on page 1238. "Grouping Transmitters by Frequencies" on page 1238. "Analysing the Frequency Allocation Using Coverage Predictions" on page 1239.

Displaying and analysing the frequency allocation

11.2.10.1

Allocating Frequencies
Atoll can automatically assign frequencies to cells according to set parameters. For example, the AFP takes into account the interference matrices, minimum reuse distance, and any constraints imposed by neighbours. The AFP can also be used to allocate physical cell IDs automatically to the cells of an network. The AFP can base the automatic frequency and physical cell ID allocation on interference matrices, whereas the automatic physical cell ID allocation feature available by default in the LTE module does not use interference matrices. Apart from this difference, the two physical cell ID allocation features are alike. For further information on physical cell IDs, see "Planning Physical Cell IDs" on page 1239. You can also allocate frequencies and physical cell IDs manually to cells. In this section, the following methods of allocating physical cell IDs are described: "Automatically Allocating Frequencies to Cells" on page 1236. "Allocating Frequencies to Cells Manually" on page 1237.

11.2.10.1.1

Automatically Allocating Frequencies to Cells

The AFP enables you to automatically allocate frequencies to cells in the current network. To automatically allocate frequencies: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Frequency Plan > Automatic Allocation. The Frequency Allocation dialogue appears. 4. Under Allocate, select Frequencies to perform automatic frequency planning. 5. Under Relations, you can set the relations to take into account in automatic allocation. Under Interference Matrices, you can calculate and take interference matrices into account for the frequency allocation. When the Frequency Allocation dialogue opens, the Take into account check box is disabled because interference matrices are not yet available. For more information on defining and calculating interference matrices for automatic allocation, see "Using Interference Matrices with the AFP" on page 1237. Take neighbours into account: Select this check box if you want the AFP to take neighbour relations into account for the allocation. For frequency 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 "Planning Neighbours" on page 1225. Take min reuse distance into account: Select this check box if you want the AFP to take relations based on distance into account for the allocation. You can enter the Default radius within which two cells whose channels have a co-channel overlap cannot have the same channel assigned. Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue or in the Cells table). If defined, a cell-specific reuse distance will be used instead of default the value entered here.

6. Under Results, Atoll displays the Total Cost of the current frequency allocation taking into account the parameters set in step 5. You can modify the parameters and click Recalculate Cost to see the change in the total cost. 7. Click Calculate. Atoll begins the process of allocating frequencies. Once Atoll has finished allocating frequencies, the proposed allocation is visible under Results. The Results table contains the following information: Site: The name of the base station. Transmitter: The name of the transmitter. Name: The name of the cell. Initial Channel Number: The channel number of the cell before automatic allocation. Channel Number: The channel number of the cell after automatic allocation. Channel Allocation Status: The value of the Channel Allocation Status of the cell. Initial Physical Cell ID: The physical cell ID of the cell before automatic allocation. Physical Cell ID: The physical cell ID of the cell after automatic allocation. Initial PSS ID: The PSS ID of the cell before automatic allocation. PSS ID: The PSS ID of the cell after automatic allocation. Initial SSS ID: The SSS ID of the cell before automatic allocation. SSS ID: The SSS ID of the cell after automatic allocation. Cost: The cost of the new frequency allocation of the cell. Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

1236

Chapter 11: LTE Networks Physical Cell ID Status: The value of the Physical Cell ID Status of the cell.

8. Click Commit. The channel numbers are committed to the cells.

Using Interference Matrices with the AFP

In Atoll, the probability of interference between pairs of cells is stored in an interference matrix. An interference matrix can be thought of as the probability that a user in a cell will receive interference higher than a defined threshold. The LTE AFP calculates interference matrices in the form of co- and adjacent channel interference probabilities for each interfered and interfering cell pair. The probabilities of interference are stated in terms of percentages of the interfered area. In other words, it is the ratio of the interfered surface area to the best server coverage area of an interfered cell. When Atoll calculates interference matrices, it calculates the ratio of the reference signal level to the total interference and noise (I+N) for each pixel of the interfered service area between two cells (the interfered cell and the interfering cell). For co-channel interference, a pixel is considered interfered if this ratio is lower than the per-channel reference signal C/N corresponding to the minimum RSRP defined for the interfered cell. For adjacent channel interference, a pixel is considered interfered if this ratio is lower than the reference signal C/N corresponding to the minimum RSRP 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 (i.e., 0 dB). To calculate interference matrices: 1. Enter a value for the Quality Margin. 2. Click the Calculate button. Atoll calculates the interference matrices. The calculation progress is displayed in the Event Viewer window. To stop the interference matrices calculation at any moment, click the Stop button. Interference matrices are calculated using the default calculation resolution set in the Properties dialogue of the Predictions folder. 3. Click the Close button once the interference matrices have been calculated. The Event Viewer window closes. To display details of the calculated interference matrices: 1. Click the Details button. The Interference Matrices Display dialogue appears. This dialogue lists all the interfered and interfering cell pairs and their respective interference probabilities in co- and adjacent channel cases. 2. Click the Close button. The Interference Matrices Display dialogue closes. To delete the calculated interference matrices: Click the Delete button.

To take the calculated interference matrices into account: Select the Take into account check box.

11.2.10.1.2

Allocating Frequencies to Cells Manually

When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically, as described in "Automatically Allocating Frequencies to Cells" on page 1236. 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. To allocate the frequency to a cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate the frequency. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Select the Cells tab. 4. Select a Frequency Band and Channel Number for the cell. 5. You can set the Channel Allocation Status to Locked if you want to lock the frequency that you assigned. 6. Click OK.

11.2.10.2

Displaying the Frequency Allocation

Once you have allocated frequencies, you can verify several aspects of the allocation. You can display frequencies in several ways: "Using the Search Tool to Display Frequency Allocation" on page 1237. "Displaying Frequency Allocation Using Transmitter Display Settings" on page 1238. "Grouping Transmitters by Frequencies" on page 1238. "Analysing the Frequency Allocation Using Coverage Predictions" on page 1239.

Using the Search Tool to Display Frequency Allocation

In Atoll, you can search for frequency bands and channel numbers using the Search Tool. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Frequencies and any potential prob-

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1237

Atoll User Manual lems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 1198. To find a frequency band using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Channel tab. 3. Select a Frequency Band from the list of available frequency bands. 4. Set Channel Number to All. 5. Click Search. Transmitters whose cells use the selected frequency band are displayed in red. Transmitters with cells using other frequency bands are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window. To find a channel number using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Channel tab. 3. Select a Frequency Band from the list of available frequency bands. 4. Select the Channel Number from the list of available channel numbers. 5. If you want only want the channel entered in the Channel Number box to be displayed, select the Co-channel Only check box. 6. 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 selected the Co-channel Only 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 Search Tool window. Note: 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 "Defining the Object Type Label" on page 35.

Displaying Frequency Allocation Using Transmitter Display Settings

You can display the frequency allocation on transmitters by using the transmitters display characteristics. To display the frequency allocation on the map: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete Values" as the Display Type and "Cells: Channel Number" as the Field. 6. Click OK. Transmitters will be displayed by channel number. You can also display the frequency band and channel number in the transmitter label or tooltip by selecting "Cells: Frequency Band" and "Cells: Channel Number" from the Label or Tip Text Field Definition dialogue. For information on display options, see "Display Properties of Objects" on page 32.

Grouping Transmitters by Frequencies

You can group transmitters on the Data tab of the Explorer window by their frequency bands or channel numbers. To group transmitters by frequency bands or channel numbers: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: Frequency Band

1238

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Channel Number Min Reuse Distance Channel Allocation Status

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. 8. 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 the transmitters will be grouped. . The selected parameter is removed from the list of parameters on which

9. 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 b. Select a parameter and click to move it up to the desired position. to move it down to the desired position.

10. Click OK to save your changes and close the Group dialogue.

Analysing the Frequency Allocation Using Coverage Predictions

You can create and compare reference signal C/(I+N) coverage predictions before and after the automatic frequency allocation in order to analyse and compare the improvements brought about by the AFP. For more information on creating reference signal C/(I+N) coverage predictions, see "Making a Coverage by C/(I+N) Level" on page 1214. For more information on comparing two coverage predictions, see "Comparing Coverage Predictions: Examples" on page 1205.

11.2.11

Planning Physical Cell IDs

In LTE, 504 physical cell IDs are available, numbered from 0 to 503. There are as many pseudo-random sequences defined in the 3GPP specifications. 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 in the range of 0 to 167, and a PSS ID is defined by a number in the range of 0 to 2. Each cells reference signals transmit a pseudo-random sequence corresponding to the physical cell ID of the cell. The SSS and PSS are transmitted over the center six frequency blocks independent of the channel bandwidths used by cells. Mobiles synchronise there transmission and reception frequency and time by listening first to the PSS. Once they know the PSS ID of the cell, they listen to the SSS of the cell in order to know the SSS ID. The combination of these two IDs gives the physical cell ID and the associated pseudo-random sequence that is transmitted over the downlink reference signals. Once the physical cell ID and the associated pseudo-random sequence is known to the mobile, the cell is recognized by the mobile based on the received reference signals. Channel quality measurements are also made on the reference signals. Because the cell search and selection depend on the physical cell IDs of the cells, these must be intelligently allocated to cells in order to avoid unnecessary problems in cell recognition and selection. You can assign physical cell IDs manually or automatically to any cell in the network. Once allocation is completed, you can audit the physical cell IDs, view physical cell ID reuse on the map, and make an analysis of physical cell ID distribution. The procedure for planning physical cell IDs for an LTE project is: Allocating physical cell IDs "Automatically Allocating Physical Cell IDs to LTE Cells" on page 1239. "Allocating Physical Cell IDs to LTE Cells Manually" on page 1240.

"Checking the Consistency of the Physical Cell ID Plan" on page 1241. Displaying the allocation of physical cell IDs "Using the Search Tool to Display Physical Cell ID Allocation" on page 1241. "Displaying Physical Cell ID Allocation Using Transmitter Display Settings" on page 1242. "Grouping Transmitters by Physical Cell ID" on page 1242. "Displaying the Physical Cell ID Allocation Histogram" on page 1243.

11.2.11.1

Allocating Physical Cell IDs

Atoll can automatically assign physical cell IDs to the cells of an LTE network according to set parameters. For example, it takes into account the selected SSS allocation strategy (free or same per site), minimum reuse distance, and any constraints imposed by neighbours. You can also allocate physical cell IDs manually to the cells of an LTE network. In this section, the following methods of allocating physical cell IDs are described: "Automatically Allocating Physical Cell IDs to LTE Cells" on page 1239. "Allocating Physical Cell IDs to LTE Cells Manually" on page 1240.

Automatically Allocating Physical Cell IDs to LTE Cells

Atoll enables you to automatically allocate physical cell IDs to cells in the current network.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1239

Atoll User Manual To automatically allocate physical cell IDs: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Physical Cell IDs > Automatic Allocation. The Physical Cell ID Allocation dialogue appears. 4. If you have access to the LTE AFP module, under Allocate, select Physical Cell IDs to allocate physical cell IDs to cells automatically. 5. Select the ID Allocation Range. You can choose to allocate physical cell IDs from the Entire (0-503) range or you can choose Custom and enter the Excluded IDs 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 index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5"). 6. Under SSS ID Allocation Strategy, you can select one of the following automatic allocation strategies (for more information, see the Technical Reference Guide): Free: The physical cell ID allocation will only be restricted by the PSS ID allocated to nearby cells. SSS IDs will not necessarily be the same for all the cells of a site. Same per Site: This strategy allocates physical cell IDs to cells such that the same SSS ID is assigned to all the cells of a site.

7. Under Relations, you can set the relations to take into account in automatic allocation. If you have access to the LTE AFP module, under Interference Matrices, you can calculate and take interference matrices into account for the physical cell ID allocation. When the Physical Cell ID Allocation dialogue opens, the Take into account check box is disabled because interference matrices are not yet available. For more information on defining and calculating interference matrices for automatic allocation, see "Using Interference Matrices with the AFP" on page 1237. Take neighbours into account: Select this check box if you want Atoll to take neighbour relations into account for the allocation. During physical cell ID allocation, Atoll will try to allocate different physical cell IDs to a cell and all of its neighbours. This means that in an ideal situation, none of a cells neighbours should have the same physical cell ID as the cell, and no two neighbours of the cell should have the same physical cell ID either. Atoll can only take neighbour relations into account if neighbours have already been allocated. For information on allocating neighbours, see "Planning Neighbours" on page 1225. Take min reuse distance into account: Select this check box if you want Atoll to take relations based on distance into account for the allocation. You can enter the Default radius within which two cells whose channels have a co-channel overlap cannot have the same physical cell ID. Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue or in the Cells table). If defined, a cell-specific reuse distance will be used instead of default the value entered here.

8. Under Results, Atoll displays the Total Cost of the current physical cell ID allocation taking into account the parameters set in step 7. You can modify the parameters and click Recalculate Cost to see the change in the total cost. 9. Click Calculate. Atoll begins the process of allocating physical cell IDs. Once Atoll has finished allocating physical cell IDs, the IDs are visible under Results. The Results table contains the following information. Site: The name of the base station. Transmitter: The name of the transmitter. Name: The name of the cell. Initial Physical Cell ID: The physical cell ID of the cell before automatic allocation. Physical Cell ID: The physical cell ID of the cell after automatic allocation. Initial PSS ID: The PSS ID of the cell before automatic allocation. PSS ID: The PSS ID of the cell after automatic allocation. Initial SSS ID: The SSS ID of the cell before automatic allocation. SSS ID: The SSS ID of the cell after automatic allocation. Cost: The cost of the new physicel cell ID allocation of the cell. Physical Cell ID Status: The value of the Physical Cell ID Status of the cell.

10. Click Commit. The physical cell IDs are committed to the cells.

Allocating Physical Cell IDs to LTE Cells Manually

When you allocate physical cell IDs to a large number of cells, it is easiest to let Atoll allocate physical cell IDs automatically, as described in "Automatically Allocating Physical Cell IDs to LTE Cells" on page 1239. 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.

1240

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks To allocate a physical cell ID to an LTE cell manually: 1. On the map, 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 dialogue appears. 3. Select the Cells tab. 4. Enter a Physical Cell ID in the cells column. 5. You can set the Physical Cell ID Status to Locked if you want to lock the physical cell ID that you assigned. 6. Click OK.

11.2.11.2

Checking the Consistency of the Physical Cell ID Plan

Once you have completed allocating physical cell IDs, you can verify whether the allocated physical cell IDs respect the specified constraints and relations by performing an audit of the plan. The physical cell ID audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Physical Cell IDs > Audit. The Physical Cell ID Audit dialogue appears. 4. In the Physical Cell ID Audit dialogue, select the allocation criteria that you want to verify: Distance: If you select the Distance check box and set a reuse distance, Atoll will check for and list cells that do not respect this reuse distance. Neighbours: If you select the Neighbours check box, Atoll will check that no cell has the same physical cell ID as any of its neighbours, and that no two neighbours of a cell have the same physical cell ID. The report will list any cell that does have the same physical cell ID as one of its neighbours. Same SSS ID at a Site: If you select the Same SSS ID at a Site check box, Atoll will check for and list base stations that do not match the criterion, i.e., base stations whose cells have physical cell IDs that correspond to different SSS IDs.

5. Click OK. Atoll displays the results of the audit in a text file called IDCheck.txt, which it opens at the end of the audit. For each selected criterion, Atoll gives the number of detected inconsistencies and details for each inconsistency.

11.2.11.3

Displaying the Allocation of Physical Cell IDs

Once you have completed allocating physical cell IDs, you can verify several aspects of physical cell ID allocation. You can display physical cell IDs in several ways: "Using the Search Tool to Display Physical Cell ID Allocation" on page 1241. "Displaying Physical Cell ID Allocation Using Transmitter Display Settings" on page 1242. "Grouping Transmitters by Physical Cell ID" on page 1242. "Displaying the Physical Cell ID Allocation Histogram" on page 1243.

Using the Search Tool to Display Physical Cell ID Allocation

In Atoll, you can search for physical cell IDs, PSS IDs, and SSS IDs using the Search Tool. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Physical cell IDs 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 1198. To find a physical cell ID using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Physical Cell ID tab. 3. Select Physical Cell ID. 4. Enter a Physical Cell ID. 5. Click Search. Transmitters whose cells use the entered physical cell ID are displayed in red. Transmitters with cells that use other physical cell IDs are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window. Note: 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 "Defining the Object Type Label" on page 35.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1241

Atoll User Manual To find a PSS ID using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Physical Cell ID tab. 3. Select PSS ID. 4. Select the PSS ID to search for, i.e., All, 0, 1, or 2. 5. Click Search. 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. Note: Transmitters with more than one cell may use different PSS IDs in different cells. Therefore, the search for all PSS IDs is only valid for single-cell transmitters.

To restore the initial transmitter colours, click the Reset Display button in the Search Tool window. To find an SSS ID using the Search Tool: 1. Click View > Search Tool. The Search Tool window appears. 2. Select the Physical Cell ID tab. 3. Select SSS ID. 4. Enter an SSS ID. 5. Click Search. Transmitters whose cells use the entered SSS ID are displayed in red. Transmitters with cells that use other SSS IDs are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.

Displaying Physical Cell ID Allocation Using Transmitter Display Settings

You can display physical cell ID allocation on transmitters by using the transmitters display characteristics. To display physical cell ID allocation on the map: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete Values" as the Display Type and "Cells: Physical Cell ID" as the Field. 6. Click OK. Transmitters will be displayed by physical cell ID. You can also display the physical cell ID in the transmitter label or tooltip by selecting "Cells: Physical Cell ID" from the Label or Tip Text Field Definition dialogue. For information on display options, see "Display Properties of Objects" on page 32.

Grouping Transmitters by Physical Cell ID

You can group transmitters on the Data tab of the Explorer window by their physical cell ID or their reuse distance. To group transmitters by physical cell ID: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: Physical Cell ID Min Reuse Distance Physical Cell ID Status

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.

1242

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 8. 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 the transmitters will be grouped. . The selected parameter is removed from the list of parameters on which

9. 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 b. Select a parameter and click to move it up to the desired position. to move it down to the desired position.

10. Click OK to save your changes and close the Group dialogue.

Displaying the Physical Cell ID Allocation Histogram

You can use a histogram to analyse the use of allocated physical cell IDs in a network. The histogram represents the physical cell IDs as a function of the frequency of their use. To display the physical cell ID histogram: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Physical Cell IDs > ID Distribution. The Distribution Histograms dialogue appears. Each bar represents a physical cell ID, its height depending on the frequency of its use. 4. Move the pointer over the histogram to display the frequency of use of each physical cell ID. The results are highlighted simultaneously in the Detailed Results list.

11.3

Studying Network Capacity

Interference is the major limiting factor in the performance of LTE networks. It has been recognized as the major bottleneck in network capacity and is often responsible for poor performance. Frequency reuse means that in a given coverage area there are several cells that use a given set of frequencies. The cells that use the same frequency are called co-channel cells, and the interference from users with the same channel in the other co-channel cells is called co-channel interference. Unlike thermal noise which can be overcome by increasing the signal-to-noise ratio (SNR), co-channel interference cannot be countered by simply 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 minimized 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, 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 or subscriber lists must be provided. Once services and users have been modelled and traffic maps and subscriber lists have been created, you can make simulations of the network traffic. In this section, the following are explained: "Defining Multi-service Traffic Data" on page 1243. "Creating a Traffic Map" on page 1244. "Exporting a Traffic Map" on page 1252. "Working with a Subscriber Database" on page 1253. "Calculating and Displaying Traffic Simulations" on page 1256. "Making Coverage Predictions Using Simulation Results" on page 1269.

11.3.1

Defining Multi-service Traffic Data

The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: 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 1344.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1243

Atoll User Manual Services: Services are the various services, such as VoIP, FTP download, etc., 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 1210. Mobility type: 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 1211. 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 1211.

11.3.2

Creating a Traffic Map

The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for LTE projects. Sector traffic map User profile traffic map User density traffic map (number of users per km2)

These maps can be used for 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 . For more information, see "Creating a Sector Traffic Map" on page 1244. User profile traffic maps can be used if you have marketing-based traffic data. User profile traffic maps, where each vector (polygon, line, or point) describes subscriber densities (or numbers of subscribers for points) with user profiles and mobility types, and user profile environment based traffic maps, where each pixel has an assigned environment class. For more information, see "Importing a User Profile Traffic Map" on page 1247, "Importing a User Profile Environment Based Traffic Map" on page 1248 and "Creating a User Profile Environment Based Traffic Map" on page 1249. User density traffic maps (number of users per km2) can be used if you have population-based traffic data, or 2G network statistics. Each pixel has a user density assigned. For more information, see "Creating User Density Traffic Maps (No. Users/km2)" on page 1250, "Importing a User Density Traffic Map" on page 1250, "Converting 2G Network Traffic" on page 1252 and "Exporting Cumulated Traffic" on page 1252

11.3.2.1

Creating a Sector Traffic Map

This section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the uplink and in the downlink or the number of users per activity status . A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 1198. To create a sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector Traffic Map. 5. Select the type of traffic information you want to input. You can choose between Throughputs in Uplink and Downlink or Number of Users per Activity Status. 6. Click the Create button. The Sector Traffic Map dialogue appears. Note: 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 another Atoll document.

7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 8. Enter the data required in the Map per Sector dialogue: If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and downlink for each sector and for each listed service. If you have selected Number of Users per Activity Status, enter the number of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each service.

1244

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Note:

You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 63.

9. Click OK. The Sector Traffic Map Properties dialogue appears. 10. Select the Traffic tab. Enter the following: a. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. b. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. c. Under Clutter Distribution, for each clutter class, enter: A weight to spread the traffic over the vector. The percentage of indoor users. An additional loss will be counted for indoor users during Monte-Carlo simulations.

11. 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 the sector traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 5. Select the Traffic tab. 6. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 7. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 8. Under Clutter Distribution, for each clutter class, enter a weight to spread the traffic over the clutter classes and the percentage of indoor users. 9. Click OK. Atoll saves the traffic map with its modifed values. You can update the information, throughput demands and the number of users, on the map afterwards. You can update Sector traffic maps. You must first recalculate the coverage prediction by transmitter. For more information, see "Making a Coverage Prediction by Transmitter" on page 1198. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map that you want to update. The context menu appears. 4. Select Update from the context menu. The Sector Traffic Map dialogue appears. 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. 5. Click OK. The Sector Traffic Map Properties dialogue appears. 6. 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 1251.

11.3.2.2

Creating a User Profile Traffic Map

The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There may also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments. A user profile models the behaviour of different user categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for calls of the type "voice") or uplink and downlink volume (for calls of the type "data"). Environment classes are used to describe the distribution of users 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 users with the same profile per km).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1245

Atoll User Manual The sections "Importing a User Profile Traffic Map" on page 1247, "Importing a User Profile Environment Based Traffic Map" on page 1248 and "Creating a User Profile Environment Based Traffic Map" on page 1249 describe how to use traffic data from the marketing department in Atoll to model traffic. In this section, the following are explained: "Modelling User Profiles" on page 1246. "Modelling Environments" on page 1246.

Modelling User Profiles

You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user may be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the LTE Parameters folder.

3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. Note: 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.

5. You can modify the following parameters: Name: Enter a descriptive name for the user profile. Service: Select a service from the list. For information on services, see "Modelling Services" on page 1210. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 1211. Calls/Hour: For services of the type "voice," enter the average number of calls per hour for the service. The calls per hour is used to calculate the activity probability. For services of the type "voice," one call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each. For services of the type "data," 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 services of the type "data," however, he may 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 may be downloading web pages and other times he may not be using the application, or he may be browsing local files, but the session is still considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time. Note: 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 (sec.): For services of the type "voice," enter the average duration of a call in seconds. For services of the type "data," this field is left blank. UL Volume (KBytes): For services of the type "data," enter the average uplink volume per session in kilobytes. DL Volume (KBytes): For services of the type "data," enter the average downlink volume per session in kilobytes.

6. Click OK.

Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of users with the same profile per km). To get an appropriate user distribution, you can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers for each clutter class. In a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss. To create or modify an LTE environment: 1. Click the Data tab of the Explorer window. 2. Click the Expand button ( ) to expand the LTE Parameters folder.

3. Right-click the Environments folder. The context menu appears. 4. Select New from the context menu. The Environments New Element Properties dialogue appears.

1246

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Note:

You can modify the properties of an existing environment by right-clicking the environment in the Environments folder and selecting Properties from the context menu.

5. Click the General tab. 6. Enter a Name for the new LTE environment. 7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility combination that this LTE environment will describe: User: Select a user profile. Mobility: Select a mobility type. Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination of user profile and mobility type.

8. Click the Clutter Weighting tab. 9. For each clutter class, enter a weight that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

For example: An area of 10 km with a user density of 100/km. Therefore, in this area, there are 1000 users. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in the Building clutter class. 10. If you wish you can specify a percentage of indoor users for each clutter class. During a Monte Carlo simulation, an additional loss will be added to the indoor users path loss. 11. Click OK.

11.3.2.2.1

Importing a User Profile Traffic Map

User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscriberskm, or polygons with a number of subscriberskm) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Densities from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1249.

7. Select the file to import. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab (see Figure 11.689). 12. Under Traffic Fields, you can specify the user profiles to be considered, their mobility type (kmh), and their density. If the file you are importing has this data, you can define the traffic characteristics by identifying the corresponding fields in the file. If the file you are importing does not have data describing the user profile, mobility, or density, you can assign values. When you assign values, they apply to the entire map.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1247

Atoll User Manual

Figure 11.689: Traffic map properties dialogue - Traffic tab Define each of the following: User Profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the LTE Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the LTE Parameters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines, and the number of subscribers when the map consists of points. Important: 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 LTE Parameters folder of the Data tab. If the imported user profile or mobility does not match, Atoll will display a warning. 13. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution. The user distribution is calculated using the following equation: Wk Sk N k = N Area ------------------------Wi Si

where: Nk Wk Sk = Number of users in the clutter k Number of users in the zone Area Weight of clutter k Surface area of clutter k (in square km)

N Area = = =

14. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss will be added to the indoor users path loss. 15. Click OK to finish importing the traffic map.

11.3.2.2.2

Importing a User Profile Environment Based Traffic Map

Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map.

1248

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 5. Select User Profile Environments from the list. 6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1249.

7. Select the file to import. The file must be in one of the following supported 8 bit raster formats: TIF, JPEG 2000, BIL, IST, BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Description tab. In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the Code column. 12. For each Code, select the environment it corresponds to from the Name column. The environments available are those available in the Environments folder, under LTE Parameters on the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 1246. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 32. 14. Click OK.

11.3.2.2.3

Creating a User Profile Environment Based Traffic Map

Atoll enables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 11.690).

Draw Map

Delete Map

Figure 11.690: Environment Map Editor toolbar 7. Select the environment class from the list of available environment classes. 8. Click the Draw Polygon button ( 9. Click the Delete Polygon button ( ) to draw the polygon on the map for the selected environment class. ) and click the polygon to delete the environment class polygon on the map.

10. Click the Close button to close the Environment Map Editor toolbar and end editing.

11.3.2.2.4

Displaying Statistics on a User Profile Environment Traffic Map

You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1249

Atoll User Manual The Statistics window lists the surface (Si in km) and the percentage of surface (% of i) for each environment Si class "i" within the focus zone. The percentage of surface is given by: % of i = ------------- 100 Sk

You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.

11.3.2.3

Creating User Density Traffic Maps (No. Users/km2)

User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. In this section, the following ways of creating a user density traffic map are explained: "Importing a User Density Traffic Map" on page 1250 "Creating a User Density Traffic Map" on page 1251.

User density traffic maps may be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. for more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 1251.

11.3.2.3.1

Importing a User Density Traffic Map

The user density traffic map defines the density of users per pixel. For a traffic density of X users per km, Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic maps properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (No. Users/km2). 5. Select the type of traffic information you input: Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity.

6. Click the Import button. The Open dialogue appears. Note: You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1249.

7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP, PlaNET, TIF, JPEG 2000, ISTAR, and Erdas Imagine. 8. Click Open. The File Import dialogue appears. 9. Select Traffic from the Data Type list. 10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears. 11. Select the Traffic tab. 12. Select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink. 13. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. 14. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 15. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.

1250

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks An additional loss will be counted for indoor users during the Monte Carlo simulations. You do not have to define a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel. 17. Click OK. Atoll creates the traffic map in the Traffic folder.

11.3.2.3.2

Creating a User Density Traffic Map

Atollenables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (Number of users per km2). 5. Select the type of traffic information you input. You can choose between: Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity.

6. Click the Create button. The traffic maps property dialogue appears. 7. Select the Traffic tab. 8. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must equal 100. 9. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 10. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 11. Under Clutter Distribution, enter for each clutter class the percentage of indoor users. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for user density traffic maps because the traffic is provided in terms of user density per pixel. 12. Click OK. Atoll creates the traffic map in the Traffic folder. 13. Right-click the traffic map. The context menu appears. 14. Select Edit from the context menu. 15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit contours, see "Editing Polygons, Lines, and Points" on page 46. Atoll creates an item called Density values in the User Density Map folder. 16. Right-click the item. The context menu appears. 17. Select Open Table from the context menu. 18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn. 19. Right-click the item. The context menu appears. 20. Select Edit from the context menu to end editing.

11.3.2.3.3

Creating User Density Traffic Maps from Sector Traffic Maps

You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps 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. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the sector traffic map from which you want to create user density traffic maps. The context menu appears. 4. Select Create density maps from the context menu. Atoll creates as many user density traffic maps as the number of services present in the sector traffic map. The user density map files use the resolution of the coverage prediction used for the sector traffic map and are embedded in the document.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1251

Atoll User Manual

11.3.2.4

Converting 2G Network Traffic

Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as traffic maps per user density into your LTE document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 1252, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1250. To import a 2G traffic map into an LTE document: 1. Create a live data traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 254. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 1252. 3. Import the traffic exported in step 2 to your LTE document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1250.

11.3.2.5

Exporting Cumulated Traffic

Atoll allows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts a user density traffic map. The cumulated traffic is exported in 32-bit BIL, ArcView Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Click the Geo tab of the Explorer window. 2. Right-click the Traffic folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: The Entire Project Area: This option allows you to export the cumulated traffic over the entire project. The Computation Zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone.

7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains at "0" and no data will be exported. 8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic data to be exported. Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal. Service: Select the service that will be exported, or select "Voice services" to export voice traffic, or select "Data services" to export data traffic. Mobility: Select the mobility type that will be exported or select "All" to export all mobility types. Activity: Select one of the following: All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status. Uplink: Select Uplink to export mobiles active in the uplink only. Downlink: Select Downlink to export mobiles active in the downlink only. Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.

9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the cumulated traffic. 10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.

11.3.3

Exporting a Traffic Map

To export a traffic map: 1. Click the Geo tab of the Explorer window. 2. Click the Expand button ( ) to expand the Traffic folder.

3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save.

1252

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks If you are exporting a raster traffic map, you have to define: The Export Region: Entire Project Area: Saves the entire traffic map. Only Pending Changes: Saves only the modifications made to the map. Computation Zone: Saves only the part of the traffic map inside the computation zone.

An export Resolution.

11.3.4

Working with a Subscriber Database

The LTE module includes a subscriber database for modelling fixed user distributions in a network. The subscriber database consists of subscriber lists. You can create subscriber lists in Atoll by adding subscribers to the list using the mouse, or by copying data from any other source such as a spreadsheet. You can also directly import subscriber lists in Atoll from text (TXT) and comma separated value (CSV) files. Atoll can allocate reference or serving base stations (cells) to subscribers. You can also have the subscriber antenna oriented towards its serving cell to decrease interference. The automatic server allocation performs a number of calculations on the subscriber locations. In this section, the following are explained: "Creating a Subscriber List" on page 1253. "Performing Calculations on Subscriber lists" on page 1256.

11.3.4.1

Creating a Subscriber List

You create subscribers in Atoll in two steps. First, you create a subscriber list, and then you add subscribers to the list. You can add subscribers to the list directly on the map using the mouse. For more information, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1255. If you need to create a large number of subscribers, Atoll allows you to import them from another Atoll document or from an external source. For more information, see "Importing a Subscriber List" on page 1255. To create a subscriber list: 1. Click the Data tab in the Explorer window. 2. Right-click the Subscribers folder. The context menu appears. 3. Select New List from the context menu. The Subscriber List N Properties dialogue appears (see Figure 11.691), where N is an incremental digit.

Figure 11.691: New subscriber list dialogue - General tab 4. Select the General tab. The following options are available: Name: The name of the subscriber list. You can change the name of the list if desired. Coordinate System: The current coordinate system used by the subscriber list. You can change the coordinate system of the list by clicking the Change button. Sort: Click the Sort button to sort the data in the subscriber list. For information on sorting, see "Sorting Data" on page 73. Filter: Click the Filter button to filter the data in the subscriber list. For information on filtering, see "Filtering Data" on page 74.

5. Click the Display tab. You can modify how subscribers added to the list are displayed. For information on defining the display properties, see "Display Properties of Objects" on page 32. 6. Click OK. Atoll creates a new subscriber list. The following parameters are available by default in a new subscriber list:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1253

Atoll User Manual ID: The subscriber ID in the subscriber list. It is an automatically created identification number. X and Y coordinates: The geographical coordinates of the subscriber. A subscribers location is always fixed. Height: The altitude of the subscriber antenna with respect to the ground (DTM). Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose contents are automatically updated. Name: You can assign a descriptive name to each subscriber. User Profile: A user profile defines the traffic demand characteristics of subscribers. Atoll determines the terminal used, the service accessed, and the activity status of subscribers during Monte Carlo simulations according to the information in the user profiles. For more information, see "Modelling User Profiles" on page 1246. Terminal: The default terminal is the user equipment with an antenna, LTE equipment, and noise characteristics. The properties of this terminal are taken into consideration when performing calculations on the subscriber list. Service: The service that the subscriber accesses by default. The properties of this service are taken into consideration when performing calculations on the subscriber list. Mobility: The mobility type associated with the subscriber. It is used to identify the thresholds and graphs to be used for the subscriber in calculations. Indoor: This field indicates whether the subscriber is indoor or outdoor. Azimuth: The orientation of the subscriber antenna in the horizontal plane. Azimuth is always considered with respect to the north. You can either define this value manually or let Atoll calculate it for the subscriber. Atoll points the subscriber antenna towards its serving base station. Mechanical Downtilt: The orientation of the subscriber antenna in the vertical plane. Mechanical downtilt is positive when it is downwards and negative when upwards. You can either define this value manually or let Atoll calculate it for the subscriber. Atoll points the subscriber antenna towards its serving base station. Lock Status: You can choose to lock the subscriber antenna orientation and serving transmitter. Use this option if you do not want Atoll to change the assigned server or the antenna orientation. Serving Base Station: The serving transmitter of the subscriber. You can either define this value manually or let Atoll calculate it for the subscriber. The serving base station is determined according to the received reference signal level from the cell with the highest reference signal power. Reference Cell: The reference cell of the serving transmitter of the subscriber. You can either define this value manually or let Atoll calculate it for the subscriber. If more than one cell of the serving base station cover the subscriber, the one with the lowest layer is selected as the reference cell. Path Loss (dB): The path loss calculated for the subscriber. Distance: The distance of the subscriber from its serving base station. This is a non-editable field whose contents are automatically updated. Received Reference Signal Power (DL) (dBm): The reference signal level received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. Received SS Power (DL) (dBm): The SS signal level received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. Received PDSCH Power (DL) (dBm): The PDSCH signal level received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. 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. This value is generated by Atoll during the calculations on subscriber lists. PDSCH & PDCCH Total Noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location in the downlink on the PDSCH and PDCCH. This value is generated by Atoll during the calculations on subscriber lists. Reference Signal C/(I+N) (DL) (dB): The reference signal C/(I+N) at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. SS C/(I+N) (DL) (dB): The SS C/(I+N) at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. PDSCH C/(I+N) (DL) (dB): The PDSCH C/(I+N) at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Bearer (DL): The highest LTE bearer available for the PDSCH C/(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. BLER (DL): The Block Error Rate read from the subscribers terminal types LTE equipment for the PDSCH C(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Diversity Mode (DL): The diversity mode supported by the cell or permutation zone in downlink. Peak RLC Channel Throughput (DL) (kbps): The maximum RLC channel throughput attainable using the highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Effective RLC Channel Throughput (DL) (kbps): The effective RLC channel throughput attainable using the highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. Received PUSCH & PUCCH Power (UL) (dBm): The PUSCH & PUCCH signal level received at the serving transmitter from the subscriber terminal in the uplink. This value is generated by Atoll during the calculations on subscriber lists. 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. This value is generated by Atoll during the calculations on subscriber lists. PUSCH & PUCCH C/(I+N) (UL) (dB): The PUSCH & PUCCH C/(I+N) at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.

1254

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 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. This value is generated by Atoll during the calculations on subscriber lists. BLER (UL): The Block Error Rate read from the reference cells LTE equipment for the PUSCH & PUCCH C/ (I+N) level at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists. Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink. Transmission Power (UL) (dBm): The transmission power of the subscribers terminal after power control in the uplink. This value is generated by Atoll during the calculations on subscriber lists. Allocated Bandwidth (UL) (No. of Frequency Blocks): The number of frequency blocks allocated to the subscriber in the uplink by the eNode-B. This value is generated by Atoll during the calculations on subscriber lists. Peak RLC Channel Throughput (UL) (kbps): The maximum RLC channel throughput attainable using the highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists. Effective RLC Channel Throughput (UL) (kbps): The effective RLC channel throughput available using the highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.

For information on how to select the columns to display in the subscriber list table, see "Selecting the Columns to Display in the Subscriber Lists" on page 1256. For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations on Subscriber lists" on page 1256. You can now move the pointer over the map and click once to place a new subscriber at the location of the pointer. Press ESC or click the normal pointer button ( ), to finish adding subscribers on the map. For information on adding subscribers to a list, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1255. You can open the subscriber list table containing all the subscribers and their parameters. To open the subscriber list table: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Subscribers folder.

3. Right-click the subscriber list you want to open. The context menu appears. 4. Select Open Table from the context menu. For information on working with data tables, see "Working with Data Tables" on page 53.

11.3.4.1.1

Adding Subscribers to a Subscriber List Using the Mouse

You can use the mouse to add subscribers to an existing subscriber list. Atoll applies the default parameters defined in the Table tab of the subscriber list Properties dialogue to all the subscribers you add to the list. For more information on the Table tab, see "Creating a Subscriber List" on page 1253. To add subscribers to a subscriber list using the mouse: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Subscribers folder.

3. Right-click the subscriber list to which you want to add subscribers. The context menu appears. 4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode ( 5. Move the mouse over the Map window, and click once to add each subscriber. 6. Press ESC or click the normal pointer button ( ) to finish adding subscribers. ).

Tip:

To place subscribers more accurately, before clicking the map, you can zoom in on the map. For information on using the zooming tools, see "Changing the Map Scale" on page 38.

11.3.4.1.2

Importing a Subscriber List

You can also import subscriber lists from text files (TXT) or comma separated value files (CSV), including Microsoft Excel files exported in CSV format. To import a subscriber list: 1. Click the Data tab in the Explorer window. 2. Right-click the Subscribers folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the ASCII text file you want to open and click Open. The Import dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1255

Atoll User Manual In the Import dialogue, you can change the reference coordinate system for the file being imported by selecting the system from the Coordinates list. Atoll will convert the coordinates of the list to the coordinate system of the document upon import. For more information on importing table data, see "Importing Tables from Text Files" on page 63. Note: You can also export subscriber lists. For information on exporting table data, see "Exporting Tables to Text Files" on page 61.

11.3.4.1.3

Selecting the Columns to Display in the Subscriber Lists

From the columns listed in "Creating a Subscriber List" on page 1253, you can select the ones to display in the Properties dialogue of the Subscribers folder. To select the columns to display in subscriber lists: 1. Click the Data tab in the Explorer window. 2. Right-click the Subscribers folder. The context menu appears. 3. Select Properties from the context menu. The Subscribers Properties dialogue appears. 4. Click the Column Selection tab. 5. Under Configuration, you can Open an existing configuration of the columns to display, Save the current settings in an exsting configuration file, or Save as a new configuration file. 6. Select the columns you want to display: a. To display a column, select the column in the Available Columns list and click Columns to Display list. b. To hide a column, select the column in the Columns to Display list and click c. To change the order of the columns, select a column and click 7. Click OK to close the Subscribers Properties dialogue. or . to move it to the

to move it up or down in the list.

11.3.4.2

Performing Calculations on Subscriber lists

You can perform calculations on subscriber lists without having to carry out simulations first. Atoll does not base calculations performed on subscriber lists on the path loss matrices calculated for transmitters. This is because the path loss matrices are calculated for a given receiver height (1.5 m by default) defined in the Properties dialogue of the Predictions folder, but each subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates the path loss, received power, and other output for each subscriber when you perform calculations based on subscribers. Atoll includes an Automatic Server Allocation feature which performs the following for all the subscribers in a list. To perform calculations on a subscriber list: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Subscribers folder.

3. Right-click the subscriber list on which you want to perform calculations. The context menu appears. 4. Select Calculations > Automatic Server Allocation from the context menu. The Automatic Server Allocation dialogue appears. If you want the calculations 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 for signal level calculations is based on the model standard deviation, and the shadowing margin for C/(I+N) calculations is based on the C/I standard deviation. 5. Click Calculate. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. 6. Once the calculations are finished, click Close to close the Event Viewer. 7. Click Commit to store the results in the subscriber list. For the list of results that are available after the calculations, see "Creating a Subscriber List" on page 1253.

11.3.5

Calculating and Displaying Traffic Simulations

To plan and optimise LTE networks, you will need to study the network capacity and to study the network coverage taking into account realistic user distribution and traffic demand scenarios. In Atoll, a simulation corresponds to a given distribution of LTE users. It is a snapshot of an LTE 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 networks response to different traffic demands. Each user distribution

1256

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks (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. LTE 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. LTE 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: "LTE Traffic Simulation Algorithm" on page 1257. "Creating Simulations" on page 1258. "Displaying the Traffic Distribution on the Map" on page 1259. "Displaying the Results of a Single Simulation" on page 1263. "Updating Cell Load Values With Simulation Results" on page 1268. "Estimating a Traffic Increase" on page 1269.

11.3.5.1

LTE Traffic Simulation Algorithm

Figure 11.692 shows the LTE simulation algorithm. The simulation process in LTE consists of the following steps: 1. Mobile Generation and Distribution Simulations require traffic data, such as traffic maps (raster, vector, or live traffic data) or subscriber lists. Atoll generates a user distribution for each simulation using a Monte Carlo algorithm. This user distribution is based on the traffic data input and is weighted by a Poisson distribution. 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. The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the subscriber locations.

Figure 11.692: LTE simulation algorithm 2. Best Server Determination Atoll determines the best server for each mobile based on the reference signal level in the downlink. The best serving transmitter is determined according to the received reference signal level from the cell with the highest

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1257

Atoll User Manual reference signal power. If more than one cell cover the mobile, the one with the lowest layer is selected as the serving (reference) cell. 3. Downlink Calculations The downlink calculations include the calculation of downlink reference signal, SS, PBCH, PDSCH, and PDCCH C/(I+N), determination of the best available bearer for the PDSCH C/(I+N), allocation of resources (RRM), and calculation of user throughputs. Static inter-cell interference coordination using fractional frequency reuse is performed on the downlink if the cell supports static DL ICIC. Interference calculation is based on the probabilities of collision between the fractions of the channel bandwidth used by the different cells. 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. Static inter-cell interference coordination using fractional frequency reuse is performed on the uplink if the cell supports static UL ICIC. Interference calculation is based on the probabilities of collision between the fractions of the channel bandwidth used by the different cells. 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: 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. At the end of the simulations, an active user can be connected in the direction corresponding to his activity status if: he has a best server assigned (step 2.), he has a bearer in the direction corresponding to his activity status (step 3. and step 4.), he is among the users selected by the scheduler for resource allocation (step 5.), and he is not rejected due to resource saturation (step 5.).

If a user is rejected during step 2., the cause of rejection is "No Coverage". If a user is rejected during step 3. or step 4., the cause of rejection is "No Service". If a user is rejected during step 5., the cause of rejection can either be "Scheduler Saturation," i.e., the user is not among the users selected for resource allocation, or he can be rejected due to "Resource Saturation," i.e., 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.

11.3.5.2

Creating Simulations
In Atoll, simulations enable you to study the capacity of your LTE network and model the different network regulation mechanisms, such as power control, uplink bandwidth allocation, and scheduling, in order to optimise network performance and maximise capacity. You can create one simulation or a group of simulations that will be performed in sequence. You must have at least one traffic map or subscriber list in your document to be able to perform simulations. To create a simulation or a group of simulations: 1. Click the Data tab in the Explorer window. 2. Right-click the LTE Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name for this simulation or group of simulations. 5. Under Execution on the General tab, you can set the Number of Simulations to be carried out. All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. 6. Under Load Constraints on the General tab, you can set the constraints that Atoll must respect during the simulation: 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

1258

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks use the maximum uplink traffic load as defined in the properties for each cell, click the button ( box and select Defined per Cell. 7. You can enter some Comments if you wish. 8. On the Source Traffic tab, enter the following: Global Scaling Factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). Select Traffic Maps to be Used: Select the traffic maps you want to use for the simulation. Select Subscriber Lists to be Used: Select the subscriber lists you want to use for the simulation. You can select traffic maps of any type. However, if you have several different types of traffic maps and want to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 1244. Note: When you perform simulations for subscriber lists, Atoll does not base the calculations on subscriber lists on the path loss matrices calculated for transmitters. This is because the path loss matrices are calculated for a given receiver height (1.5 m by default), but each subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates the path loss, received power, and other output, for each subscriber when you perform simulations on subscribers. ) beside the

9. On the Advanced tab, enter the following: 10. Under Generator Initialisation, enter an integer as the generator initialisation value. If you enter "0," the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value.

Tip:

Using the same generated user and shadowing error distribution for several simulations can be useful when you want to compare the results of several simulations where only one parameter changes.

11. Under Convergence, enter the following parameters: Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. 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.

12. Once you have defined the simulation, you can run it immediately or you can save it to run it later: Run: Click Run to save the defined simulation and run it immediately OK: Click OK to save the defined simulation without running it. You can run it later clicking the Calculate button ( ) on the Radio toolbar.

All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. You can now use the results from completed simulations for LTE coverage predictions. For more information on using simulation results in coverage predictions, see "Making Coverage Predictions Using Simulation Results" on page 1269.

11.3.5.3

Displaying the Traffic Distribution on the Map

Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to activity status, service, reference cell, or throughputs. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 33. In this section are the following examples of traffic distribution: "Displaying the Traffic Distribution by Activity Status" on page 1260. "Displaying the Traffic Distribution by Connection Status" on page 1260. "Displaying the Traffic Distribution by Service" on page 1261. "Displaying the Traffic Distribution by Throughput" on page 1261. "Displaying the Traffic Distribution by Uplink Transmission Power" on page 1262.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1259

Atoll User Manual

Tip:

You can make the traffic distribution easier to see by hiding geographic data and coverage predictions. For information, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.

11.3.5.3.1

Displaying the Traffic Distribution by Activity Status

In this example, the traffic distribution is displayed by the activity status. To display the traffic distribution by the activity status: 1. Click the Data tab in the Explorer window. 2. Right-click the LTE Simulations folder. The context menu appears. 3. Select Properties from the context menu. The LTE Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "Activity Status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 11.693).

Figure 11.693: Displaying the traffic distribution by activity status

11.3.5.3.2

Displaying the Traffic Distribution by Connection Status

In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Click the Data tab in the Explorer window. 2. Right-click the LTE Simulations folder. The context menu appears. 3. Select Properties from the context menu. The LTE Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "Connection Status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 11.694).

Figure 11.694: Displaying the traffic distribution by connection status

1260

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

11.3.5.3.3

Displaying the Traffic Distribution by Service

In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Click the Data tab in the Explorer window. 2. Right-click the LTE Simulations folder. The context menu appears. 3. Select Properties from the context menu. The LTE Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete Values" as the Display Type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 11.695).

Figure 11.695: Displaying the traffic distribution by service

11.3.5.3.4

Displaying the Traffic Distribution by Throughput

In this example, the traffic distribution is displayed by throughput. To display the traffic distribution by throughput: 1. Click the Data tab in the Explorer window. 2. Right-click the LTE Simulations folder. The context menu appears. 3. Select Properties from the context menu. The LTE Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value Intervals" as the Display Type and one of the following throughput types as the Field: In the downlink: - Peak RLC, effective RLC, or application channel throughput - Peak RLC, effective RLC, or application cell capacity - Peak RLC, effective RLC, or application user throughput In the uplink: - Peak RLC, effective RLC, or application channel throughput - Peak RLC, effective RLC, or application cell capacity - Peak RLC, effective RLC, or application allocated bandwidth throughput - Peak RLC, effective RLC, or application user throughput

5. Click OK. The traffic distribution is now displayed by throughput (see Figure 11.696).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1261

Atoll User Manual

Figure 11.696: Displaying the traffic distribution by throughput

11.3.5.3.5

Displaying the Traffic Distribution by Uplink Transmission Power

In this example, the traffic distribution is displayed by the uplink transmission power of the mobiles. You can analyse the effect of the uplink power control. To display the traffic distribution by uplink transmission power: 1. Click the Data tab in the Explorer window. 2. Right-click the LTE Simulations folder. The context menu appears. 3. Select Properties from the context menu. The LTE Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value Intervals" as the Display Type and "Transmission Power (UL) (dBm)" as the Field. 5. Click OK. The traffic distribution is now displayed by uplink transmission power (see Figure 11.697).

Figure 11.697: Displaying the traffic distribution by uplink transmission power

11.3.5.3.6

Displaying Traffic Simulation Results Using Tooltips

You can display information by placing the pointer over a mobile generated during a simulation to read the information displayed in the tool tips. The information displayed is defined by the settings you made on the Display tab. For information on defining the tool tips, see "Defining the Object Type Tip Text" on page 36. To display simulation results in the form of tool tips: In the map window, place the pointer over the user that you want more information on. After a brief pause, the tooltip appears with the information defined in the Display tab of the LTE Simulations folder properties (see Figure 11.698).

1262

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.698: Displaying the traffic simulation results using tool tips

11.3.5.4

Displaying the Results of a Single Simulation

After you have created a simulation, as explained in "Creating Simulations" on page 1258, you can display the results. To access the results of a single simulation: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( you want to access. ) to expand the LTE Simulations folder. ) to expand the folder of the simulation group containing the simulation whose results

4. Right-click the simulation. The context menu appears. 5. Select Properties from the context menu. The simulation properties dialogue appears. One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain simulation results as identified by the tab title. The Statistics tab: The Statistics tab contains the following sections: Request: Under Request, is 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; 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 number of iterations that were run in order to converge. 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. These data are also given per service.

Results: Under Results, is data on the connection results: -

The Sites tab: The Sites tab contains the following information per site: Peak RLC Aggregate 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 Aggregate 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. 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 RLC Aggregate 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 Aggregate 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. 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. Peak RLC Aggregate 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 Aggregate 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. 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 RLC Aggregate 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 Aggregate 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. 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.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1263

Atoll User Manual 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." Connected: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both. Connected DL+UL: The number of users connected to any cell of the site in downlink and uplink both. Connected DL: The number of users connected to any cell of the site in downlink. Connected UL: The number of users connected to any cell of the site in uplink. 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. 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: Traffic Load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation. ICIC Ratio (DL) (%): The percentage of the downlink traffic load that corresponds to the ICIC part of the frame. 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. ICIC UL Noise Rise (dB): The noise rise of the cells calculated on the uplink during the simulation for the ICIC part of the frame. MU-MIMO Capacity Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. Peak RLC Aggregate Throughput (DL) (kbps): The sum of peak RLC user throughputs of all the users connected in the downlink. Effective RLC Aggregate Throughput (DL) (kbps): The sum of effective RLC 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 RLC Aggregate Throughput (UL) (kbps): The sum of peak RLC user throughputs of all the users connected in the uplink. Effective RLC Aggregate Throughput (UL) (kbps): The sum of effective RLC 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. Peak RLC Aggregate 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 Aggregate Throughput (DL) (kbps) For Each Service: For each service, the sum of effective RLC 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 RLC Aggregate 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 Aggregate Throughput (UL) (kbps) For Each Service: For each service, the sum of effective RLC 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. 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." Connected: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Connected DL+UL: The number of users connected to the cell in downlink and uplink both. Connected DL: The number of users connected to the cell in downlink. Connected UL: The number of users connected to the cell in uplink. Connection Success Rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. 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.

1264

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 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. 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 DL, UL, or DL+UL. 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. 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. Indoor: This field indicates whether indoor losses have been added or not. Serving Base Station: The serving transmitter of the subscriber. Reference Cell: The reference cell of the serving transmitter of the subscriber. 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 serving base station. 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 serving base station. Path Loss (dB): The path loss from the best server calculated for the user. 2nd Best Server Path Loss (dB): The path loss from the second best server calculated for the user. Received Reference Signal Power (DL) (dBm): The reference signal level received at the user location in the downlink. RSRP (RS EPRE) (DL) (dBm): The RSRP, average Reference Signal Received Power per Subcarrier, at the user location in the downlink. RSSI (DL) (dBm): The RSSI, Received Signal Strength Indicator, 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 PDSCH Power (DL) (dBm): The PDSCH signal level received at the user location in the downlink. 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. PDSCH & PDCCH Total Noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location in the downlink on the PDSCH and PDCCH. Reference Signal C/(I+N) (DL) (dB): The reference signal C/(I+N) at the user location in the downlink. RSRQ (DL) (dB): The RSRQ, Reference Signal Received Quality, 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. PDSCH C/(I+N) (DL) (dB): The PDSCH C/(I+N) at the user location in the downlink. 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 LTE equipment for the PDSCH 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 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, etc.). 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, etc.). 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 reference cells LTE equipment for the PUSCH & PUCCH C/ (I+N) level at the serving transmitter of the user in the uplink.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1265

Atoll User Manual 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 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, etc.). 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, etc.). 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, etc.). It is calculated from the effective RLC throughput, the throughput scaling factor of the service and the throughput offset. Notes: In Atoll, channel throughputs are peak RLC, effective RLC, or application throughputs achieved at a given location using the highest LTE bearer with the entire channel resources. If a user is rejected, his user throughput is zero.

The Initial Conditions tab: The Initial Conditions tab contains the following information: The global transmitter parameters: The PDCCH overhead (number of symbol durations per subframe) The PUCCH overhead (average number of frequency blocks) The switching point periodicity The default cyclic prefix ratio The UL power control margin The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink traffic load convergence thresholds The uplink noise rise convergence threshold The names of the traffic maps and subscriber lists used.

The input parameters specified when creating the simulation:

The parameters related to the clutter classes, including the default values.

11.3.5.5

Displaying the Average Results of a Group of Simulations

After you have created a group of simulations, as explained in "Creating Simulations" on page 1258, you can display the average results of the group. If you wish to display the results of a single simulation in a group, see "Displaying the Results of a Single Simulation" on page 1263. To display the averaged results of a group of simulations: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the LTE Parameters folder.

3. Right-click the group of simulations whose results you want to display. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain the averaged results for all simulations of the group.

1266

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks The Statistics tab: The Statistics tab contains the following sections: Request: Under Request, is 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; 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 number of iterations that were run in order to converge. 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. These data are also given per service.

Results: Under Results, is data on the connection results: -

The Sites (Average) tab: The Sites (Average) tab contains the following information per site: Peak RLC Aggregate 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 Aggregate 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. 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 RLC Aggregate 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 Aggregate 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. 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. Peak RLC Aggregate 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 Aggregate 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. 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 RLC Aggregate 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 Aggregate 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. 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. 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." Connected: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both. Connected DL+UL: The number of users connected to any cell of the site in downlink and uplink both. Connected DL: The number of users connected to any cell of the site in downlink. Connected UL: The number of users connected to any cell of the site in uplink. 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. 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 site and transmitter: Traffic Load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation. ICIC Ratio (DL) (%): The percentage of the downlink traffic load that corresponds to the ICIC part of the frame. 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. ICIC UL Noise Rise (dB): The noise rise of the cells calculated on the uplink during the simulation for the ICIC part of the frame. MU-MIMO Capacity Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1267

Atoll User Manual Peak RLC Aggregate Throughput (DL) (kbps): The sum of peak RLC user throughputs of all the users connected in the downlink. Effective RLC Aggregate Throughput (DL) (kbps): The sum of effective RLC 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 RLC Aggregate Throughput (UL) (kbps): The sum of peak RLC user throughputs of all the users connected in the uplink. Effective RLC Aggregate Throughput (UL) (kbps): The sum of effective RLC 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. Peak RLC Aggregate 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 Aggregate Throughput (DL) (kbps) For Each Service: For each service, the sum of effective RLC 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 RLC Aggregate 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 Aggregate Throughput (UL) (kbps) For Each Service: For each service, the sum of effective RLC 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. 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." Connected: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Connected DL+UL: The number of users connected to the cell in downlink and uplink both. Connected DL: The number of users connected to the cell in downlink. Connected UL: The number of users connected to the cell in uplink. Connection Success Rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. 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: The global transmitter parameters: The PDCCH overhead (number of symbol durations per subframe) The PUCCH overhead (average number of frequency blocks) The switching point periodicity The default cyclic prefix ratio The UL power control margin The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink traffic load convergence thresholds The uplink noise rise convergence threshold The names of the traffic maps and subscriber lists used.

The input parameters specified when creating the simulation:

The parameters related to the clutter classes, including the default values.

11.3.5.6

Updating Cell Load Values With Simulation Results

After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 1258, you can update cell load values for each cell with the results calculated during the simulation. To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Click the Data tab in the Explorer window. b. Click the Expand button ( ) to expand the LTE Simulations folder.

c. Right-click the group of simulations whose results you want to access.

1268

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks d. Select Average Simulation from the context menu. A properties dialogue appears. To display the results for a single simulation: a. Click the Data tab in the Explorer window. b. Click the Expand button ( c. Click the Expand button ( sults you want to access. ) to expand the LTE Simulations folder. ) to expand the folder of the simulation group containing the simulation whose re-

d. Right-click the simulation whose results you want to access. e. Select Properties from the context menu. The simulation properties dialogue appears. 2. Click the Cells tab. 3. On the Cells tab, click Commit Results. The following values are updated for each cell: Traffic Load (DL) Traffic Load (UL) UL Noise Rise MU-MIMO Capacity Gain (UL) No. of Users (DL) No. of Users (UL) ICIC UL Noise Rise ICIC Ratio (DL)

11.3.5.7

Estimating a Traffic Increase

When you create simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increase of traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations as described in "Creating Simulations" on page 1258. 2. Click the Source Traffic tab of the properties dialogue. 3. Enter a Global Scaling Factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).

11.3.6

Making Coverage Predictions Using Simulation Results

In Atoll, you can can analyse simulation results by making coverage predictions using simulation results. In a coverage prediction each pixel is considered as a non-interfering probe user with a defined terminal, mobility, and service. The analyses can be based on a single simulation or on an averaged group of simulations. When no simulations are available, Atoll uses the downlink traffic loads and uplink noise rise values stored for each cell to make coverage predictions. For information on cell properties, see "Cell Description" on page 1176; for information on modifying cell properties, see "Creating or Modifying a Cell" on page 1179. Once you have made simulations, Atoll can use the information from the simulations instead of the defined parameters in the cell properties to make coverage predictions. For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, which uses the average of all simulations in the group. The coverage predictions that can use simulation results are: Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see "Making a Coverage by C/(I+N) Level" on page 1214. Coverage by Best Bearer: For information on making a downlink or uplink coverage by best bearer, see "Making a Coverage by Best Bearer" on page 1216. Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making a Coverage by Throughput" on page 1218. Coverage by Quality Indicator: For information on making a downlink or uplink coverage by quality indicator, see "Making a Coverage by Quality Indicator" on page 1221.

When no simulations are available, you select "(Cells Table)" from the Load Conditions list, on the Condition 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 Condition tab. 2. From the Load Conditions list, select the simulation or group of simulations on which you want to base the coverage prediction.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1269

Atoll User Manual

11.4

Optimising Network Parameters Using the ACP

Atoll Automatic Cell Planning (ACP) enables radio engineers designing LTE networks to automatically calculate the optimal network settings in terms of network coverage and capacity. Atoll ACP can also be used in co-planning projects where LTE networks must both be taken into consideration when calculating the optimal network settings. Coverage maps are used for the optimisation process, however, traffic maps can be used for weighting network load distribution. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and cell pilot power. ACP can also be used during the initial planning stage of a LTE network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP also enables you to select to select which sites can be added or removed to improve existing or new networks.

11.4.1

The ACP Module and Atoll

Atoll ACP can be used either with existing networks or with networks in the initial planning phases. With existing networks, it is most efficient to focus on tuning the parameters that can be easily changed remotely, for example: Antenna electrical tilt: ACP adjusts the electrical tilt by selecting the best antenna from the antenna group assigned to this transmitter. Total power for each cell: The total power is set within a defined minimum and maximum value for each cell.

When optimising a network that is still in the planning phase, Atoll ACP can calculate how the network can be improved by: Selecting the antenna type for each transmitter: ACP selects the best antenna from the antenna group assigned to this transmitter. Changing the antenna azimuth: ACP sets the antenna azimuth using a defined range on either side of the currently defined azimuth. Changing the mechanical tilt of the antenna: ACP sets the mechanical tilt using a defined range on either side of the currently defined mechanical tilt. Changing the height of the antenna: ACP sets the optimal antenna height using a defined range on either side of the currently defined antenna height. Selecting sites: ACP adds or removes sites that you have indicated as candidates for addition or removal in order to improve existing or new networks.

In this section, the following are explained: "Using Zones with ACP" on page 1270 "Using Traffic Maps with ACP" on page 1271 "Shadowing Margin and Indoor Coverage" on page 1271 "ACP and Antenna Masking" on page 1271.

11.4.1.1

Using Zones with ACP

ACP uses different zones during the optimisation process for different purposes. ACP uses the computation zone to define the area of the network to be optimised. ACP always takes the entire computation zone into consideration, even if the zone selected for optimisation is the focus zone; the sites and transmitters included in the computation zone and not in the focus zone are still taken into consideration when calculating signal, interference, and best server status. ACP enables you to define different targets and different weights for each zone: for the computation zone, for the focus zone, for the hot spot zones, and for each clutter classes. In this section, the following are explained: "Using the Computation Zone and the Focus Zone" on page 1270 "Using Hot Spots" on page 1270 "Using the Filtering Zone" on page 1271.

11.4.1.1.1

Using the Computation Zone and the Focus Zone

Atoll ACP optimises the settings for the sites in either the computation zone or the focus zone. If you have both a computation zone and a focus zone defined, you can select which zone will be used for the optimisation process. If there is no focus or computation zone, the ACP optimises the settings for the cells in a rectangle including all cells in the network. Atoll ACP allows you to define different targets for the computation zone and the focus zone, as well as for the hot spot zones. You can also define different weights for each zone. Note: It is recommended to define a computation zone. ACP uses the computation zone as the area in which the quality figures are calculated and improved during optimisation. Additionally, the zone defined by ACP might take into account areas outside of actual traffic boundaries.

11.4.1.1.2

Using Hot Spots

Atoll ACP also allows you to use hot spot zones, enabling you to specify different quality targets for each hot spot zone and display final results per zone. You can also define different weights for each zone. You can use the hot spot zones

1270

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks defined in the Atoll document, import ArcView SHP files to create hot spot zones, or you can create hot spot zones based on clutter classes.

11.4.1.1.3

Using the Filtering Zone

If there is a filtering zone defined, Atoll ACP will optimise all currently defined and active cells selected by the filtering zone.

Note:

ACP automatically considers all the cells that have an effect on the computation or focus zone, and ignores the rest (for example, cells that are too far away to have an impact on the selected cells). It is nonetheless recommended to use a filtering zone to speed up initial data extraction from the Atoll document.

11.4.1.2

Using Traffic Maps with ACP

Atoll ACP can use traffic maps to determine the traffic density on each pixel. The traffic density is used to weight each of the quality figures according to traffic and to put more emphasis on high traffic areas. You can apply the imported traffic density files to either or both of the quality indicators.

Figure 11.699: ACP traffic parameters Note: For the moment, traffic profiles are only used to evaluate the traffic weighting to apply to each pixel (by adding the load-scaled traffic distribution on each traffic profile). This information will also be used in the future to better manage cell load.

11.4.1.3

Shadowing Margin and Indoor Coverage

Atoll ACP enables you to take indoor coverage and a shadowing margin into consideration. When indoor coverage is taken into consideration, all pixels marked as indoors have an additional indoor loss added to total losses. The indoor loss is defined per clutter class. By default, ACP considers all pixels to be indoors, but Atoll ACP allows you to specify which clutter class should be considered as indoors and which not. When the shadowing margin is taken into consideration, the defined shadowing margin is taken into consideration in the calculation of the received useful signal power and interfering signal power. For more information on how shadowing and macro-diversity gains are calculated, see the Technical Reference Guide. Note: You can set ACP to not take macro-diversity gains into consideration by setting the appropriate option in the acp.ini file. You will need to update the corresponding parameters in the atoll.ini file as well. For information on modifying the atoll.ini file, see the Administrator Guide.

11.4.1.4

ACP and Antenna Masking

When ACP performs any type of antenna reconfiguration, it must determine how attenuation to the path loss changes when the antenna is modified. ACP determines changes to path loss attenuation using antenna masking. Depending on the propagation model used to calculate the path loss matrices, ACP supports the following antenna masking methods: Natively supported propagation models: ACP calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. Because ACP is using the same propagation model as was used to calculate the original path loss matrices, the results are consistent and accurate. For this reason, using natively supported propagation models is the preferred method. For more information, see "Natively Supported Propagation Models" on page 1272. ACPs default propagation model: If the propagation model used to calculate the original path loss matrices is not supported by ACP, ACP can use its own default propagation model. Because the ACP default propagation model is not the same as the one used to calculate the original path loss matrices, accuracy cannot be guaranteed. ACPs default propagation model is similar to Atolls Standard Propagation Model and should deliver acceptable results for any macro-type propagation model. For more information, see "ACPs Default Propagation Model" on page 1272. Precalculated path loss matrices: ACP allows you to designate all propagation models in the project which are not supported by the native method. ACP will then prerecalculated path loss matrices for these propagation models. For more information, see "Precalculated Path Loss Matrices" on page 1272.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1271

Atoll User Manual Note: Preamble power optimisation and site selection (without reconfiguration) are made independently of the method used to determine changes to path loss attenuation.

11.4.1.4.1

Natively Supported Propagation Models

During antenna optimisation, ACP must calculate how the attenuation to the path loss changes when the antenna is modified, i.e., when the antenna type, tile, or azimuth is modified. When ACP uses natively supported propagation models, it calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. The unmasking and remasking operations are strongly dependent on the propagation model that was used to calculate the path losses, especially to: Find the horizontal and vertical emission angles between a transmitter and the receiving pixel. The angles depend strongly on the radial method used to account for the height profile between the transmitter and receiver. Find the correct antenna gain for a given set of horizontal and vertical emission angles. The gain is usually based on a 3-D interpolation of the 2-D patterns and can be model-dependent.

How ACP calculates attenuation depends on the propagation model used by Atoll to generate the path loss. The propagation model parameters which affect processing are automatically extracted by ACP. ACP supports the propagation models commonly used in Atoll. For other propagation models, ACP uses a default model similar to Cost-Hata, however, you can always set ACP to use another propagation model, the SPM for example, if you feel it would give more accurate results. The raster data needed by ACP depends on the propagation model that Atoll used to generate the path loss.

Propagation Model
All Atoll Hata-based propagation models (Cost-Hata, Okumura-Hata, ITU, etc.)

Raster Data Required

DEM file DEM file Clutter Height file (optional) Clutter file (optional) DEM file

Atoll Standard Propagation Model

All other models.

Because the path loss information is not stored in the ACP optimisation setup but in the Atoll document where it is accessed by ACP, changes in the Atoll document can cause inconsistency between the optimisation results and the actual state of the network, for example, when transmitters are modified in the document. ACP deals with this situation by locking optimisation results. An optimisation can not be rerun on locked results if the path loss data are not consistent with the internal state of the optimisation. The results are automatically unlocked if the state of the Atoll document again becomes consistent with the ACP optimisation. The same mechanism applies when settings produced by an optimisation run are committed to the Atoll network. The results are locked after being committed and will be unlocked if the network is rolled back to the state on which the optimisation was based.

11.4.1.4.2

ACPs Default Propagation Model

ACP has an internal default propagation model that can be used if the propagation model used to calculate the original path loss matrices is not supported by ACP. Because the ACP default propagation model is not the same as the one used to calculate the original path loss matrices, accuracy can not be guaranteed, although it should deliver acceptable results for any macro-type propagation model. ACP offers a few parameters that enable you to improve the accuracy of the default propagation model: Use Clutter Height: By selecting Use Clutter Height, ACP will take into consideration clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on Top of Clutter: If the receiver is on top of the clutter, for example, if receivers are located on top of buildings, you can select Receiver on Top of Clutter. The receiver height will then be sum of the clutter height and the receiver height. Use Radial Method: You can select the Use Radial Method check box if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

These parameters can be set individually for each propagation model for which ACP will use the default propagation method. These parameters belong to the advanced parameters; to modify them, you must first make the advanced parameters visible. For information on making the advanced parameters visible, "Configuring the Default Settings" on page 1273.

11.4.1.4.3

Precalculated Path Loss Matrices

After the ACP setup has been created, ACP calculates the path loss matrices necessary (i.e., for sites that are being optimised and do not use natively supported propagation models or the ACP's internal model) while the optimisation is loading. ACP does not calculate all path loss matrices for all possible combinations, for example, five possible changes in electrical tilt and five possible changes in azimuth, i.e., 25 path loss matrices to be calculated. ACP only calculates the path loss matrices for the most common optmisation changes, for example, changes to the electrical tilt. By pre-calculating only the most common changes, ACP reduces the number of path loss changes to be calculated and reduces the calculation time.

1272

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks While the optimisation is running, ACP uses the pre-calculated path loss matrices. If a change is made to a transmitter that was not taken into the consideration when the path loss matrices were calculated, ACP recalculates the path loss matrix for that change only. The end result are considerable savings in both time and computer resources. For information on natively supported propagation models, see "Natively Supported Propagation Models" on page 1272. 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, it is often similar enough to a supported propagation model so that ACP can still use it. 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. Notes: Precalculated path loss matrices can only be used when optimising the antenna type and azimuth. Optimising the mechanical tilt is not currently supported.

11.4.2

Configuring the ACP Module

You can change the default settings of the Atoll ACP module so that selected options are the default settings each time you run ACP. Additionally, you can base the default ACP settings on some or all of the settings of a given Atoll optimisation. In this section, the following are explained: "Configuring the Default Settings" on page 1273 "Saving Settings to a User Configuration File" on page 1275.

11.4.2.1

Configuring the Default Settings

To configure the default settings of the ACP module: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Default Settings tab. On the Default Settings tab, you can define the configuration files that contain the default settings. These settings are applied every time you run an optimisation project. Under Loading Default Settings: Global Configuration: The Global Configuration is the configuration file set up by the administrator. This configuration provides the same default settings to everyone on the network. For information on the ACP global configuration file, see the Administrator Manual. User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings you want to be the default settings for the ACP module.

5. Click the User Preferences tab. On the User Preferences tab (see Figure 11.700), you can define settings that are saved to the acp.ini configuration file found in the ACP installation folder. These settings will be applied every time you run a new configuration.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1273

Atoll User Manual

Figure 11.700: Setting ACP user preferences Under Setup Preferences: You can define the following settings: Enable automatic setting from custom table field (antennas, sites): Select the Enable automatic setting from custom table field (antennas, sites) check box if you want ACP to use the custom columns in the SITES and ANTENNAS tables. If you want ACP to use the custom columns, you must set the appropriate options in the acp.ini file. For more information on the acp.ini file, see the Administrator Manual. Show advanced optimisation settings: Select the Show advanced optimisation settings check box if you want the ACP to display the Advanced tab when you define an optimisation setup. When the Advanced tab is available, you can set a few additional options related to services, terminals, clutter, and propagation models. Calculation setting: Adjust the slider to define whether you want ACP to provide its results more quickly, at the expense of precision, or whether you want ACP to provide more accurate results, at the expense of speed. By selecting a higher speed, you will cause ACP to reduce the number of cells monitored for each pixel, some of which might only create a bit of interference at first, but which could possibly create significantly more interference after antenna parameters are changed during the optimisation process. Selecting a higher precision avoids this problem at the expense of more time and computer resources.

Under Result Preferences: You can define the following setting for report maps: Default map transparency: Define the default map transparency with the slider.

6. Click the Private Directory tab. On the Private Directory tab (see Figure 11.701), you can define the directory to be used by the ACP to store precalculated path loss matrices as well as the path loss matrices for antenna height optimisation.

Figure 11.701: Defining the directory for path loss matrices 7. Enter the name of the directory or click the the Browse button ( 8. Click OK to save your changes. When the propagation model used is not one natively supported by ACP, for example, complex ray-tracing propagation models, ACP can use precalculated path loss matrices to calculate attenuation. For more information, see "Defining the Antenna Masking Method" on page 1275. ) to navigate to the directory.

1274

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

11.4.2.2

Defining the Antenna Masking Method

You can define how Atoll ACP calculates path loss matrices, using either Atolls propagation models, ACPs internal propagation model, or precalculated path loss matrices. These parameters will be applied to all new and duplicated setups. To define how ACP calculates path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Antenna Masking Model tab (see Figure 11.702).

Figure 11.702: The Antenna Masking Model tab 5. If you are using a propagation model that ACP does not natively support, select the Enable precalculated path loss matrices check box. You will then be able to select the propagation model for which ACP will pre-calculate path attentuation. 6. Under Propagation Models, select the check boxes in each column to define how ACP will interact with that propagation model. Not all parameters are available for all propagation models:

Tip:

By default, all available propagation models are displayed. By selecting the Show only used propagation models check box, ACP will only display the propagation models that are actually used.

Antenna masking method: The Antenna masking method indicates whether ACP can use this propagation model natively, or whether ACP uses its own default method. The information in this column can not be edited. Use precalculated path loss: Select the check box in the Use precalculated path loss column corresponding to every propagation model that is not supported natively by ACP or that can not be replaced using ACPs internal default method. Use clutter height: Select the check box in the Use clutter height column if you want ACP to take clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on top of clutter: Select the check box in the Receiver on top of clutter column if you want the receiver height to be sum of the clutter height and the receiver height. This option can be used, for example, to model receivers on top of buildings. Use radial method: Select the check box in the Use radial method column if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

7. Click OK.

11.4.2.3

Saving Settings to a User Configuration File

To save the settings to a user configuration file: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1275

Atoll User Manual 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Default Settings tab. On the Default Settings tab, you can define the configuration files that contain the default settings. These settings are applied every time you run an optimisation project. Under Loading Default Settings: Global Configuration: The Global Configuration indicates the configuration file set up by the administrator. This configuration provides the same default settings to everyone on the network. For information on the ACP global configuration file, see the Administrator Manual. User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings you want to be the default settings for the ACP module.

5. Click the Save Configuration File button under Saving Default Settings to save settings to a user configuration file. Note: The settings you save to a user configuration file are from an ACP optimisation from the current Atoll document. If you have not yet used ACP for an optimisation in the current document, the Save Configuration File button is not available.

When you click the Save Configuration File button, the Save Configuration File dialogue opens (see Figure 11.703).

Figure 11.703: The Save Configuration File dialogue 6. From the Save setting based on setup list, select the ACP setup on whose parameters you want to base the user configuration file. 7. Click the Browse button ( file. ) next to To configuration file to select where you will save the user configuration

8. Under Sections to save, select the check boxes of the types of parameters whose settings you want to save to the user configuration file. 9. Click Save.

11.4.3

Optimising Cell Planning with the ACP

Optimising cell planning with the Atoll ACP consists of defining the parameters that will be used during the optimisation process and then running the process. Each optimisation, with its parameters and results, is stored in a Setup folder in the ACP - Automatic Cell Planning folder on the Data tab of the Explorer window. In this section, the following are explained: "Creating an Optimisation Setup" on page 1276 "Defining Optimisation Parameters" on page 1277.

11.4.3.1

Creating an Optimisation Setup

In ACP, you can create an optimisation setup either by creating and running a new one, or by duplicating or opening an existing optimisation, editing the parameters, and then running it. In this section, the following are explained: "Creating a New Optimisation Setup" on page 1277 "Running an Existing Optimisation Setup" on page 1277 "Duplicating an Existing Optimisation Setup" on page 1277.

1276

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Creating a New Optimisation Setup

To create a new optimisation setup: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 1277. 4. After defining the optimisation setup: Click the Run button to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 1301. Click the Create Setup button to save the defined optimisation. For information on running the optimisation, see "Running an Existing Optimisation Setup" on page 1277.

Running an Existing Optimisation Setup

To run an existing optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

3. Right-click the optimisation you want to run. The context menu appears. Select Run from the context menu to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 1301. Select Properties from the context menu to view or modify the parameters of the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 1277.

Duplicating an Existing Optimisation Setup

To duplicate an existing optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

3. Right-click the setup you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The ACP Duplicate Options dialogue appears. 5. Under Data Synchronisation Option, select one of the following: Minimal: The duplicated ACP setup will have only the data that was changed by the ACP during optimisation. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid. Complete: The duplicated ACP setup will have have all the data from the ACP optimisation.

6. Run the existing optimisation setup as described in "Running an Existing Optimisation Setup" on page 1277.

11.4.3.2

Defining Optimisation Parameters

In Atoll ACP, when you create a new optimisation setup, you must first define all the parameters. You can also modify the parameters of an existing optimisation setup before running it. Creating a new optimisation setup is explained in "Creating a New Optimisation Setup" on page 1277. Running an existing optimisation is explained in "Running an Existing Optimisation Setup" on page 1277. The optimisation parameters are grouped onto specific tabs of the dialogue. The parameters are the same whether you create a new optimisation setup or whether you modify the parameters of an existing one. In this section, the following parameters are explained: "Setting Optimisation Parameters" on page 1277 "Setting Objective Parameters" on page 1280 "Setting Traffic Parameters for Non-uniform Traffic" on page 1283 "Setting Network Reconfiguration Parameters" on page 1284 "Defining Site Selection Parameters" on page 1290 "Defining Antenna Groups" on page 1294 "Adding Comments to the Optimisation Setup" on page 1298 "Setting Advanced Parameters" on page 1298.

11.4.3.2.1

Setting Optimisation Parameters

The Optimisation tab allows you to define the various parameters related to the optimisation algorithm. To set the optimisation parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Optimisation tab (see Figure 11.704).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1277

Atoll User Manual

Figure 11.704: The Optimisation tab 3. Define the following: Number of Iterations: Set the number of iterations for the optimisation algorithm. ACP calculates a suggested number of iterations by multiplying the total number of parameters to optimise (i.e., cell pilot power, antennas, azimuth, mechanical tilt, sites subject to selection) by two. You can accept the number of iterations, or set your own value. Often one-half or one-quarter of the suggested number is sufficient for ACP to find the optimal configuration. Resolution (m): Specify the resolution for the optimisation. Each criterion will be evaluated on each of these pixels. The total number of pixels and the average number per site is indicated. This parameter has a large influence on the accuracy and speed of the optimisation process. You should either set a resolution that is consistent with the path loss and raster data in the Atoll document, or you should set a resolution that will result in between 300 and 3000 positions per site.

4. Under Setup, you can set the following optimisation-related objectives and parameters: a. In the pane on the left-hand side, click Layers. Under Layers (see Figure 11.704 on page 1278), you can define the following for each layer to be optimised: Use: You can select which layers are to be considered in the optimisation process by selecting their check box in the Use column. The signals and interference of the transmitters and sites in the selected layers will be taken into consideration during the optimisation process. If the transmitters and sites in the selected layers are within the area to be optimised (the computation zone or the focus zone, as selected under Zones on the Optimisation tab), these transmitters and cells will be optimised. Selecting layers to be taken into consideration is most useful when you want to take the signal and interference of several layers into consideration, but only want to optimise one of the layers. Selecting the layers here ensures that ACP will take them into consideration. Transmitters and sites in layers which are not selected are treated by 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. Note: If a transmitter on one selected layer that is optimised is linked with a transmitter on another selected layer that is not optimised, the second transmitter will still appear on the Reconfiguration tab and any changes to the first transmitter will be applied to the linked transmitter as well. Name: You can change the name of the layer by clicking it and entering a new name. Weight: You can change the weight assigned to the layer during optimisation by clicking it and entering a new weight. ACP will put more emphasis on increasing the quality of the layer with the greater weight. For example, if one layer has a weight of "2" and another layer has a weight of "1," ACP will consider increasing the quality of the first layer by 1% as equivalent to increasing the quality of the second layer by 2%. Reconfiguration: If you want the layer to be taken into consideration for reconfiguration, you can select the check box in the Reconfiguration column. Site Selection: If you want the layer to be taken into consideration for site selection, you can select the check box in the Site Selection column.

1278

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks The following columns give information about the layer; they can not be edited: Technology: The technology (LTE in this case) used by the layer. Freq. Band/Carrier: The frequency band and carrier (if applicable) used by the layer. Nb Tx/Cell: The number of transmitters in the layer.

You can merge layers if you want to define identical objectives for both layers (for more information on objectives, see "Setting Objective Parameters" on page 1280). To merge layers: i. Hold CTRL and click the layers you want to merge.

ii. Click the Merge button. b. In the pane on the left-hand side, click Zones. Under Zones (see Figure 11.706), you can define how the zones will be used during optimisation. The zones are used to define geographical objectives and weighting. The zones are taken into consideration in the following order: the hot spot zones in their defined order, the focus zone, and finally the computation zone. Filtering Zones: Select the Computation Zone check box to lock sectors outside the computation zone and the Focus Zone check box to lock sectors outside the focus zone. If there is no focus zone in the project to be optimised, the computation zone is automatically selected. Hot Spots: For each new hot spot, enter a Name in the row marked with the New Row icon ( click the Browse button ( ) and ) to open the Zone Definition dialogue. You can import an ArcView SHP file

by selecting From file and clicking the the Browse button ( ). Or, you can use an existing hot spot zone in the Atoll document by selecting From hot spot and selecting the hot spot zone from the list. Or, you can create a hot spot zone composed of all areas in the reconfiguration zones that are included in one or more clutter class by selecing From clutter classes and selecting the check box corresponding to the clutter class or classes you want to study.

Figure 11.705: The Zone Definition dialogue You can change the order in which the hot spots will be taken into consideration, by clicking the layers number in the Order column and then clicking the Up button ( ) or the Down button ( ).

Figure 11.706: Configuring zones on the Optimisation tab c. In the pane on the left-hand side, click Cost Control. Under Cost Control (see Figure 11.707), you can define how the costs will be calculated for each optimisation option. ACP will use the defined costs to calculate the optimisations that are the most cost-effective. You can select three types of cost control:

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1279

Atoll User Manual No cost control: If you select No cost control, ACP will not take cost into consideration when optimising the network. Maximum cost: If you select Maximum cost, you can enter a maximum cost not to be exceeded and define the costs under Cost Setting. Quality/Cost trade-off: If you select Quality/Cost trade-off, ACP will find a compromise between cost and quality. You can use the slider to define whether ACP should put more emphasis on quality (Low) or cost (High).

Figure 11.707: Configuring costs on the Optimisation tab In the Reconfiguration Cost section, under Cost Setting, define the individual costs for each reconfiguration option. If reconfiguring an option can only be done at the physical location of the transmitter, select the check box in the Site Visit column. The cost will be increased by the defined Site Visit value. The site visit cost is incurred only once per site, independently of the number of reconfigurations that might be made to the same site, including sites supporting more than one technology. In the Site Selection Cost section, under Cost Setting, define the individual costs for each site selection option.

11.4.3.2.2

Setting Objective Parameters

The Objectives tab allows you to define the various parameters related to the objectives of the optimisation. ACP allows you to set different objectives for each layer selected in the Use column under Layers on the Optimisation tab. The objectives vary according to the technology used by the network being optimised. The options are given here. To set the objective parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Objectives tab (see Figure 11.708).

1280

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.708: The Optimisation tab 3. Under Criteria, you can set the following objective-related objectives and parameters. a. Under Objective, click RS Coverage to define the RS (i.e., the reference signal level) parameters. Computation zone: Select the check box in the Use column if you want to define a C Minimum threshold (dBm) for C coverage in the computation zone. Under Area Coverage, you can define the percentage by which the current C coverage should be improved (Improve current coverage (+-)) or a target C coverage (Target coverage (%)). Focus zone: Select the check box in the Use column if you want to define a C Minimum threshold (dBm) for C coverage in the focus zone. Hot Spot zone: Each hot spot zone defined under Zones on the Optimisation tab will appear under Name. For each hot spot zone, select the check box in the Use column if you want to define a C Minimum threshold (dBm) for C coverage in the hot spot zone.

b. Under Objective, click Parameters under RS Coverage to define how ACP will calculate the reference signal level coverage. From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate reference signal level coverage, or you can select Manual Configuration and define the settings yourself. Important: If you want to use a coverage prediction, the coverage prediction must have already been calculated. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own maps. However, if you have saved the display options of an ACP map as default, or if you are using a configuration file for ACP, these defined ranges and colours will be used as the default, overriding the settings in the selected coverage prediction. For information on setting ACP map display options as the default, see "Changing the Display Properties of ACP Maps" on page 1313. For information on saving a configuration file, see "Configuring the Default Settings" on page 1273. If you selected Manual Configuration from the Base prediction settings on list, define the following options: Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell edge coverage probability. When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied. You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced Parameters" on page 1298. Select the Use Service and Terminal check box if you want RS coverage to be calculated using a defined service and terminal and select a Service and Terminal from the lists. Select the Calculate as CN check box if you want the RS coverage to be calculated as CN and not as C.

c. Under Objective, click RS CINR to define the received signal level to interference-plus-noise ratio (RS CINR) parameters. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

1281

Atoll User Manual Under Calculation Method, define how the RS CINR will be calculated: Select Using frequency plan if you want the frequency plan to be taken into consideration when calculating the RS CINR. Select Ignoring frequency plan if you want the RS CINR to be calculated without taking the frequency plan into consideration.

d. Under Objective, define the RS CINR coverage parameters. Computation zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for received signal CINR coverage in the computation zone. Under Area Coverage, you can define the percentage by which the current received signal CINR coverage should be improved (Improve current coverage (+-)) or a target received signal CINR coverage (Target coverage (%)). Focus zone: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for RS CINR coverage in the focus zone. Hot Spot zone: Every hot spot zone defined under Zones on the Optimisation tab will appear under RS CINR. For each hot spot zone, select the check box in the Use column if you want to define a Minimum threshold (dBm) for received signal CINR in the hot spot zone.

e. Under Objective, click Parameters under RS CINR to define how ACP will calculate received signal CINR coverage. From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate received signal CINR coverage, or you can select Manual Configuration and define the settings yourself. Important: If you want to use a coverage prediction, the coverage prediction must have already been calculated. If you selected Manual Configuration from the Base prediction settings on list, define the following options: Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a Cell edge coverage probability. When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Macro diversity is also taken into account during the calculation of received signal CINR. Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied. You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced Parameters" on page 1298. Select a Service and a Terminal. The service and terminal specified are used during the calculation of received signal CINR through gain and losses (i.e., the service body loss, the gain and loss of the terminal antenna, and terminal noise factor).

f.

Under Criteria, click Weighting to set the importance of the objectives (see Figure 11.709).

Figure 11.709: Setting weighting options for LTE

1282

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks i. Under Weighting, move the slider to set the relative importance of RS and CINR coverage. You can set meeting one objective as more important than meeting the other, or you can set meeting only the RS or CINR coverage.

ii. Under Zone weighting, define the weight given to the computation zone, the focus zone, and any hot spot zone. With zone weighting, ACP adds an extra weight to all the pixels of a zone. Because one pixel can belong to several zones (for example, a pixel can be inside both the focus zone and the computation zone and in a hot spot zone, if there is one), the weight applied to that pixel is the weight of the zone with the highest priority: the hot spot zone, if it exists, then the focus zone, finally the computation zone. Important: It is important to remember that, if every zone is assigned the same weight, the optimisation is made as if no weight is assigned to any zone. Defining a weight of "0" for a zone means that that zone will not be taken into consideration when trying to reach the set objectives. Zone weighting is used to focus optimisation on the appropriate areas. The assigned weights are used to weight the traffic parameters selected on the Traffic tab, unless the optimisation is based on uniform traffic. For information on the selected traffic parameters, see "Setting Traffic Parameters for Non-uniform Traffic" on page 1283. However, if no traffic maps are available or if the optimisation is based on uniform traffic, zone weighting can be used to ensure that ACP prioritises the optimisation of areas of high traffic. With multiple layers, you might have a layer that is restricted geographically (for example, the LTE 2.5 GHz layer might only be available in rural areas). Because ACP always measures the quality target over the entire computation zone, such a situation would lead to a measurement of poor quality in the urban areas, where there are no LTE 2.5 GHz sectors. By defining a weight of "0" outside of the rural area for this layer, you can restrict the measurement of coverage only to the part of the layer with LTE 2.5 GHz sectors. This way, the global target (90% of coverage for instance) is measured in a meaningful way. g. Under Criteria, click Miscellaneous to define the overlap threshold margin. Enter an Overlap threshold margin. It will be used for traffic maps.

11.4.3.2.3

Setting Traffic Parameters for Non-uniform Traffic

By default, the traffic is assumed to be uniform within the computation zone. The Traffic tab enables you to select traffic maps in the Atoll document to define non-uniform traffic. The traffic maps describe the distribution of users in the network, along with their characteristics (i.e., services, terminals, and mobility types). Traffic maps can used to weight the quality figures measured on each pixel by using the traffic density on that pixel. You can use traffic maps to weight quality figures. For example, you can optimise RS CINR coverage based only on area (defined on the Optimisation tab as explained in "Setting Optimisation Parameters" on page 1277) while optimising signal coverage using traffic distribution. When using traffic maps, network quality is always optimised using traffic weighting. ACP supports all traffic maps used by Atoll. To set the traffic parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Traffic tab (see Figure 11.710).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1283

Atoll User Manual

Figure 11.710: Defining non-uniform traffic using the Traffic tab 3. Under Traffic Generated From, select one of the following methods for defining non-uniform traffic: Maps based on traffic densities: If you select Maps based on traffic densities, you can define the traffic weighting and traffic profiles. Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of CINR or Coverage or both. The weighting applied is the weighting defined on the Objectives tab. Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Service, Terminal, select a Traffic Density File by clicking the Browse button ( ), and assign a Weight.

When optimising LTE networks, you can use traffic maps as a traffic density file by first exporting traffic maps as traffic density maps. For information on exporting traffic maps, see "Exporting a Traffic Map" on page 1252. Following traffic maps: If you select Following traffic maps, you can select the maps that will be used to generate traffic and define the resolution of the extracted traffic and the traffic weighting. Under Following traffic maps, select the maps that will be used to generate traffic. Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of CINR or Coverage or both. Under Traffic Profiles, the traffic profiles will be displayed after ACP has extracted them from the selected traffic maps.

4. If you want to view the traffic profiles without running the optimisation setup, click Create Setup. ACP will then create the traffic profiles based on the traffic maps selected and the traffic parameters defined.

11.4.3.2.4

Setting Network Reconfiguration Parameters

The Reconfiguration tab allows you to select the LTE cells for which the total power will be reconfigured and the transmitters for which the antenna, azimuth, height, or tilt will be reconfigured. The Reconfiguration tab also allows you to select which sites or sectors can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly select sites for reconfiguration. For information on site selection, see "Defining Site Selection Parameters" on page 1290. Atoll allows you to export the reconfiguration parameters, modify them in an external application and then reimport them into the Reconfiguration tab. In this section, the following are explained: "Setting LTE Cell Reconfiguration Parameters" on page 1285 "Setting Transmitter Reconfiguration Parameters" on page 1286 "Linking Transmitters in Multi-layer Networks" on page 1287 "Using Precalculated Path Loss Matrices to Calculate Path Loss Attenuation" on page 1288 "Importing Network Reconfiguration Parameters" on page 1289.

1284

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Setting LTE Cell Reconfiguration Parameters

To set the LTE cell reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the LTE Cells tab (see Figure 11.712).

Figure 11.711: LTE cell reconfiguration options 3. Select the Total power check box for the total power of each selected cell 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 preamble power as offsets of the current power. 4. Select the Synchronise cell power on co-sector cells check box to ensure that all cells on the same sector are assigned the same cell power.

Important: 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. 5. Define the total power settings for each cell. Use: Select the Use check box corresponding to the cell to include it in the optimisation of the total power. Current: The current total power for the cell. Min. and Max.: Set a minimum and maximum preamble power to be respected during the optimisation process. Note: If you selected the Power max/min as offset check box, you will set the Min. Offset and Max. Offset for each cell.

Step (dB): Set a Step in dB that ACP should use with attempting to find the optimal total power. Note: For total power optimisation, the total range is defined with minimum, maximum and step values. There is an absolute maximum possible total power which depends on the other powers used in the cell (for control, traffic, and max cell power).

You can make the same changes to several cells by making the change for one item, selecting the others starting from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 59. You can select the cells to which the reconfiguration options are going to be applied using the Advanced section of the Reconfiguration tab. For more information, see "Selecting Sites for Reconfiguration" on page 1293. You can sort the contents of any column by right-clicking the column and selecting Sort Ascending or Sort Descending from the context menu.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1285

Atoll User Manual Caution: Cells that have been filtered out, either by zone or by clearing their check box in the table, will not be optimised but are still present in the network and, therefore, continue to generate interference.

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. For information on importing network reconfiguration options, see "Importing Network Reconfiguration Parameters" on page 1289.

Setting Transmitter Reconfiguration Parameters

To set the transmitter reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Reconfiguration tab (see Figure 11.712).

Figure 11.712: Transmitter reconfiguration options 3. Select the parameters that will be optimised: Antenna type: Select the Antenna type check box for ACP to adjust the antenna type by selecting the best antenna from the antenna group assigned to each selected transmitter. Electrical tilt: Select the Electrical tilt check box for ACP to select the best electrical tilt from the antenna group assigned to each selected transmitter within the defined range. Note: When ACP selects the best antenna type, it will also chose the best electrical tilt from the antenna group even if it is not optimising the electrical tilt. However, because no range is defined, ACP will select the best electrical tilt from all available.

Azimuth: Select the Azimuth check box for ACP to set the antenna azimuth using a defined range on either side of the currently defined azimuth. Note: By default, ACP optimises the antenna azimuth of each sector of a site individually. However, you might want to retain the same inter-sector angle separation. If this is the case, you can select the Azimuth check box corresponding to that site under Lock Site on the Sites tab of the Reconfiguration tab.

Mechanical tilt: Select the Mechanical tilt check box for ACP to set the mechanical tilt within the defined range and in the defined number of steps. Height: Select the Height check box for ACP to set the antenna height within the defined range and in the defined number of steps.

1286

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Note:

By default, ACP optimises the height of all antennas of a site identically. In other words, if ACP optimises the antenna of one sector by raising it 1 m., it will also raise the antennas of all other sectors by the same amount, in order to respect the distance between all antennas on the transmitter mast. However, in might not be necessary to maintain this distance, in which case you might want to optimise the height of each antenna of a site individually. f this is the case, you can clear the Height check box corresponding to that site under Lock Site on the Sites tab of the Reconfiguration tab.

The table displays, for each parameter selected, both the current settings for each cell in the selected zone and the currently defined optimisation parameters. Note: If you want ACP to display more information on each transmitter, you can select the Show Advanced Grid check box. ACP will then display, for each transmitter, the antenna masking method, the propagation model used, the transmitter height, and the name and status of the site the transmitter is located on. The propagation model displayed is extracted from the Atoll document but can be changed if the propagation model is not recognised by ACP (for more information, see "ACP and Antenna Masking" on page 1271).

4. Define the settings to be optimised for each cell. If are optimising the antenna azimuth, you can enter a single value in the Variation column, to define a range on either side of the current azimuth, or you can enter a minimum and maximum value separated by a semi-colon in the format "-min;max", (for example, "-20;40") in the Variation column for an asymmetric antenna. You can make the same changes to several cells by making the change for one item, selecting the others starting from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 59.

Linking Transmitters in Multi-layer Networks

When you are optimising transmitters in multi-layer environments, ACP automatically links transmitters in the same location but in different layers to ensure that it applies the same reconfiguration to them. ACP links them not only by location, but also by azimuth, mechanical tilt, and antenna height. If ACP does not automatically link two transmitters which should be linked, it is normally because there is too large a difference in one of the parameters of the two transmitters, for example, a few degrees in azimuth, one degree in mechanical tilt, or one meter difference in antenna height. If two transmitters should be linked but were not, you can manually link them. Note: If the site of one of the linked transmitters has either its antenna heights or azimuths locked, i.e., if changes made to one sector of the site are made to all sectors on that site, then corresponding changes will be made to the other linked transmitter. For more information on locking antenna heights or azimuths, see "Setting Transmitter Reconfiguration Parameters" on page 1286.

To link transmitters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the Transmitters tab. 3. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear. 4. Under Advanced, click the Multi-layer Management tab. On the Multi-layer Management tab, you can link transmitters (see Figure 11.713).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1287

Atoll User Manual

Figure 11.713: Multi-layer management To link transmitters in the same location but on different layers: a. Hold CTRL and click the first transmitter in the table above and then the second transmitter. The Link button on the Multi-layer Management tab is now available. b. Click the Link button. The two transmitters are now linked and ACP will apply the same reconfiguration to them both. To unlink linked transmitters: a. Select the transmitters in the table The Unlink button on the Multi-layer Management tab is now available. b. Click the Unlink button. The transmitters are no longer linked. To unlink all linked transmitters: Click the Unlink All button. ACP resets all linked transmitters.

To automatically all transmitters in the same location but on different layers: Click the Auto Link button. ACP links all transmitters that have the same position, azimuth and mechanical tilt.

Using Precalculated Path Loss Matrices to Calculate Path Loss Attenuation

You can define how Atoll ACP calculates path loss matrices, using either Atolls propagation models, ACPs internal propagation model, or precalculated path loss matrices. These parameters will be applied to all new and duplicated setups. To define how ACP calculates path loss matrices: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Reconfiguration tab (see Figure 11.712). 3. If you are using a propagation model that ACP does not natively support, select the Enable precalculated path loss matrices check box. You will then be able to select the propagation model for which ACP will pre-calculate path attentuation. 4. Under Propagation Models, select the check boxes in each column to define how ACP will interact with that propagation model. Not all parameters are available for all propagation models:

Tip:

By default, all available propagation models are displayed. By selecting the Show only used propagation models check box, ACP will only display the propagation models that are actually used.

Antenna masking method: The Antenna masking method indicates whether ACP can use this propagation model natively, or whether ACP uses its own default method. The information in this column can not be edited.

1288

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Use precalculated path loss: Select the check box in the Use precalculated path loss column corresponding to every propagation model that is not supported natively by ACP or that can not be replaced using ACPs internal default method. Use clutter height: Select the check box in the Use clutter height column if you want ACP to take clutter height information from the clutter heights file, if available, or from the clutter classes file. Receiver on top of clutter: Select the check box in the Receiver on top of clutter column if you want the receiver height to be sum of the clutter height and the receiver height. This option can be used, for example, to model receivers on top of buildings. Use radial method: Select the check box in the Use radial method column if you want ACP to use the radial method to extract the profile between the transmitter and the receiver.

5. Click OK. Important: When you use precalculated path loss matrices, they must be stored externally. For information on storing path loss matrices externally, see "Setting the Storage Location of Path Loss Matrices" on page 171. 6. In the table on the Reconfiguration tab, select the check box in the Precalculated Path Loss Matrices column for each entry in the Tx Name column that uses a propagation model that is not natively supported by ACP (see Figure 11.714).

Figure 11.714: Using precalculated path loss matrices

Importing Network Reconfiguration Parameters

Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reimport them into the Reconfiguration tab. To import reconfiguration parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the desired tab. 3. Right-click the table and select Export as Text from the context menu. The Save As dialogue appears. 4. Enter a name in the File name box and click Save. The file will be saved as a tab-delimited text file. 5. Open the text file in another application, for example, in a spreadsheet application, and make the modifications desired. 6. Save the file as a text file and return to Atoll. 7. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear. 8. Under Advanced, click the Import Facility tab. 9. Click the Import from File button. The Open dialogue appears. 10. Browse to the file and click Open. The Import Data dialogue appears (see Figure 11.715).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1289

Atoll User Manual

Figure 11.715: Importing site data into the Reconfiguration tab 11. Under Format Parameters, enter the number of the first row with data in the First Imported Row box, select the data Separator, and select the Decimal Symbol used in the file. 12. If you want only the cells in the imported list to be used on the Reconfiguration tab, select the Use Only Cells in List check box. The Use check box will be cleared for all cells that are not in the imported file and they will not be affected by reconfiguration options. 13. In the table, ensure that the column names from the imported file (the Source file) match the column names on the Reconfiguration tab (Destination). You can change the Destination column by clicking the column name and selecting the name from the list. Note: Any values in the imported file for current values can not be imported.

14. Click the Import button to import the file and replace the settings in the Reconfiguration tab.

11.4.3.2.5

Defining Site Selection Parameters

The Reconfiguration tab allows you to select which sites can be added or removed to improve existing or new networks. You can also use the Reconfiguration tab to quickly select sites for reconfiguration. In this section, the following are explained: "Selecting Sites for Addition or Removal" on page 1290 "Creating Candidate Sites" on page 1292 "Selecting Sites for Reconfiguration" on page 1293.

Selecting Sites for Addition or Removal

You can use the Reconfiguration tab to select the sites that will be added or removed to improve existing or new networks. To set site selection parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab (see Figure 11.716).

1290

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.716: Site selection 3. Select the Current Site Selection check box to enable site selection. You can then define how sites will be added or removed. 4. In the table, define how each site will be treated during site selection: a. Select the Locked check box for each site that is not to be affected by site selection.

Tip:

If you have many sites that you do not want to be affected by site selection, you can select and lock them with the Advanced section. For more information on the options in the Advanced section, see "Selecting Sites for Reconfiguration" on page 1293.

b. Select the Status for each site that is not locked: Important: Only active sites are loaded by ACP. If you want inactive sites to be taken into account during site selection, you must set them as active first in Atoll. When you commit the results of the ACP run, all sites and sectors disabled by the ACP will be set to inactive in Atoll. Existing: An "Existing" site is considered as being active in the initial network. ACP will remove an existing site if the Site Removable check box has been checked and if removing the site will improve network quality. If the Sectors Removable check box has been checked, one or more sectors might be removed if removing them will improve network quality. Candidate: A "Candidate" site is considered as being inactive in the initial network. ACP will add the site during the optimisation process if adding the site will improve network quality. If the Sectors Removable check box has been checked, only one or more sectors might be added if adding them will improve network quality. You can define candidate sites by clicking the New Candidate Setup button. For more information on defining candidate sites, see "Creating Candidate Sites" on page 1292. c. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality. d. Select the Site Removable check box for each site that can be removed to improve network quality. e. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group. Note: If a site group has no sites belonging to it, it is automatically deleted.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1291

Atoll User Manual You can create a new group for candidate sites if desired. To create a group: i. Under Group, click the field and select New from the list. The New Site Group dialogue appears (see Figure 11.717).

ii. Enter a Group Name and define the minimum and maximum number of sites from this group (from 0 to 1000) that must be respected by ACP during optimisation (Minimum Site Occurrence and Maximum Site Occurrence, respectively). If there is no minimum or maximum that ACP must respect, leave the field blank. iii. Click OK to create the group and return to the Site Selection tab.

Figure 11.717: Creating a new site group f. Select the Sectors Removable check box for each site that can have sectors removed to improve network quality.

g. Select the Site Removable check box for each site that can be removed to improve network quality. h. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a group, ACP must respect the constraints of the group. Note: If a site group has no sites belonging to it, it is automatically deleted.

You can create a new group for candidate sites if desired. To create a group:

Creating Candidate Sites

The ACP enables you to create a list of candidate sites that can be added to the network to improve quality. For each candidate, you can specify both the location and the station template the candidate site would be based on if the ACP adds it to the network. As well, the ACP can optimise candidate sites when they are added to the network. During optimisation, the ACP will choose first from the sites defined as candidates on the Sites tab and then from the list of candidate sites. To create or edit candidate sites: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab. 3. On the Sites tab, click the New Candidate Setup button. The New Candidate Setup dialogue appears (see Figure 11.718).

Figure 11.718: New Candidate Setup dialogue

1292

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 4. Under Zone Configuration, define, if desired, how candidate sites will be treated for each zone: Zone: Select the zone (computation, focus, or hot spot zone defined on the Optimisation tab) from the list. The ACP will add the candidate site according to the quality objectives defined on the Optimisation tab. Default Station Template: Select the station template that any candidate site the ACP adds in the selected zone will be based on. Note: The ACP can optimise each candidate site based on a template. You can set the optimisation parameters for each template by clicking the Template Reconfiguration button. For information on the options, see "Setting Transmitter Reconfiguration Parameters" on page 1286.

Default Group: Select the group that the candidate site will belong to by default. Radio Layer: If there is more than one radio layer, select the radio layer the candidate site will be added to.

5. Under New Candidate List, define the individual candidate sites. For each candidate site set the following: Name: Enter a name for the candidate site. Location: Click the Browse button ( ) to define the location of the candidate site. You can define the location either as a set of co-ordinates or you can select an existing site from a list. Station Template: Select the station template the candidate site will be based on. This selection overrides the selection made under Zone Configuration. Group: Select the group the candidate site will belong to. This selection overrides the selection made under Zone Configuration. Height: The 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 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. Radio Layer: Select the radio layer the candidate site will be added to. This selection overrides the selection made under Zone Configuration.

6. If desired, select the Try to use multi-band antenna when possible check box. The ACP will attempt to use linked transmitters on candidate sites if possible. 7. Click the Action button to update the list of new candidates by selecting one of the following options: Clear List: Select Clear List to delete all current entries in the New Candidate List. Import from File: Select Import from File to import a list of candidate sites, defined as XY coordinates. Import from Current Sites Defined as Location Only: Select Import from Current Sites Defined as Location Only to import as candidate sites sites in the current document that have no transmitters. The sites imported are those in the reconfiguration zone(s) selected on the Optimisation tab. The defined reconfiguration zone(s) is displayed at the top of the Reconfiguration tab as well. Update Candidate Height from Clutter Height: Select Update Candidate Height from Clutter Height to define the height of all candidate sites for each clutter class.

Selecting Sites for Reconfiguration

You can use the Advanced area of the Reconfiguration tab to select sites. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on page 1284. To select sites: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab. 3. Select the Site Selection check box. 4. Click Advanced to display the Advanced area (see Figure 11.719).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1293

Atoll User Manual

Figure 11.719: The Advanced section 5. Select the Global Change tab. 6. Select the sites: For entire table: Select For entire table if you want to select all sites in the table. 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 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. Note: This option is only available in co-planning projects with more than one technology.

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. Note: If you want to lock the selected sites, you can select the Set "Locked" check box and click Apply. The locked sites will not be affected by the site addition or removal options.

11.4.3.2.6

Defining Antenna Groups

You can use the Antenna tab to define antenna groups according to their physical characteristics, as well as grouping patterns according to their antenna pattern and defining multi-band antennas. The antenna groups are necessary to apply the antenna type or electrical tilt reconfiguration options defined on the Reconfiguration tab. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration Parameters" on page 1284. 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. In this section, the following are explained: "Creating and Grouping Antennas by Pattern" on page 1295 "Grouping Antennas Automatically" on page 1296 "Defining Multi-band Antennas" on page 1296 "Creating Antenna Groups" on page 1297.

1294

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Creating and Grouping Antennas by Pattern

Atoll enables you to create physical antennas by grouping several instances of antennas by their pattern. By setting an option in the ACP.ini file, you can also optimise the additional electrical downtilt (AEDT) of antennas. When you have set this option, you can select which antennas for which you will optimise the AEDT and the range of values that Atoll can chose from during the optimisation process. For information on setting options in the ACP.ini file, see the Administrator Manual. To group antennas by their pattern: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 11.720). The Antenna tab displays all antennas in the Antenna Pattern Table and the groups under Physical Antenna.

Figure 11.720: Antenna tab 3. Click the New button to create a new group under Physical Antenna. You can change the name of the new group or of any group by right-clicking the group name twice under Physical Antenna, selecting Rename from the context menu, and entering the new name. You can delete one group by selecting it under Physical Antenna and clicking the Delete button. You can delete all groups by clicking the Delete All button. 4. Assign antennas to a group to create physical antennas or to associate antenna patterns to define a radiation diagramme of a group of antennas with several variations of electrical tilt: a. Select the group under Physical Antenna. b. Select the antenna under Antenna Pattern Table and click the right arrow between the columns ( ) to assign it to the selected group. Antennas under Antenna Pattern Table that have been assigned to a group are indicated with an icon ( ). You can assign the same antenna to more than one group. You can remove an antenna from a group by selecting it in the group under Physical Antenna and clicking the left arrow between the columns ( Note: ).

When you have grouped the antennas, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antennas will then be grouped automatically according to this definition.

5. If you are also optimising additional electrical downtilt, select the check box in the Use AEDT column corresponding to each antenna for which you want to optimise the additional electrical downtilt and define the limits Atoll must respect by entering values in the Min. AEDT and Max. AEDT for each antenna to be optimised.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1295

Atoll User Manual

Figure 11.721: The Antenna Pattern Table with AEDT enabled

Grouping Antennas Automatically

You can group antennas automatically using a regular expression, or "regex." The regular expression is retained from one Atoll session to the next. Therefore, once you have set the regular expression for the given antenna naming convention, you will not have to set again for the next Atoll session. The default regex pattern is overwritten when you change it. You can return to the default regular expression by clearing the text box and clicking OK. You can change the default regular expression by editing the appropriate entry in the ACP.ini file. For more information on the options available in the ACP.ini file, see the Administrator Manual. Important: It is recommended to identify both the antenna type and the electrical tilt in the antenna name in Atoll and to separate the antenna type and electrical tilt with a special character, for example, "_". This will make it easier to group antenna groups automatically using a regular expression. To group antenna automatically: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Patterns tab (see Figure 11.720 on page 1295). 3. Under Automatic Creation, enter a regular expression, or "regex," in the text box.

Tip:

Clicking the tooltip button ( expressions.

) displays a tooltip with an explanation of common regular

4. Click the Build from expression button to create antenna groups according to the defined regular expression. Note: When you have created the antenna groups, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antenna groups are then automatically created according to this definition.

Defining Multi-band Antennas

When you have grouped antennas according to their physical characteristics as explained in "Creating and Grouping Antennas by Pattern" on page 1295 and "Grouping Antennas Automatically" on page 1296, they are displayed on the Radome tab of the Antenna tab, grouped according to their frequency band. You can merge these groups to create groups of antennas that are multi-band antennas. To define multi-band antennas: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Radome tab (see Figure 11.720 on page 1295).

1296

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.722: Creating multi-band antennas 3. Create multi-band antennas by merging two or more antenna groups: a. Select two or more antenna groups by holding CTRL and clicking the antenna groups in the Radome Table. b. Click the Merge button. The antenna groups are now merged and will appear on the Antenna Groups tab. You can break the merged antenna groups up by selecting them in the Radome Table and clicking the Unmerge button, or by clicking Unmerge All. If you click Unmerge All, all merged antenna groups will be broken up. 4. Under Automatic Creation, enter a regular expression, or "regex," in the text box.

Creating Antenna Groups

ACP creates antenna groups based on common their frequency band, but you can create antenna groups based on other common characteristics. The antenna groups are used especially to chose between a directive antenna (of 35 degrees) and a less directive one (of 65 degrees). However, in most circumstances, one antenna group corresponds to one antenna radome. To group antennas: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Antenna Groups tab (see Figure 11.723 on page 1298). On the Antenna Groups tab, there is already one group called "Default" in the Antenna Groups pane of the tab. The "Default" group is created automatically by ACP and contains all the antenna patterns available for a given frequency.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1297

Atoll User Manual

Figure 11.723: Creating antenna groups 3. Click the New button to create a new group under Antenna Groups. You can change the name of the new group or of any group by right-clicking the group name twice under Antenna Groups, selecting Rename from the context menu, and entering the new name. You can delete one group by selecting it under Antenna Groups and clicking the Delete button. You can delete all groups by clicking the Delete All button. 4. Assign antennas to groups according to their physical characteristics: a. Select the group under Antenna Groups. b. Select the antenna under Radome Table and click the right arrow between the columns ( ) to assign it to the selected group. Antennas under Radome Table that have been assigned to a group are indicated with an icon ( ). You can assign the same antenna to more than one group. You can remove an antenna from a group by selecting it in the group under Antenna Groups and clicking the left arrow between the columns ( Note: ).

When you have created the antenna groups, you can back up the configuration by clicking the Backup Configuration button. In future ACP sessions, the antenna groups are then automatically created according to this definition.

11.4.3.2.7

Adding Comments to the Optimisation Setup

You can enter comments about the current optimisation setup on the Comments tab. To add comments: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Comments tab and add your comments.

11.4.3.2.8

Setting Advanced Parameters

The Advanced tab displays the traffic parameters that ACP uses to optimise the Atoll project. You can use the Advanced tab to modify this Atoll data. The Advanced tab is not displayed by default. For information on displaying the advanced parameters, see "Configuring the Default Settings" on page 1273. To set advanced parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 1276. 2. Click the Advanced tab. 3. In the left column, click the Expand button ( ) to expand the Parameters folder. 4. In the Parameters folder, select Services. In the Services section, the service-related parameters of the Atoll document are displayed.

1298

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 5. Under Services, define the body loss for each of the services defined in the Atoll document. 6. In the Parameters folder, select Terminals. In the Terminals section, the terminal-related parameters of the Atoll document are displayed. In a co-planning document, there will be a Terminals folder for each technology. 7. Under Terminals, define the Antenna Gain, the Loss, and the Noise Factor for each terminal. 8. In the Parameters folder, select Clutter Classes. In the Clutter Classes section, the clutter-related parameters of the Atoll document that affect optimisation are displayed. 9. Under Clutter Classes, you can set the following parameters for each clutter class: Height: You can set the Height for each clutter class. Indoor Loss (dB): You can set the Indoor Loss (dB) for each clutter class. The indoor loss is used to calculate shadowing losses on the path loss, as related to the cell edge coverage probability. Model Standard Deviation (dB): You can set the Model Standard Deviation (dB) for each clutter class. The model standard deviation is used to calculate shadowing losses on the path loss, as related to the cell edge coverage probability. C/I Standard Deviation (dB): You can set the Ec/Io Standard Deviation (dB) for each clutter class. The CI standard deviation is used to calculate shadowing losses on the C/I values, as related to the cell edge coverage probability. SU-MIMO Gain Factor: You can set the SU-MIMO Gain Factor for each clutter class. The SU-MIMO gain factor is used 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): You can set the Additional Diversity Gain (DL) (dB) for each clutter class. The additional diversity gain DL is added to the users downlink C/(I+N). Additional Diversity Gain (UL) (dB): You can set the Additional Diversity Gain (UL) (dB) for each clutter class. The additional diversity gain UL is added to the users uplink C/(I+N). Is Indoor: You can define the clutter class as being inside by selecting the Is Indoor check box. You can set default values for all clutter classes for each of these parameters except for height.

Note:

11.4.4

Running an Optimisation Setup

When you have finished defining the optimisation parameters as described in "Defining Optimisation Parameters" on page 1277, you can run the optimisation setup, either immediately by clicking the Run button. You can also save the defined optimisation setup by clicking the Create Setup button and then running the optimisation at a later point. To run a saved optimisation setup: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 3. Right-click the setup folder that you want to run in the ACP - Automatic Cell Planning folder. The context menu appears. 4. Select Run from the context menu. The optimisation setup runs. As the optimisation setup runs, ACP displays the current status of the process (see Figure 11.724) allowing you to observe the progress. You can pause the optimisation if you desire or stop the optimisation early, The Optimisation dialogue has two tabs: Graphs: The Graphs tab displays a graph with the iterations on the X axis and the optimisation objectives (RS, CINR, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 11.724). The values displayed are indicated with a legend. Changes: The Changes tab displays in a graph indicating the quantity of changes made for each reconfiguration parameter selected during setup. The values displayed are indicated with a legend. Quality Maps: The Quality Maps tab displays coverage quality maps for RS and RS CINR improvement. The maps display the computation zone with the network improvement performed to that point. If you based this optimisation on a coverage prediction (see "Setting Objective Parameters" on page 1280), the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default (see "Changing the Display Properties of ACP Maps" on page 1313) or by using a configuration file (see "Configuring the Default Settings" on page 1273).

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1299

Atoll User Manual

Figure 11.724: The network coverage improvement graphs and maps When the optimisation has finished, the results are stored in the optimisation folder on the Data tab of the Explorer window. By default, Atoll calls the optimisation folder a "Setup" folder. Each setup folder contains one or more optimisation processes. Each optimisation process folder contains the results of that optimisation. For information on viewing optimisation results, see "Viewing Optimisation Results" on page 1301.

Figure 11.725: An optimisation run in the Explorer window Note: You can perform an optimisation on a network that has already been optimised. After running the first optimisation and committing the results, you can create and run a second optimisation, with different parameters on the optimised network.

11.4.5

Working with Optimisations in the Explorer Window

Atoll offers you several options for working with the optimisation that you can access using the context menu on the Data tab of the Explorer window. To work with the optimisation: 1. Click the Data tab in the Explorer window. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder.

4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 11.726).

1300

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.726: Options available in the context menu 5. Select one of the following from the context menu: Properties: Selecting Properties from the context menu opens the optimisations Properties dialogue. You can modify all of the optimisation parameters except for the selection of traffic maps (for information on the optimisation parameters, see "Defining Optimisation Parameters" on page 1277). If you want to base an optimisation on different traffic maps, you must create a new optimisation (for information on creating a new optimisation, see "Creating an Optimisation Setup" on page 1276). Run: Selecting Run runs the optimisation setup. The results will be contained in a new optimisation folder in the setup folder. Caution: If you have changed some data in Atoll, for example, if you added transmitters or change some of the transmitter settings, the data that optimisation results are based on may differ from the current Atoll data. If you run a optimisation based on settings made before the changes, it will not take the changed data into consideration. ACP normally detects changes in the Atoll document data and can lock a group if it is impossible to run an optimisation that is coherent with existing data. ACP can lock a group if, for example, when you commit optimisation results after the path losses have been recalculated and are no longer consistent with the data used to run the optimisation. When this happens you will either have to: Create a new optimisation as explained in "Creating a New Optimisation Setup" on page 1277. Duplicate an existing optimisation which will create a new optimisation with the same configuration but with updated parameters. Roll back the previously committed parameters as explained in "The Commit Tab" on page 1308.

Delete: Selecting Delete deletes the defined optimisation setup and any results. Storing optimisation results and the group configuration increase the size of the Atoll file. Deleting unused setups in the ACP - Automatic Cell Planning folder will decrease the size of the Atoll file.

Load Configuration: Selecting Load Configuration displays the Open dialogue. You can then select a PRJ file based on the settings of a different optimisation. When you load a configuration based on a different Atoll document, only the settings that are not specific to that document are loaded. Save Configuration: Selecting Save Configuration displays the Save As dialogue. You can then save the optimisation settings in a PRJ file. You can then use this PRJ file to quickly configure an optimisation.

Tip:

Saving a configuration is a quick way to save the settings you have made in an external file. you can then easily create new configurations using these same settings as a basis without having to recreate them.

Duplicate: Selecting Duplicate displays the ACP Duplicate Options dialogue. You can then duplicate the either the ACP-generated data of selected optimisation setup or all of the data of the setup. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid.

11.4.6

Viewing Optimisation Results

Once you have run the calibrated optimisation as explained in "Running an Optimisation Setup" on page 1299, the results are stored in the optimisation folder on the Data tab of the Explorer window. You can view the results in the optimisations Properties dialogue or in the map window. In this section, the following are explained: "Viewing Optimisation Results in the Properties Dialogue" on page 1302 "Viewing Optimisation Results in the Map Window" on page 1308 "Viewing Optimisation Results Using the Histogram" on page 1314.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1301

Atoll User Manual

11.4.6.1

Viewing Optimisation Results in the Properties Dialogue

You can view the results of the optimisation run in its Properties dialogue in the ACP - Automatic Cell Planning folder. To view the results of the optimisation in its Properties dialogue: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view.

4. Right-click the optimisation. The context menu appears. 5. Select Properties from the context menu. The optimisations Properties dialogue appears. The optimisation results are on individual tabs of the Properties dialogue (with an extra tab, the General tab, that allows you to change the name of the optimisation results): Statistics: The Statistics tab displays a synthesised view of the optimisation results of the quality figures (RS coverage and RS CINR). For more information on the Statistics tab, see "The Statistics Tab" on page 1302. Sectors: The Sectors tab displays a table with the reconfigured cells in green, sites and sectors which have been added or removed, and the RS quality, the CINR quality, and the total power per cell before and after optimisation. For more information on the Statistics tab, see "The Sectors Tab" on page 1303. Graph: The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (RS coverage, RS CINR, and global cost, if you have selected to take cost into consideration) on the Y axis. The values displayed are indicated with a legend. For more information on the Graph tab, see "The Graph Tab" on page 1305. Quality: The Quality tab displays the computation zone with coverage quality maps for RS coverage before and after optimisation. For more information on the Quality tab, see "The Quality Tab" on page 1306. Change Details: The Change Details tab enables you to analyse the improvement caused by each reconfiguration option. For more information on the Change Details tab, see "The Change Details Tab" on page 1307. Commit: The Commit tab enables you to commit the set of selected changes. For more information on the Commit tab, see "The Commit Tab" on page 1308.

11.4.6.1.1

The Statistics Tab

The Statistics tab displays a synthesized view of the optimisation results of the quality figures (RS coverage quality and RS CINR quality).

Figure 11.727: The Statistics tab For the RS coverage quality and RS CINR quality, both the initial and final figures are given, as well as the absolute improvement. These figures are given both for the computation zone and the focus zone. If you defined weights for each zone on the Objectives tab of the dialogue used to define the optimisation (see "Setting Objective Parameters" on page 1280), ACP indicates that the results are weighted. You can see more detailed information by clicking the links (see Figure 11.728): Show Change Statistics: The change statistics showing the reconfiguration and site selection statistics. Show Detailed Hot Spot/Clutter Results: The detailed quality figures on each hot spot and by each clutter class. Show Input: The input settings of this optimisation.

1302

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.728: The Statistics tab - detailed information You can export the results by clicking the Export button. The Save As dialogue that appears allows you to select the format in which you want to save the results: XLS, TXT, HTML, or XML.

11.4.6.1.2

The Sectors Tab

The Sectors tab displays a table with all the cells in the network with the following information: Cells which have been reconfigured are displayed in green (i.e., if they have had their antenna type, antenna height, azimuth, mechanical tilt, or total power reconfigured). Sites and sectors which have been added or removed. The RS quality and RS CINR quality before and after optimisation. The quality figures are measured on the best server area of each cell. Antenna type, height, azimuth, mechanical tilt, and total power initial and final values for each cell.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1303

Atoll User Manual

Figure 11.729: The Sectors tab The cell results are displayed in a table. You can access options such as sorting, exporting data using the context menu (see Figure 11.730) sort, column hiding, export, etc.

Figure 11.730: Options available for data in the Sectors tab

1304

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

11.4.6.1.3

The Graph Tab

The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (RS coverage, RS CINR, and global cost, if you have selected to take cost into consideration) on the Y axis (see Figure 11.731). The values displayed are indicated with a legend.

Figure 11.731: The Graph tab The tool bar allows you to: Zoom and span the graph Export to a BMP image file or simple text file Print the graph Show the values along the curves.

Figure 11.732: The Graph tab with the values displayed on the selected point

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1305

Atoll User Manual

11.4.6.1.4

The Quality Tab

The Quality tab displays the coverage quality maps for RS and RS CINR before and after optimisation. You can define the area displayed in the coverage quality maps by selecting the zone (computation, focus, or hot spot) from the list above the maps.

Figure 11.733: Coverage maps on the Quality tab The maps are displayed with a range of values displayed on the right. If you based this optimisation on a coverage prediction (see "Setting Objective Parameters" on page 1280), the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default (see "Changing the Display Properties of ACP Maps" on page 1313) or by using a configuration file (see "Configuring the Default Settings" on page 1273). This range can be modified using the Map Properties dialogue accessed through the tool bar (see Figure 11.734).

Figure 11.734: Defining the display properties of the coverage maps In addition to the map, a histogram is provided for quick evaluation of the improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the Generate Report tool in Atoll which only uses uniform weighting. Note: The default colour range used for display can be changed using the acp.ini preference configuration file. For information on the acp.ini file options, see the Administrator Manual.

1306

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

11.4.6.1.5

The Change Details Tab

In addition of the map, a histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through the Generate Report tool in Atoll which only uses uniform weighting. Note: The default colour range used for display can be changed using the acp.ini preference configuration file. For information on the acp.ini file options, see the Administrator Manual.

Figure 11.735: The Change Details tab You can select a subset of all changes using a slider and view the corresponding performance improvement on the graph. This can enable you to achieve two goals: To select a subset of changes to be implemented. For example, you might find that implementing only one-third of the recommended changes will provide 80% of the benefit. You could then chose to commit only those changes to the Atoll document. To find the optimal order in which to apply these changes in the field, while at the same time avoiding less than optimal performance, or even degrading the performance, during the implementation phase.

Before selecting a subset of recommended changes, it is important to understand that ACP calculates the set of recommendations globally and that these changes are interdependent. During the finalisation step, ACP calculates the ordered list of changes displayed on the Change Details tab by starting from the initial network configuration and iteratively selecting the change that will have the most effect on the network. If you 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 proposed configuration. Important: The data displayed on the other tabs takes all the proposed changes into consideration. If you select only a subset of the proposed changes on the Change Details tab, the statistics displayed on other tabs do not change. When you commit the optimisation changes, ACP will only commit the proposed changes selected on the Change Details tab. For information on committing the optimisation changes, see "The Commit Tab" on page 1308.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1307

Atoll User Manual

11.4.6.1.6

The Commit Tab

This dialogue enables you to commit the set of selected changes (total power, antenna, azimuth, tilt, or site selection) to the Atoll document or to roll the network back to its initial state. The Commit tab automatically takes into account the changes selected on the Change Details tab; the Use check box is cleared for any change that was deselected on the Change Details tab.

Figure 11.736: The Commit tab You can select one of the following: Commit: Clicking the Commit button will update the Atoll document with the changes displayed on the Commit tab. Once you have committed the changes, you can recalculate the path losses and use any of the functions available in Atoll, including coverage predictions and simulations. After you perform any such calculations, remember to click the Roll Back to Initial State button to return to the original network settings. Roll Back to Initial State: Clicking the Roll Back to Initial State button will revert the Atoll network to its state before the optimisation was run.

When you click either the Commit button or the Roll Back to Initial State button, information about the commit or rollback process is displayed in the Atoll Event Viewer.

The Effects of Committing or Rolling Back Changes on Existing Setups

When you commit the optimisation results, all existing configuration setups are locked because the network state on which the configuration setup was based is not coherent with the current path losses. ACP automatically detects any incoherence and prevents you from running an optimisation on incoherent data. ACP will unlock the optimisation setups when it becomes possible, for example, when you roll back the data to restore the Atoll state to be coherent with the network state on which the configuration setup was based. It is important to remember that you can commit or roll back other optimisation results even when the setup is locked.

11.4.6.2

Viewing Optimisation Results in the Map Window

ACP can display optimisation results in the form of maps in the map window. This allows you to view the results and facilitates analysis. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be used for the quality maps, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default or by using a configuration file. To view the results of the optimisation in the map window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view.

4. Right-click the optimisation. The context menu appears. 5. Select New Map from the context menu. The ACP Map Types dialogue appears (see Figure 11.738).

1308

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.737: Displaying a new map based on ACP results The maps available in the ACP Map Types dialogue are organised by category. 6. Select the category of maps or click the Expand button ( egory or map. ) to expand the category and then select the sub-cat-

7. Click OK to create the maps. The maps are created and inserted into the folder of the setup containing the optimisation results (see Figure 11.738).

Figure 11.738: The map types correspond to the available results You can display a map by selecting its check box in the folder of the setup containing the optimisation results. The display properties can be changed for a single map or for all maps. For information on the display properties for ACP maps, see "Changing the Display Properties of ACP Maps" on page 1313. The following sections provide more information on the maps: "The Quality Analysis Maps" on page 1309 "The Coverage Analysis Maps" on page 1310 "The Change Analysis Maps" on page 1311 "Best Server Analysis" on page 1312 "Comparing Maps" on page 1312 "Changing the Display Properties of ACP Maps" on page 1313 "Exporting ACP Coverage Maps" on page 1314.

11.4.6.2.1

The Quality Analysis Maps

The quality analysis maps enable you to display the signal quality maps in the Atoll map window. These maps are the same as those displayed on the Quality tab of the optimisations Properties dialogue. The quality analysis maps are the equivalent of maps created by different Atoll coverage predictions: The RS coverage maps correspond to the Atoll coverage by signal level. For more information, see "Studying Signal Level Coverage" on page 1189. The RS CINR coverage maps correspond to Atoll coverage by C(I+N) level. For more information, see "Making a Coverage by C/(I+N) Level" on page 1214. The overlapping zones maps correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 1199.

Making these maps available within ACP enables you to quickly validate the optimisation results without having to commit the results and then calculate a coverage prediction in Atoll. The ACP maps display results very similar to those that Atoll

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1309

Atoll User Manual would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before basing any decision to commit the optimisation results on the maps produced by ACP, you should keep the following recommendations in mind: You should verify the results with a different Atoll coverage prediction, such as the pilot pollution prediction. ACP generated maps are generated using the entire set of proposed changes. They do not take into account the change subset defined on the Change Details tab. Multiple carriers are not supported by ACP; the maps are only provided for the requested carrier. Even after committing the optimisation results, differences can remain between the ACP maps and the maps resulting from Atoll coverage predictions.

You can view the exact RS coverage value on any pixel by letting the pointer rest over the pixel. The RS coverage value is then displayed in a tooltip. For the overlapping zones map, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Configuring the Default Settings" on page 1273) or by setting the CellOverlap parameter in the acp.ini file.

Figure 11.739: Examples of an RS coverage variation map (left) and a final overlapping zones map (right) For each network quality study, ACP offers a map showing the initial network state, the final network state, and a map showing the changes between the initial and final state.

11.4.6.2.2

The Coverage Analysis Maps

The coverage analysis maps display the coverage status according to the defined threshold used in the optimisation (for both RSCP and EcIo). You can use the coverage analysis maps to quickly see the area where the coverage requirements have been fulfilled. In addition, the thresholds used for clutter and hot spot zones are taken into account. There are two types of coverage analysis maps: Initial and Final Coverage: The initial and final transmitter coverage maps display the areas where there is transmitter RS and CINR coverage improvement. Coverage Improvement: The transmitter and CINR coverage improvement maps show how the RS and CINR coverage has been improved or degraded by the optimisation.

Figure 11.740: Example of final RS/CINR coverage improvement (left) and RS coverage improvement (right) You can define how the coverage analysis maps will be displayed. To define the coverage analysis map display: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 1308, right-click the Coverage Analysis folder. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears (see Figure 11.741).

1310

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.741: Defining display and threshold properties 3. Select the Display tab. On the Display tab, you can select the colour used to display initial CINR coverage improvement, final CINR coverage improvement, and both. As well, you can use the slider to adjust the Transparency. 4. Select the Thresholds tab. On the Thresholds tab, you can set the thresholds to be used for the map for the RS CINR coverage. You can use the same thresholds as you used when you calculated the optimisation, or you can set a different threshold.

11.4.6.2.3

The Change Analysis Maps

The change analysis maps allow you to analyse the changes recommended by the ACP. The change attributes are displayed on the map using a best server map, because the types of changes that ACP recommends are all related to individual cells. The best server map used is usually the initial best server map but you can use the final best server map for new sites (i.e., sites that have been added during optimisation). The following maps are available: Reconfiguration Types: In the Reconfiguration Types folder, there is a separate map for each reconfiguration option displaying the changes to the network: azimuth, mechanical tilt, and antenna. The changes are displayed for the best server zone. The maps can be displayed individually to display each reconfiguration option separately or together to display all reconfiguration options. Sector Selection Types: In the Sector Selection Types folder, there are maps to display which sites have been added or removed. These maps are only available if the site selection was activated during optimisation. Change Order: The Change Order map displays the order of changes (as displayed on the Change Details tab of the optimisations Properties dialogue). You can define the colours used to display the order of changes by right-clicking the Change Order map in the Data tab, selecting Properties from the context menu and then changing the colours on the Display tab. By displaying the Change Order map, you can see where the most important changes to be made to the network are located. Change of Electrical Tilt, Mechanical Tilt, Azimuth, Height, Pilot Power, and Change Cost: These maps show the variation of the given parameter. They can be used to see where in the network this reconfiguration option was changed. Note: The electrical tilt values are calculated using the vertical antenna pattern. The Change of Electrical Tilt map is made available even when the change was to the antenna type.

Figure 11.742: Example of electrical tilt change (left) and electrical tilt change (right)

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1311

Atoll User Manual

11.4.6.2.4

Best Server Analysis

The best server analysis maps contain maps enabling you to analyse cell-related parameters as related to the best server. The following maps are available: Initial and Final Electrical and Mechanical Tilt Values: These maps show the tilt values on the initial and final network. They can be used, for example, to identify areas with strong tilt values. Initial and Final Antenna Height: These maps show the initial and final antenna heights. Initial and Final Transmitter RS and CINR Coverage: These maps show the percentage of the best server area which is covered according to the defined threshold. The values displayed are the same as those on the Sectors tab of the optimisations Properties dialogue. You can use these maps to quickly identify the cells which potentially have poor quality. Initial and Final Overlapping Ratio: These maps show the percentage of the best server area with overlapping coverage greater than "1," i.e., with several received signals over the defined threshold.

11.4.6.2.5

Comparing Maps
You can compare the results displayed on one map with the results of another map from the same optimisation or from a different optimisation. To compare a map with a map from the same optimisation: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 1308, right-click the map you want to compare. The context menu appears. 2. From the context menu, select Compare With and then select one of the maps in the submenu. A new map is created in the Data tab and the results of the comparison are displayed in the map window. 3. ACP creates a new map in the Data tab and displays it in the map window with the pixels that are displayed on both maps or only on a single map.

Figure 11.743: Comparing two optimisation maps To compare a map with a map from a different map type or with a map from a different optimisation: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 1308, right-click the map you want to compare. The context menu appears. 2. From the context menu, select Compare With > Others. The ACP Compare Map dialogue appears (see Figure 11.744). By default, the ACP Compare Map dialogue displays only maps from the same optimisation as the map you want to compare.

Figure 11.744: The ACP Compare Map dialogue

1312

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 3. Define the maps you choose from: Show studies from Predictions folder: Select the Show studies from Predictions folder check box if you want to be able to compare with a map from a coverage prediction you have already created and calculated. Show maps from all ACP setups: Select the Show maps from all ACP setups check box if you want to be able to compare with a map from a different optimisation. Show only maps of same type: Select the Show only maps of same type check box if you want to restrict the maps displayed to maps displaying comparable information.

4. Select the map with which you want to compare the first one and click OK. ACP creates a new map in the Data tab and displays it in the map window with the pixels that are displayed on both maps or only on a single map.

Tip:

By first defining a display interval of "1" in both maps and then comparing them, the resulting comparison map will have more meaningful results. For information on defining "Changing the Display Properties of ACP Maps" on page 1313.

11.4.6.2.6

Changing the Display Properties of ACP Maps

You can define how ACP maps are displayed in the Atoll map window. You can define the colours used as well as the ranges of values on the Display tab of each maps Properties dialogue. As well, ACP allows you to display the value on each pixel in the form of a tooltip. To define the display of an ACP map: 1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation results as explained in "Viewing Optimisation Results in the Map Window" on page 1308, right-click the map whose display you want to define. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears (see Figure 11.745).

Figure 11.745: Setting the display properties for a map 3. Select the Display tab. 4. On the Display tab, you can define the following settings: Colours: For each range of values, you can click the colour button and select the colour that will be used to represent that range. Min. and Max.: You can define the minimum and maximum values that will define that range. Transparency: You can define the transparency of the map using the slider. Add to legend: You can display the range of values of the optimisation map by selecting the Add to legend. check box. Actions: You can modify the ranges of values by clicking the Actions button and selecting one of the following: Select All: Select Select All to select all the ranges on the display tab. Anything you select after that from the Actions menu (for example, Delete) will be applied to the selected ranges. Delete: Select Delete to delete the selected range or ranges. Insert Before: Select Insert Before to insert a new range before the selected range. Insert After: Select Insert After to insert a new range after the selected range Shading: Select Shading to open the Shading dialogue where you can define all the ranges by setting the first value, the last value, and the step between values, as well as the colour used for the first value and the colour used for the last value. ACP will shade the ranges in between the first and last value with a range of colours going from the first colour to the last.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1313

Atoll User Manual Save as Default: Select Save as Default to set the current settings on the display tab to the default settings. These settings can then be used for all maps of the same kind. Load from Default: Select Load from Default to change the current settings to those set as the default using Save as Default. Reset to Default: Select Reset to Default to change the current settings back to the ACP defaults. You can also use Reset to Default to return to the ACP defaults when you have created user-defined defaults using Save as Default.

You can display the value on a pixel by resting the pointer on the pixel in the map window. The value on that pixel will be displayed in a tooltip (see Figure 11.746).

Figure 11.746: Tool tip displaying ACP results on selected point

11.4.6.2.7

Exporting ACP Coverage Maps

ACP enables you to export the optimisation coverage maps as BMP files. Before you can export an optimisation coverage map, you must first select the map and define its appearance as explained in "Viewing Optimisation Results in the Map Window" on page 1308. To export an optimisation coverage map: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( 4. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation map you want to export. ) to expand the optimisation.

5. Right-click the map. The context menu appears. 6. Select Export the Coverage from the context menu. The Save As dialogue appears. 7. Enter a File name for the exported coverage map and select the format from the Save as type list. 8. Click Save. The exported coverage map is saved in the selected format. Depending on the file format selected from the Save as type list, Atoll creates an additional file in the same location containing geo-referencing information: BMP file: Atoll creates a BPW file. ArcView grid (TXT) file: Atoll creates a BPW file. BIL file: Atoll creates a HDR file. GRD or GRC file: Atoll creates a TAB file. PNG file: Atoll creates a PGW file. TIF file: Atoll creates a TFW file.

9. Atoll also creates a BPW file in the same location containing geo-referencing information.

11.4.6.3

Viewing Optimisation Results Using the Histogram

ACP can display optimisation results in the form of a histogram. The histogram is provided for quick evaluation of improvement seen across the entire range of values. This histogram displays the statistics within the focus zone if selected. If you based this optimisation on a coverage prediction, the ranges and colours defined in the selected coverage prediction will be used for the histogram, unless you have already defined display defaults for ACP, either by saving an ACP maps settings as the default or by using a configuration file. To view the results of the optimisation using a histogram: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( 3. Click the Expand button ( 4. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. ) to expand the folder of the setup containing the optimisation results you want to view. ) to expand the folder of the optimisation.

1314

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Note:

Depending on the type of optimisation results you want to view, you might need to expand additional folders.

5. Right-click the optimisation results. The context menu appears. 6. Select Histogram from the context menu. The histogram appears in a separate window with a legend on the right side.

11.5

Verifying Network Capacity

An important step in the process of creating an LTE network is verifying the capacity of the network. This is done using measurements of the strength of the reference signal levels, SS, PBCH, PDSCH, and PDCCH signal levels, and various C/(I+N) at different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: "Importing a Drive Test Data Path" on page 1315 "Displaying Drive Test Data" on page 1317 "Defining the Display of a Drive Test Data Path" on page 1317 "Network Verification" on page 1318 "Exporting a Drive Test Data Path" on page 1322 "Extracting CW Measurements from Drive Test Data" on page 1322 "Printing and Exporting the Drive Test Data Window" on page 1323.

11.5.1

Importing a Drive Test Data Path

In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In LTE networks, a cell can be identified by its physical cell ID. Therefore, you must indicate during the import process which column contains the physical cell IDs of cells.

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. Click the Data tab in the Explorer window. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the file or files you want to open. You can import one or several files. Note: If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import.

5. Click Open. The Import of Measurement Files dialogue appears. Note: Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue.

6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Configuration, select an import configuration from the Configuration list. b. Continue with step 10.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1315

Atoll User Manual

Notes: When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. In case several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.

7. Click the General tab. On the General tab, you can set the following parameters: Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document. 8. Click the Setup tab (see Figure 11.747).

Figure 11.747: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click Setup to link file columns and internal Atoll fields. The Drive Test Data Configuration dialogue appears. c. 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. Note: 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. In the Physical Cell ID Identifier box, enter a string that must be found in the column name identifying the physical cell IDs of scanned cells. For example, if the string "ID" is found in the column names identifying the

1316

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks physical cell IDs of scanned cells, enter it here. Atoll will then search for the column with this string in the column name. e. Click OK. Important: If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Configuration dialogue, Atoll should recognize all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>". 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.

9. If you wish 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 Configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atolls installation folder. 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. Notes: 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 button ( ) in front of the file in the Setup part to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Setup 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 drive test data are imported into the current Atoll document.

11.5.2

Displaying Drive Test Data

When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see the information at that location. To display information about a single drive test data point: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Select the display check box of 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 more information. Atoll displays an arrow pointing towards the serving cell (see Figure 11.749 on page 1321) in the same colour as the transmitter.

11.5.3

Defining the Display of a Drive Test Data Path

You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to define labels, tool tips and the legend. To display the Display tab of a drive test data paths Properties dialogue: 1. Click the Data tab in the Explorer window. 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. The drive test data paths properties dialogue appears.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1317

Atoll User Manual 5. Click the Display tab. Each point can be displayed by a unique attribute or according to: a text or integer attribute (discrete value) a numerical value (value interval).

In addition, you can display points by more than one criterion at a time using the Advanced option in the Display Type list. When you select Advanced from the Display Type list, the Shadings dialogue opens in which you can define the following display for each single point of the measurement path: a symbol according to any attribute a symbol colour according to any attribute a symbol size according to any attribute

You can, for example, display a signal level in a certain colour, choose a symbol type for Transmitter 1 (a circle, triangle, cross, etc.) and a symbol size according to the altitude. Notes: 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 Display if the Fast Display check box has been selected. You can sort drive test data paths in alphabetical order on the Data tab of the Explorer window by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can export the display settings of a drive test data path in a configuration file to make them available for future use. You can export the display settings or import display settings by clicking the Actions button on the Display tab of the drive test data paths Properties dialogue and selecting Export or Import from the menu.

11.5.4

Network Verification
The imported drive test data is used to verify the LTE network. To improve the relevance of the data, Atoll allows you to filter out incompatible or inaccurate points. You can then compare the drive test measurements with coverage predictions. To compare drive test data with coverage predictions, you overlay coverage predictions calculated by Atoll with the drive test data path displayed using the same parameter as that used to calculate the coverage prediction. In this section, the following are explained: "Filtering Incompatible Points Along Drive Test Data Paths" on page 1318. "Creating Coverage Predictions from Drive Test Data Paths" on page 1320. "Displaying Statistics Over a Drive Test Data Path" on page 1320 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1320. "Analysing Data Variations Along the Path" on page 1321.

11.5.4.1

Filtering Incompatible Points Along Drive Test Data Paths

When using a drive test data path, some measured points may present values that are too far outside the median values to be useful. As well, test paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from a more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder.

The context menu appears. 3. Select Filter from the context menu. The Drive Test Data Filter dialogue 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.

1318

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks To filter out incompatible points using a filter: 1. Click the Data tab in the Explorer window. 2. On the Data tab of the Explorer window, right-click the Drive Test Data on which you want to filter out incompatible points: All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder.

The context menu appears. 3. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 4. Click More. The Filter dialogue appears. 5. Click the Filter tab: a. Select a Field from the list. b. Under Values to Include, you will find all the values represented in the selected field. Select the check boxes next to the values you want to include in the filter. Click Clear All to clear all check boxes. 6. Click the Advanced tab: a. In the Column row, select the name of the column to be filtered on from the list. Select as many columns as you want (see Figure 11.748).

Figure 11.748: The Filter dialogue - Advanced tab b. Underneath the name of each column, 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 X*

Data are kept in the table only if

value equal to X (X may be a number or characters) value not equal to X (X may be a number or characters) numerical value is less than X numerical value is greater than X numerical value is less than or equal to X numerical value is greater than or equal to X text objects which contain X text objects which end with X text objects which start with X

7. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering" on page 75. 8. Click OK to apply the filter and close the dialogue. Note: The Refresh Geo Data option available in the context menu of drive test data paths enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1319

Atoll User Manual

11.5.4.2

Creating Coverage Predictions from Drive Test Data Paths

You can create the following coverage predictions for all transmitters on each point of a drive test data path: Point Signal Level Coverage by Signal Level

To create a coverage prediction along a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Study from the context menu. The Study Types dialogue appears. 5. Under Standard Studies, select Coverage by Signal Level and click OK. The Coverage by Signal Level properties dialogue appears. 6. Click the Condition tab. At the top of the Condition 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. 7. 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 7. for each new coverage prediction. 8. When you have finished creating new coverage predictions for these drive test data, right-click the drive test data. The context menu appears. 9. Select Calculations > Calculate All the Studies from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calculations in Atoll). You can display the information in these new columns in the Drive Test Data window. For more information on the Drive Test Data window, see "Analysing Data Variations Along the Path" on page 1321.

11.5.4.3

Displaying Statistics Over a Drive Test Data Path

Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific Drive Test Data path: 1. Click the Data tab in the Explorer window. 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 dialogue 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.

11.5.4.4

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. Click the Data tab in the Explorer window. 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.

1320

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 4. Select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter dialogue appears. 5. Select a transmitter from the On the Transmitter list. 6. Click the For the Fields list. The list opens. 7. Select the check box beside the field you want 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.

11.5.4.5

Analysing Data Variations Along the Path

In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point. To analyse data variations using the Drive Test Data window. 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 11.749).

Figure 11.749: The Drive Test Data window 5. Click the Display button at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 11.750).

Figure 11.750: The Drive Test Data window 6. In the Display Parameters dialogue: Select the check box next to each field you want to display in the Drive Test Data window. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1321

Atoll User Manual

Note:

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 window. 7. You can display the data in the drive test data path in the following ways: Click the values in the Drive Test Data window. Click the points on the drive test data path in the map window.

The drive test data path appears in the map window as an arrow pointing towards the best server (see Figure 11.749 on page 1321) in the same colour as the transmitter. 8. 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 dialogue. You select the value to be displayed from the right-hand list at the top of the Drive Test Data window. The values are displayed in the colour defined in the Display Parameters dialogue. 9. You can change the zoom level of the Drive Test Data window display in the Drive Test Data window in the following ways: Zoom in or out: i. Right-click the Drive Test Data window.

ii. Select Zoom In or Zoom Out from the context menu. Select the data to zoom in on: i. Right-click the Drive Test Data window on one end of the range of data you want to zoom in on.

ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data window on the other end of the range of data you want to zoom in on. iv. Select Last Zoom Point from the context menu. The Drive Test Data window zooms in on the data between the first zoom point and the last zoom point. 10. Click the data in the Drive Test Data window to display the selected point in the map window. Atoll will recentre the map window on the selected point if it is not presently visible.

Tip:

If you open the table for the drive test data you are displaying in the Drive Test Data window, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data window (see Figure 11.749 on page 1321).

11.5.5

Exporting a Drive Test Data Path

You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.

11.5.6

Extracting CW Measurements from Drive Test Data

You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears.

1322

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the Transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the For the Fields list. 6. Under CW Measurement Creation Parameters: a. Enter the Min. Number of Points to Extract per Measurement Path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured Signal Levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.

11.5.7

Printing and Exporting the Drive Test Data Window

You can print or export the contents of the Drive Test Data window using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Click the Data tab in the Explorer window. 2. Click the Expand button ( ) to expand the Drive Test Data folder.

3. Right-click the drive test data path you want to print or export. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 11.749 on page 1321). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 1321. 6. Right-click the Drive Test Data window. The context menu appears. To export the Drive Test Data window: a. Select Copy from the context menu. b. Open the document into which you want to paste the contents of the Drive Test Data window. c. Paste the contents of the Drive Test Data window into the new document. To print the Drive Test Data window: a. Select Print from the context menu. The Print dialogue appears. b. Click OK to print the contents of the Drive Test Data window.

11.6

Co-planning LTE Networks with Other Networks

Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design an LTE and a GSM network for the same area in Atoll, and then work with Atolls co-planning features to study the mutual impacts of the two networks. Important: Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other networks Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In addition, you can optimise the settings of the two networks using Atolls Automatic Cell Planning (ACP) module. In this section, the following are explained: "Switching to Co-planning Mode" on page 1324. "Working with Coverage Predictions in an Co-Planning Project" on page 1325. "Performing Inter-Technology Neighbour Allocation" on page 1328. "Creating an LTE Sector From a Sector in the Other Network" on page 1339. "Using ACP in a Co-planning Project" on page 1339. "Ending Co-planning Mode" on page 1341.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1323

Atoll User Manual

11.6.1

Switching to Co-planning Mode

Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have an LTE Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, the LTE document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Important: Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems. To switch to co-planning mode: 1. Open the main document. Select File > Open or File > New > From an Existing Database.

2. Link the other document with the open main document. a. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document. b. Select File > Link With. The Link With dialogue appears. c. Select the document to be linked. d. Click Open. The selected document is opened in the same Atoll session as the main document and the two documents are linked. The Explorer window of the main document now contains a folder named Transmitters in [linked document], where [linked document] is the name of the linked document and another folder named Predictions in [linked document]. Note: By default, only the Transmitters and Predictions folders of the linked document appear in the main document. If you want the Sites folder of the linked document to appear in the main document as well, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.

As soon as a link is created between the two documents, Atoll switches to co-planning mode and Atolls co-planning features are now available. When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll syncronises the display for the following: Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.

Displaying Both Networks in the Same Atoll Document

After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 1324, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the Explorer window of the linked document to the Explorer window of the main document (e.g., you can display GSM sites and measurement paths in an LTE document). To display sites from the linked document in the main document: 1. Click the linked documents map window. The linked documents map window becomes active and the Explorer window shows the contents of the linked document. 2. Click the Data tab of the Explorer window. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In > [main document] from the context menu, where [main document] is the name of the main document. 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.

1324

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 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 rightclicking 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 82. You can also set the tool tips to enable you to distinguish the objects and data displayed on the map. For more information on tool tips, see "Defining the Object Type Tip Text" on page 36. In order to more easily view differences between the networks, you can also change the order of the folders or items in the Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers Using the Explorer" on page 28. Figure 11.751 shows an example of LTE transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in a tool tip.

Figure 11.751: GSM and LTE Transmitters displayed on the map

11.6.2

Working with Coverage Predictions in an Co-Planning Project

Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: "Updating Coverage Predictions" on page 1325 "Analysing Coverage Predictions" on page 1326.

11.6.2.1

Updating Coverage Predictions

You can access the properties of the coverage predictions in the linked Predictions folder in the main documents Explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button ( ) in the toolbar.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1325

Atoll User Manual When you click the Calculate button, Atollfirst calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 185. If you want, you can make Atoll recalculate all path loss matrices, including valid ones, before calculating unlocked coverage predictions in the main and linked Predictions folders. To force Atoll to recalculate all path loss matrices before calculating coverage predictions: Click the Force Calculate button ( ) in the toolbar.

When you click the Force Calculate button, Atoll first removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions defined in the main and linked Predictions folders. Note: 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.6.2.2

Analysing Coverage Predictions

In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tooltips to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which studies to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28. In this section, the following are explained: "Co-Planning Coverage Analysis Process" on page 1326 "Displaying the Legend Window" on page 1327 "Comparing Coverage Prediction Results Using Tooltips" on page 1327 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 1327 "Studying Differences Between Coverage Areas" on page 1328.

11.6.2.2.1

Co-Planning Coverage Analysis Process

The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. Note: In a co-planning environment, many sites share the same antennas, using one mast for both technologies. When transmitter, remote antenna, or repeater antennas have the same co-ordinates and the same value set for the SHAREDMAST field in both coplanning documents, Atoll assumes that the antennas are shared. Atoll then automatically synchronises changes made to shared antenna parameters in one coplanning document in the other document. The shared antenna parameters include the site location (X and Y coordinates), the antenna's position relative to the site (Dx, Dy), antenna height, azimuth and mechanical tilt. The SHAREDMAST field is not available by default and must be added in order for the synchronization mechanism to operate. For information on setting up shared antenna parameter synchronisation, see the Administrator Manual.

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 (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the main document. For more information, see "Making a Coverage Prediction by Transmitter" on page 1198 and "Making a Coverage Prediction by Signal Level" on page 1197. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tool tip contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage predictions Properties dialogue. 4. Make the two new coverage predictions in the linked document accessible in the main document as described in "Displaying Both Networks in the Same Atoll Document" on page 1324.

1326

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 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 1327 and "Studying Differences Between Coverage Areas" on page 1328. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.

11.6.2.2.2

Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: 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.

11.6.2.2.3

Comparing Coverage Prediction Results Using Tooltips

You can compare coverage predictions by by placing the pointer over an area of the coverage prediction to read the information displayed in the tooltip. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Co-Planning Coverage Analysis Process" on page 1326). To get coverage prediction results in the form of tooltips: 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 tooltip appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 11.661). The tooltip for the working document is on top and the tooltip for the linked document, with the linked document identified by name is on the bottom.

Figure 11.752: Comparing coverage prediction results using tooltips

11.6.2.2.4

Comparing Coverage Areas by Overlaying Coverage Predictions

You can compare the coverage areas of the main and linked documents by overlaying the coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is dislayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 32. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1327

Atoll User Manual 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 dialogue 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 "Working with Layers Using the Explorer" on page 28.

11.6.2.2.5

Studying Differences Between Coverage Areas

You can compare coverage predictions to find differences in coverage areas. To compare coverage predictions: 1. Click the main documents map window. The main documents map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Right-click the coverage prediction of the main document you want to compare. The context menu appears. 5. Select Compare With > [linked coverage prediction] from the context menu, where [linked coverage prediction] is the linked coverage prediction you want to compare with the coverage prediction of the main document. The Comparison Properties dialogue opens. 6. Select the display parameters of the comparison and add a comment if you want. 7. Click OK. The two coverage predictions are compared and a comparison coverage prediction is added to the main documents Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 1205.

11.6.3

Performing Inter-Technology Neighbour Allocation

The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between an LTE and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to LTE cells. In this section, the following are explained: "Setting Inter-Technology Exceptional Pairs" on page 1328 "Configuring Importance Factors for Inter-Technology Neighbours" on page 1330 "Allocating Inter-Technology Neighbours Automatically" on page 1330 "Displaying Inter-Technology Neighbours on the Map" on page 1333 "Allocating and Deleting Inter-Technology Neighbours per Cell" on page 1333 "Calculating the Importance of Existing Inter-technology Neighbours" on page 1336 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 1338.

In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Co-planning Mode" on page 1324.

11.6.3.1

Setting Inter-Technology Exceptional Pairs

You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Exceptional Pairs from the context menu. The Exceptional Pairs of Inter-technology Neighbours table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list.

1328

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. d. Atoll fills the Number and Distance (m) fields automatically. In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector). You can access a cells inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cells Properties dialogue: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Double-click the row corresponding to the cell whose properties you want to access. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitters Properties dialogue.

Displaying Inter-Technology Exceptional Pairs on the Map

You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select which exceptional pair links to display: Outwards Non-Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Selecting this option displays an exceptional pair link for each transmitter/cell in the linked document that has an exceptional pair defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Forced Neighbours or Forbidden Neighbours from the menu. The exceptional pair of a cell will be displayed when you select a transmitter. 8. Click the Visual Management button ( ) in the Radio toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Visual Management button again. 9. Click a transmitter on the map to show its exceptional pair links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map.

Adding and Removing Inter-Technology Exceptional Pairs on the Map

You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-Technology Exceptional Pairs on the Map" on page 1329.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1329

Atoll User Manual To add a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set an exceptional pair. Atoll adds both transmitters to the list of inter-technology exceptional pairs of the other transmitter. To remove a symmetric forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes both transmitters from the list of inter-technology exceptional pairs of the other transmitter. To add an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set an exceptional pair. Atoll adds the reference transmitter to the list of inter-technology exceptional pairs of the other transmitter. To remove an outwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the reference transmitter from the list of inter-technology exceptional pairs of the other transmitter. To add an inwards forced or forbidden exceptional pair: Click the reference transmitter on the map. Atoll displays its neighbour relations. If the two transmitters already have a symmetric exceptional pair relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation. If there is no existing exceptional pair relation between the two transmitters, first create a symmetric exceptional pair relation between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric exceptional pair relation.

To remove an inwards forced or forbidden exceptional pair: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes the transmitter from the inter-technology exceptional pairs list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

11.6.3.2

Configuring Importance Factors for Inter-Technology Neighbours

You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Neighbours > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. Note: In a GSM project, you must select Neighbours > Configure Importance from the Transmitters folders context menu.

4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Co-site Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located on the same site as reference transmitter. The Co-site Factor will be used if you select the Force co-site transmitters as neighbours check box when performing automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Inter-Technology Neighbours Automatically" on page 1330.

5. Click OK.

11.6.3.3

Allocating Inter-Technology Neighbours Automatically

Atoll can automatically determine handover relations between networks of different technologies, for example, LTE and GSM. In this case, inter-technology handovers from LTE to GSM may occur when the LTE coverage is not continuous. The networks overall coverage is extended by an LTE-to-GSM handover. Atoll can automatically determine neighbours

1330

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks in the linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database. To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 5. Click the Inter-technology Neighbours tab. 6. Define the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. 7. Define the maximum number of inter-technology neighbours that can be allocated to a cell in the Max Number of Neighbours box. This value can be either set here for all the cells, or specified for each cell in the Cells table. 8. Clear the Use Overlapping Coverage check box in order to base the neighbour allocation on distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour allocation on coverage conditions. a. Click the Define button to change the coverage conditions for the cells in the main document. The LTE Coverage Conditions dialogue appears. In the LTE Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is a UMTS document, the UMTS Coverage Conditions dialogue appears. In the UMTS Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell. Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the best server in terms of pilot quality or a cell of the active set. Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the reference cell. DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink load for all the cells, or the downlink loads Defined per Cell. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is a CDMA document, the CDMA Coverage Conditions dialogue appears. In the CDMA Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell. Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the best server in terms of pilot quality or a cell of the active set.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1331

Atoll User Manual Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the reference cell. DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink load for all the cells, or the downlink loads Defined per Cell. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is a TD-SCDMA document, the TD-SCDMA Coverage Conditions dialogue appears. In the TD-SCDMA Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Margin: Enter the margin relative to the pilot signal level of the best server. 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 desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. e. In the % Min. Covered Area box, enter the minimum percentage of the cells coverage area that the neighbours coverage area should also cover to be considered as a neighbour. 9. Under Calculation Options, define the following: CDMA Carriers: If the linked document is a UMTS, CDMA, or TD-SCDMA document, select the carriers on which you want to run the allocation. You can choose one or more carriers; Atoll will allocate only the cells using the selected carriers as neighbours. Force co-site as neighbours: Selecting the Force co-site as neighbours check box will include the co-site transmitters/cells in the neighbour list of the LTE cell. The check box is automatically selected when the neighbour allocation is based on distance. Force exceptional pairs: Selecting the Force exceptional pairs check box will apply the inter-technology exceptional pair criteria on the neighbours list of the LTE cell. Delete existing neighbours: Selecting the Delete existing neighbours check box will delete all existing neighbours in the neighbours list and perform a clean neighbour allocation. If the Delete existing neighbours check box is not selected, Atoll keeps the existing neighbours in the list.

10. Click the Calculate button to start calculations. 11. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the names of the neighbours, the number of neighbours of each cell, and the reason they are included in the neighbours list. The reasons include:

Reason
Exceptional Pair Co-site Distance % of covered area and overlapping area Existing

Description
Neighbour relation is defined as an exceptional pair. The neighbour is located at the same site as the reference cell. The neighbour is within the maximum distance from the reference cell. Neighbour relation that fulfils coverage conditions. The neighbour relation existed before running the automatic allocation.

When
Force exceptional pairs is selected Force co-site as neighbours is selected Use Coverage Overlapping is not selected Use Coverage Overlapping is selected Reset is not selected

12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: Click Compare. The list of automically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: The document name and the neighbour allocation type, The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations,

1332

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations, The number of existing neighbour relations (existing neighbour relations that are also proposed in the automatic allocation results) and the list of these relations.

13. Click the Commit button. The allocated neighbours are saved in the Intra-technology Neighbours tab of each cell. 14. Click Close.

11.6.3.4

Displaying Inter-Technology Neighbours on the Map

You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Click the main documents map window. 2. Click the arrow ( ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

3. Select Display Options from the menu. The Visual Management dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select the neighbour links to display: Outwards Non-Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines. ) next to the Visual Management button ( ) in the Radio toolbar. A menu appears.

6. Click the arrow (

7. Select Neighbours as the type of neighbour links to display. 8. Click the Visual Management button ( ) in the Radio toolbar. Neighbours are now displayed on the map. Neighbours and displayed until you click the Visual Management button again. 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31). If you select the Display Links check box under Inter-technology Neighbours, Atoll displays both inter-technology and intra-technology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.

11.6.3.5

Allocating and Deleting Inter-Technology Neighbours per Cell

Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-tech-

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1333

Atoll User Manual nology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Intertechnology Neighbours table. This section explains the following: "Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1334. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 1334. "Allocating and Removing Inter-Technology Neighbours on the Map" on page 1335.

Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Cells tab of the transmitters Properties dialogue: 1. On the main documents map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitters Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cells Properties dialogue appears. 5. Click the Inter-Technology Neighbours tab. 6. If desired, you can enter the Maximum Number of Neighbours. 7. To allocate a new neighbour: a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon ( ). b. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, and sets the Type to "manual." 8. To create a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 9. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the neighbour in the Neighbour column. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 10. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. 11. Click OK. In GSM, the inter-technology neighbours tab is available in each transmitters Properties dialogue.

Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table

To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Inter-technology Neighbours from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. To allocate an inter-technology neighbour: a. In the row marked with the New Row icon ( b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. ), select a reference cell in the Cell column.

1334

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Type to "manual." 7. To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. 8. To make several neighbour relations symmetric: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Symmetrise from the context menu. 9. To take all exceptionnal pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. Note: You can add or delete either forced neighbours or forbidden neighbours using the Exceptional Pairs of Inter-Technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu.

10. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. 11. To delete several symmetric neighbour relations: a. Click in the left margin of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. a. Right-click the Neighbours table. The context menu appears. b. Select Delete Link and Symmetric Relation from the context menu. 12. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector).

Allocating and Removing Inter-Technology Neighbours on the Map

You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-Technology Neighbours on the Map" on page 1333. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1335

Atoll User Manual T remove an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the list of inter-technology neighbours of the other transmitter. To add an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. There can be two cases: If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.

To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the inter-technology neighbours list of the other transmitter. Note: When there is more than one cell on the transmitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see "Selecting One of Several Transmitters" on page 31).

11.6.3.6

Calculating the Importance of Existing Inter-technology Neighbours

After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing inter-technology neighbours: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Cells > Neighbours > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. Note: In a GSM project, you must select Neighbours > Calculate Importance from the Transmitters folders context menu.

5. Select the Inter-technology Neighbours tab. 6. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance. 7. Clear the Use Overlapping Coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour importance calculation on coverage conditions. 8. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for cells in the main document. The LTE Coverage Conditions dialogue appears. In the LTE Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the reference signal level of the best server. The reference signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. If the linked document is a GSM document, the GSM Coverage Conditions dialogue appears. In the GSM Coverage Conditions dialogue, you can change the following parameters:

1336

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM transmitter. Margin: Enter the margin relative to the BCCH signal level of the best server. The BCCH signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is a UMTS document, the UMTS Coverage Conditions dialogue appears. In the UMTS Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell. Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the best server in terms of pilot quality or a cell of the active set. Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the reference cell. DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink load for all the cells, or the downlink loads Defined per Cell. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is a CDMA document, the CDMA Coverage Conditions dialogue appears. In the CDMA Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Min. Ec/Io: Enter the minimum Ec/Io which must be provided by the reference cell. Ec/Io Margin: Enter the Ec/Io margin relative to the Ec/Io of the best server. The reference cell is either the best server in terms of pilot quality or a cell of the active set. Max. Ec/Io: Select the Max. Ec/Io option and enter the maximum Ec/Io which must not be exceeded by the reference cell. DL Load Contributing to Io: You can select whether Atoll should use a Global Value (% Pmax) of the downlink load for all the cells, or the downlink loads Defined per Cell. Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

If the linked document is a TD-SCDMA document, the TD-SCDMA Coverage Conditions dialogue appears. In the TD-SCDMA Coverage Conditions dialogue, you can change the following parameters: Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell. Margin: Enter the margin relative to the pilot signal level of the best server. 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 desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.

d. Click OK to save your modifications and close the Coverage Conditions dialogue. 9. If you cleared the Use Overlapping Coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. Note: You can use many of Atolls table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 53. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.

10. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1337

Atoll User Manual Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. Cell: The name of the reference cell. Neighbour: The neighbour of the reference transmitter. Importance (%): The importance as calculated with the options selected in step 4. Cause: The reason Atoll has calculated the value in the Importance column. Co-site Symmetry Coverage

Distance: The distance in kilometres between the reference cell and the neighbour.

11. Click Close. The importance values and the reasons for allocation are automatically committed in the Neighbours table when you close the dialogue.

11.6.3.7

Checking the Consistency of the Inter-technology Neighbour Plan

You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Cells > Neighbours > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab. 5. Define the parameters of the audit: Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want 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 the Full Lists check box if you want 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 the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have nonsymmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.

6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited. Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax: |CELL|

Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax: |CELL| |NUMBER| |MAX NUMBER|

Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax: Note: |CELL| |NUMBER| |MAX NUMBER| If the field Max number of inter-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.

Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

1338

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR|

Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|

Distance Between Neighbours > Y: X; total number of neighbours existing in the audited neighbour plan that are located at a distance greater than Y. Syntax: |CELL| |NEIGHBOUR| |DISTANCE|

11.6.4

Creating an LTE Sector From a Sector in the Other Network

You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main documents map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new LTE transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main documents map window. 2. Click the Data tab of the Explorer window. 3. Right-click the Transmitters folder of the main document. The context menu appears. 4. Select Apply Current Configuration from the context menu.

Figure 11.753: New sector Before and after applying the configuration

11.6.5

Using ACP in a Co-planning Project

Atoll ACP enables you to automatically calculate the optimal network settings in terms of network coverage and capacity in co-planning projects where networks using different technologies, for example, LTE and GSM, must both be taken into consideration. When you run an optimisation setup in a co-planning environment, you can display the sites and transmitters of both networks in the document in which you will run the optimisation process, as explained in "Switching to Co-planning Mode" on page 1324. While this step is not necessary in order to create a co-planning optimisation setup, it will enable you to visually analyse the changes to both networks in the same document. Afterwards you can create the new optimisation setup, but when creating an optimisation setup in a co-planning environment, you can not run it immediately; you must first import the other network into the ACP setup. This section explains how to use ACP to optimise network settings in a co-planning project: "Creating a New Co-planning Optimisation Setup" on page 1339 "Importing the Other Network into the Setup" on page 1340.

11.6.5.1

Creating a New Co-planning Optimisation Setup

Once you have displayed both networks in the main document as explained in "Switching to Co-planning Mode" on page 1324, you can create the new co-planning optimisation setup.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1339

Atoll User Manual To create a new co-planning optimisation setup: 1. Click the main documents map window. 2. Click the Data tab in the Explorer window. 3. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 4. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation process. For information on the parameters available, see "Defining Optimisation Parameters" on page 1277. 5. After defining the optimisation setup, click the Create Setup button to save the defined optimisation. The optimisation setup has now been created. The next step is to add the GSM network to the ACP optimisation setup you have just created.

11.6.5.2

Importing the Other Network into the Setup

Once you have created the co-planning optimisation setup, you must import the linked network. To import the linked network: 1. Click the main documents map window. 2. Click the Data tab in the Explorer window. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 1339. 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.

ACP displays a dialogue enabling you to define which traffic will be used for the document you are importing. 6. Under Traffic generated from, select one of the following: Uniform traffic: Select Uniform traffic if the traffic in the document you are importing is uniform. Maps based on traffic densities: If the traffic is to be generated from traffic density maps, select Maps based on traffic densities and define the following parameters: When importing a GSM project: Under Traffic parameters, define whether traffic weighting should be applied to Cell Dominance or the BCCH or both by selecting the appropriate check boxes. When importing an LTE project: Under Traffic parameters, define whether traffic weighting should be applied to the RS CINR or the RS Coverage or both by selecting the appropriate check boxes. When importing either a GSM project or an LTE project: Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Terminal, and select a Traffic Density File by clicking the Browse button ( ).

Following traffic maps: Select Following traffic maps if you have traffic maps available and then select the check boxes corresponding to the traffic maps you want to use.

7. Click OK. The setup has been modified to include the linked network. You can modify the parameters for the optimisation setup by right-clicking it on the Data tab of the Explorer window and selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation Parameters" on page 1277. After defining the co-planning optimisation setup: Click the Run button to run the optimisation immediately. For information on running the optimisation, see "Running an Optimisation Setup" on page 1299. For information on the optimisation results, see "Viewing Optimisation Results" on page 1301. Click the Create Setup button to save the defined optimisation to be run later.

1340

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

11.6.6

Ending Co-planning Mode

once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents. To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select File > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.

11.7

Advanced Configuration
The following sections describe different advanced parameters and options available in the LTE module that are used in coverage predictions as well as Monte Carlo simulations. In this section, the following advanced configuration options are explained: "Defining Frequency Bands" on page 1341. "The Global Transmitter Parameters" on page 1342. "Defining LTE Radio Bearers" on page 1344. "Defining LTE Quality Indicators" on page 1344. "Defining LTE Equipment" on page 1345. "Defining LTE Schedulers" on page 1347. "Multiple Input Multiple Output Systems" on page 1349. "Defining the Minimum Signal to Thermal Noise Threshold" on page 1350. "Modelling Shadowing" on page 1350. "Modelling Inter-Technology Interference" on page 1351. "Listing LTE Frame Details" on page 1352.

11.7.1

Defining Frequency Bands

To define frequency bands: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Frequencies > Bands from the context menu. 4. In the table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each frequency band, enter: Name: Enter a name for the frequency band, for example, "1.9 GHz - 5 MHz." Each LTE frequency band has a specific channel bandwidth. Mentioning the channel bandwidth in the frequency band name is a good approach. This name will appear in other dialogues when you select a frequency band. Channel Width (MHz): Enter the channel bandwidth for each channel 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. Note: The relationship between the frequency band (spectrum), the channel width, and the channel numbers can be defined as: Frequency Band Width = Channel Bandwidth x (Last Channel + 1 - First Channel) So, if you have a frequency band of 15 MHz, and you are deploying your network with 3 MHz allocated to each cell, you can find the First and Last Channel numbers by: Last Channel - First Channel = (Frequency Band Width/Channel Bandwidth) - 1 If you plan to keep the First Channel number = 0, for our example: Last Channel = (15 MHz/3 MHz) - 1 = 4

Excluded Channels: Enter the channel numbers which do not constitute the frequency band. 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. 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. Number of Frequency Blocks (RB): Enter the number of frequency blocks (i.e., the number of resource block widths in the frequency domain) used for the channel bandwidth.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1341

Atoll User Manual 5. When you have finished adding frequency bands, click Close. You can also access the properties dialogue of each individual frequency band by clicking the Properties button.

11.7.2

The Global Transmitter Parameters

Atoll allows you to set network level parameters which are common to all the transmitters and cells in the network. These parameters are used in coverage predictions as well as during Monte Carlo simulations by the radio resource management and scheduling algorithms. This section explains the options available on the Global Parameters tab of the Transmitters Properties dialogue, and explains how to access the tab: "The Options on the Global Parameters Tab" on page 1342. "Modifying Global Transmitter Parameters" on page 1343.

11.7.2.1

The Options on the Global Parameters Tab

The global LTE parameters include: 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 cyclix prefix types: normal and extended. PDCCH Overhead: The Physical Downlink Control Channel (PDCCH) can take up to 3 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. Amounts of resources corresponding to different signals and channels in LTE can be calculated and displayed in Atoll. For more information, see "Listing LTE Frame Details" on page 1352. Switching Point Periodicity (TDD only): For the TDD LTE frame, the switching point can either be after each half-frame or each frame. You can select the frame configuration, i.e., the configuration of uplink and downlink subframes in a frame, for each cell according to the selected switching point periodicity. Reference Signal EPRE: The reference signal EPRE can be either calculated automatically using the maximum power and the offsets for different downlink channels defined per cell, or entered per cell by the user. Serving (reference) cell layer selection method: The reference cell layer selection method is used for determining the reference cell in case of transmitters supporting more than one cell. The best serving transmitter for a pixel, subscriber, or mobile is determined according to the received reference signal level from the cell with the highest reference signal power. If more than one cell of the same transmitter cover the pixel, subscriber, or mobile, the reference cell is determined according to the selected method: Random: In coverage prediction calculations and in calculations on subsriber lists, the cell with the lowest layer is selected as the serving (reference) cell. In Monte Carlo simulations, a random cell is selected as the serving (reference) cell. Distributive: In coverage prediction calculations and in calculations on subsriber lists, the cell with the lowest layer is selected as the serving (reference) 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 lowest cell layer, the 2nd mobile to the second lowest cell layer, and so on. Min DL Traffic Load: (Not implemented yet) The cell with the lowest downlink traffic load is selected as the serving (reference) cell. If more than one cell has the same lowest downlink traffic load, the first cell among all such cells is selected. During Monte Carlo simulations, as the cell traffic loads may vary, the serving cell for mobiles may also change. Min UL Traffic Load: (Not implemented yet) The cell with the lowest uplink traffic load is selected as the serving (reference) cell. If more than one cell has the same lowest uplink traffic load, the first cell among all such cells is selected. During Monte Carlo simulations, as the cell traffic loads may vary, the serving cell for mobiles may also change.

The Min DL Traffic Load and Min UL Traffic Load options model load balancing between cells. In coverage predictions as the probe mobile selects the least loaded cell, i.e., tries to keep the traffic load balanced between cells of the transmitter. Instead of loading already loaded cells even more, the eNode-B chooses to load the least loaded among them. When using either the Random or the Distributive cell layer selection method, the reference cell once assigned to a mobile does not change during Monte Carlo simulations. 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.

1342

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Figure 11.754 and Figure 11.755 give examples of downlink and uplink FDD resource blocks for the single antenna case using the normal cyclic prefix.

Figure 11.754: LTE downlink resource blocks

Figure 11.755: LTE uplink resource blocks

11.7.2.2

Modifying Global Transmitter Parameters

You can change global transmitter parameters on the Global Parameters tab of the Transmitters Properties dialogue. To set the network level parameters: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Global Parameters tab. In this tab you can set the frame structure parameters. Frame Structure: In this section, you can modify the Default Cyclic Prefix, the PDCCH Overhead, the PUCCH Overhead, and, for TDD networks, the Switching Point Periodicity.

5. Click the Advanced button. The Advanced Parameters dialogue appears. 6. In the Advanced Parameters dialogue, you can set: Downlink Transmit Power Calculation: In this section (see Figure 11.756), you can select whether the downlink reference signal EPRE is calculated from the maximum power and the EPRE offsets defined per cell, or is entered by the user directly per cell. Serving Cell Layer Selection: In this section, you can choose the serving cell layer selection Method. Uplink Power Control: In this section, you can enter the uplink power control Margin.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1343

Atoll User Manual

Figure 11.756: LTE Global Parameters 7. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.

11.7.3

Defining LTE Radio Bearers

LTE radio bearers carry the data in the uplink as well as in the downlink. Note: In the Atoll LTE module, a "bearer" refers to a combination of MCS, i.e., modulation and coding schemes.

The LTE Bearers table lists the radio bearers available in Atoll by default. You can add, remove, and modify bearer properties, if you wish. To define LTE bearers: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > LTE Bearers from the context menu. The LTE Bearers table appears. 4. In the table, enter one bearer per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each LTE bearer, enter: 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 LTE equipment. Name: Enter a name for the bearer, for example, "16QAM 3/4." This name will appear in other dialogues 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 1355. 5. Click the Close button ( ) to close the LTE Bearers table.

11.7.4

Defining LTE Quality Indicators

Quality indicators depict the coverage quality at different locations. The quality indicators table lists the quality indicators available in Atoll by default. You can add, remove and modify quality indicators, if you wish. To define quality indicators: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Quality Indicators from the context menu. The Quality Indicators table appears. 4. In the table, enter one quality indicator per row. For information on working with data tables, see "Working with Data Tables" on page 53. For each quality indicator, enter: Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in other dialogues and results. Used for Data Services: Select this check box to indicate that this quality indicator can be used for data services.

1344

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Used for Voice Services: Select this check box to indicate that this quality indicator can be used for voice services. ) to close the Quality Indicators table.

5. Click the Close button (

11.7.5

Defining LTE Equipment

LTE equipment model the reception characteristics of cells and user terminals. Bearer selection thresholds and channel quality indicator graphs are defined in LTE equipment. To create a new piece of LTE equipment: 1. Click the Data tab in the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Equipment > LTE Equipment from the context menu. The LTE Equipment table appears. 4. In the LTE Equipment table, each row describes a piece of equipment. For the new piece of equipment you are creating, enter its name. 5. Double-click the equipment entry in the LTE Equipment table once your new equipment has been added to the table. The equipments Properties dialogue opens. The Properties dialogue has the following tabs: Bearer Selection Thresholds: In this tab (see Figure 11.757), 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 carrierto-interference-and-noise ratio is higher than its selection threshold. For more information on bearers and mobility types, see "Defining LTE Radio Bearers" on page 1344 and "Modelling Mobility Types" on page 1211, respectively.

Figure 11.757: LTE Equipment - Bearer Selection Thresholds i. Click the Best Bearer Thresholds button. The C/(I+N) Thresholds (dB) dialogue appears (see Figure 11.758).

ii. Enter the graph values. iii. Click OK.

Figure 11.758: C/(I+N) Thresholds (dB) dialogue For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresholds" on page 1354. For converting receiver equipment sensitivity values (dBm) into bearer selection thresholds, see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1355.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1345

Atoll User Manual Quality Graphs: On this tab (see Figure 11.759), you can modify the Quality Indicator Graphs for different bearers for different mobility types. These graphs depict the behaviour of various quality indicators under different radio conditions. For more information on bearers, quality indicators, and mobility types, see "Defining LTE Radio Bearers" on page 1344, "Defining LTE Quality Indicators" on page 1344, and "Modelling Mobility Types" on page 1211, respectively.

Figure 11.759: LTE Equipment - Quality Indicator Graphs i. Click the Quality Graph button. The Quality Graph dialogue appears (see Figure 11.760).

ii. Enter the graph values. iii. Click OK.

Figure 11.760: Quality Indicator Graph dialogue MIMO: On this tab (see Figure 11.761), 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 capacity gain due to spatial multiplexing is the increase in channel capacity compared to a SISO system. For more information on bearers and mobility types, see "Defining LTE Radio Bearers" on page 1344 and "Modelling Mobility Types" on page 1211, respectively. For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on page 1349.

Note:

No MIMO gain (diversity, SU-MIMO, and MU-MIMO) is applied if N Ant = N Ant = 1 .

TX

RX

1346

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.761: LTE Equipment - MIMO gains i. Enter the Diversity Gain for a combination of Mobility, Radio Bearer Index, Max BLER, Number of Transmission Antenna Ports, and Number of Reception Antenna Ports.

ii. Click the Max MIMO Gain Graphs button to open the Max MIMO Gain dialogue for a combination of Mobility, Radio Bearer Index, Max BLER, Number of Transmission Antenna Ports, and Number of Reception Antenna Ports (see Figure 11.762). iii. Enter the graph values. iv. Click OK. You can define the diversity and SU-MIMO gains for a specific 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.

Figure 11.762: Max MIMO Gain dialogue 6. Click OK. The Properties dialogue closes. The settings are stored. 7. Click the Close button ( ) to close the LTE Equipment table.

11.7.6

Defining LTE Schedulers

In Atoll, schedulers perform the selection of users for resource allocation, the radio resource allocation and management according to the QoS classes of the services being accessed by the selected users. The scheduling process is composed of the following three steps: 1. Selection of users for resource allocation: The Max Number of Users defined for each cell is the maximum number of users that the cells scheduler can work with simultaneously. At the start of the scheduling process, the scheduler keeps only as many users as the maximum number defined for resource allocation. If no limit has been set, all the users generated during the Monte Carlo simulations for this cell are considered, and the scheduler continues to allocate resources until there are no more resources to allocate. 2. Resource allocation for supporting the Min Throughput Demands: The minimum throughput demand is the guaranteed bit rate of a service. If there are enough resources available, the scheduler may be able to allocate

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1347

Atoll User Manual the exact amount of resources required to fully support the minimum throughput demands, otherwise 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. In order to be connected, users who are active in downlink and uplink must be able to get their minimum throughput in both directions. If a user who is 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 multi-user 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 all the resources they require. The end result of this scheduling method is that the aggregate 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 schedulers available in Atoll by default. You can add, remove, and modify scheduler properties, if you wish. To define LTE schedulers: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > Schedulers from the context menu. The Schedulers table appears. 4. In the table, enter one scheduler per row. For information on working with data tables, see "Working with Data Tables" on page 53. 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 voice-type services. Target Throughput for Data Services: Select the throughput that the scheduler will target to satisfy for all data-type 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 LTE 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 LTE 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 LTE equipment. 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. The definition of the lowest bearer depends on the Bearer Selection Criterion, i.e., lowest index, lowest peak RLC throughput, or lowest effective RLC throughput. - 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.

1348

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks When 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. You can open a schedulers properties dialogue by double-clicking the corresponding row in the Schedulers table. In the properties dialogue, a MUG tab is available for Proportional Fair schedulers. In the MUG tab, you can enter the throughput gains due to multi-user diversity for different mobility types and the maximum PDSCH and PUSCH C/(I+N) above which the gains are not applied to throughput. 5. Click the Close button ( ) to close the Schedulers table.

11.7.7

Multiple Input Multiple Output Systems

Multiple Input Multiple Output (MIMO) systems use different transmission and reception diversity techniques. MIMO diversity systems can roughly be divided into the following types, all of which are modelled in Atoll:

Transmit and Receive Diversity

Transmit or receive diversity uses more than one transmission or reception antenna to send or receive more than one copy of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining) at the receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, diversity improves the C/(I+N) at the receiver. It is often used for the regions of a cell that have bad C/(I+N) conditions. In Atoll, you can set whether a cell supports transmit or receive diversity by selecting the corresponding diversity support modes in cell properties (see "Cell Description" on page 1176). Diversity gains on downlink and uplink can be defined in the LTE equipment for different numbers of transmission and reception antenna ports, mobility types, bearers, and maximum BLER. For more information on uplink and downlink diversity gains, see "Defining LTE Equipment" on page 1345. Additional gain values can be defined per clutter class. For information on setting the additional uplink and downlink diversity gain for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 121. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell that supports transmit or receive diversity, will benefit from the downlink or uplink diversity C/(I+N) gains.

Single-User MIMO or Spatial Multiplexing

SU-MIMO uses more than one transmission antenna to send different signals (data streams) on each antenna. The receiver can also have more than one antenna for receiving different signals. Using spatial multiplexing with M transmission and N reception antenna ports, the throughput over the transmitter-receiver link can be theoretically increased M or N times, depending on which is smaller, M or N. 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 multiplxing) or simply MIMO. In Atoll, you can set whether a cell supports SU-MIMO by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 1176). SU-MIMO capacity gains can be defined in the LTE 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 Equipment" on page 1345. 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 C/(I+N). As SU-MIMO improves the channel capacity or throughputs, the PDSCH C/(I+N) of a user is first determined. Once the PDSCH 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 121. 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 C (I + N) TX RX Where CC MIMO = Min ( N Ant, N Ant ) Log 2 1 + ------------------------------------------ is the channel capacity at a given C/(I+N) for a MIMO TX RX Min ( N Ant, N Ant ) system 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.
TX RX

Adaptive MIMO Switch

This is a technique for switching from SU-MIMO to transmit or receive diversity as the reference signal conditions get worse than a given threshold. AMS can be used in cells to provide SU-MIMO gains to users that have better reference

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1349

Atoll User Manual signal C/N conditions than a given AMS threshold, and diversity gains to users that have worse reference signal C/N conditions than the threshold. AMS provides the optimum solution using transmit and receive diversity and SU-MIMO features to their best. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell that supports AMS, will benefit from the gain to be applied, diversity or SU-MIMO, depending on the users reference signal C/N and the AMS threshold defined in the cell properties. Diversity gain is applied to the users PDSCH C/(I+N) if the users reference signal C/N is less than the AMS threshold, and SU-MIMO is used if the reference signal C/N is higher than the AMS threshold.

Multi-User MIMO or Collaborative MIMO

MU-MIMO (Multi-User MIMO) or Collaborative MIMO is a technique for spatially multiplexing more than one user who have good enough radio conditions at their locations. This technique is used in uplink so that a cell with more than one reception antenna port can receive uplink transmissions from two different users over the same frequency-time allocation. This technique provides considerable capacity gains in uplink, and can be used with single-antenna user equipment, i.e., it does not require more than one antenna port at the user equipment as opposed to SU-MIMO, which only provides considerable gains with more than one antenna at the user equipment. In Atoll, you can set whether a cell supports MU-MIMO in uplink by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 1176). MU-MIMO capacity gains result from the scheduling and RRM process. Using MU-MIMO, schedulers are able to allocate resources over two spatially multiplexed parallel frames in the same frequency-time resource allocation plane. MU-MIMO can only work under good radio conditions and if the cell has more than one reception antenna port. Therefore, the reference signal C/N must be higher than the MU-MIMO threshold defined by cell in order for the scheduler to be able to multiplex users in uplink. During the calculations of Monte Carlo simulations in Atoll, each new user connected to the first antenna port creates virtual resources available on the second antenna port. These virtual resources can then be allocated to a second user connected to the second antenna port without increasing the overall load of the cell. In this way, each new mobile consumes the virtual resources made available be the previous mobile, and may make new virtual resources available on the other antenna port. The MU-MIMO capacity gain resulting from this uplink collaborative multiplexing is simply the ratio of the traffic loads of all the mobiles connected to both parallel frames in uplink to the uplink traffic load of the cell. MU-MIMO is only possible for mobiles that support MIMO and at which the reference signal C/N is greater than the MU-MIMO threshold defined for their serving cell. The MU-MIMO capacity gain can be defined per cell by the user or it can be an output of the Monte Carlo simulations. This gain is used during the calculation of uplink throughput coverage predictions. The channel throughput is multiplied by this gain for pixels where MU-MIMO is used as the diversity mode.

11.7.8

Defining the Minimum Signal to Thermal Noise Threshold

In Atoll, you can define a limit on the received signal level with respect to the thermal noise level. This value is used by Atoll to limit the input of interferers in calculations. The performance of C/(I+N)-based coverage predictions, interference matrices calculations, and Monte Carlo simulatinos can be improved by setting a high value of the minimum signal to thermal noise threshold. This value is used as a filter criterion on interferers. Atoll will discard all interferers with a signal to thermal noise level lower than this value. To define the minimum signal to thermal noise threshold: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions Properties dialogue appears. 4. Click the Predictions tab. 5. Under Calculation Limitation, enter a Min Interferer C/N Threshold in dB. 6. Click OK.

11.7.9

Modelling Shadowing
Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be better and in 50% of the measured cases, the result will be worse. Atoll uses a model standard deviation for the clutter class with the defined cell edge coverage probability to model the effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. 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.

1350

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks 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 121. Shadowing can be taken into consideration when Atoll calculates the signal level and C/(I+N) for: A point analysis (see "Making a Point Analysis to Study the Profile" on page 1187) A coverage prediction (see "Studying Signal Level Coverage" on page 1189).

Atoll always takes shadowing into consideration when calculating a Monte Carlo-based LTE simulation. 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 C/(I+N) based coverage predictions. You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter Class" on page 1351.

11.7.9.1

Displaying the Shadowing Margins per Clutter Class

To display the shadowing margins per clutter class: 1. Click the Data tab in the Explorer window. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears (see Figure 11.763). 4. You can set the following parameters: Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin: From 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.

5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.

Figure 11.763: The Shadowing Margins dialogue

11.7.10

Modelling Inter-Technology Interference

Analyses of LTE networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in an LTE network. Atoll can take into account interference from coexisting networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modeled in Atoll: Interference received by mobiles on the downlink: Interference can be received by mobiles in 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) may be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. Atoll Interference from external mobiles (also called uplink-to-downlink interference) may be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your LTE 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 LTE 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 Description" on page 1176.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1351

Atoll User Manual

Figure 11.764: Interference received by mobiles on the downlink 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) may 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) may be created by the use of same or nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possible to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the Inter-technology UL Noise Rise definable for each cell in the LTE network. This noise rise is taken into account in uplink interference-based calculations in the simulation. It is not considered in predictions. For more information on the Inter-technology UL Noise Rise, see "Cell Description" on page 1176.

Figure 11.765: Interference received by cells on the uplink

11.7.11

Listing LTE Frame Details

Atoll can calculate and display the numbers of resource elements corresponding to different LTE physical signals and logical channels in downlink and uplink. To calculate and list details on LTE frames: 1. Click the Data tab of the Explorer window. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Frame Details from the context menu. The Frame Details dialogue appears. The Frame Details command is also available in the context menu of a transmitter and a group of transmitters. The Frame Details dialogue lists only the cells belonging to the transmitter or folder from which it is run. Filters are also taken into account. 4. Click the Downlink tab. 5. Under Display, you can select to display the Numbers of Resource Elements and the Percentages of Resource Elements belonging to the downlink physical signals and logical channels. 6. Click Calculate. Atoll calculates the numbers of resource elements corresponding to different parts of the downlink LTE frame for each listed cell. The following information is available: Total: The total number of resource elements in the downlink subframes. RS Transmitted: 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.

1352

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks RS Reserved: The number and percentage of resource elements reserved for the cell specific reference signals. SSS: The number and percentage of resource elements belonging to the SSS. PSS: The number and percentage of resource elements belonging to the PSS. PBCH: The number and percentage of resource elements belonging to the PBCH. PDCCH+PCFICH+PHICH: The number and percentage of resource elements belonging to the PDCCH (which is considered to include the PCFICH and PHICH). PDSCH: The number and percentage of resource elements remaining in the PDSCH after removing the reference signals, synchronisation signals, and control channel overheads.

7. Click the Uplink tab. 8. Under Display, you can select to display the Numbers of Resource Elements and the Percentages of Resource Elements belonging to the uplink physical signals and logical channels. 9. Click Calculate. Atoll calculates the numbers of resource elements corresponding to different parts of the uplink LTE frame for each listed cell. The following information is available: Total: The total number of resource elements in the uplink subframes. DRS: The number and percentage of resource elements belonging to the DRS. SRS: The number and percentage of resource elements belonging to the SRS. PUCCH: The number and percentage of resource elements belonging to the PUCCH. PUSCH: The number and percentage of resource elements remaining in the PUSCH after removing the reference signals and control channel overheads

10. Click Close. The Frame Details dialogue window closes. For more information on the LTE logical and transport channels, see "Glossary of LTE Terms" on page 1357. For more information on the LTE frame structure, see "The Global Transmitter Parameters" on page 1342.

11.8

Tips and Tricks

The following tips and tricks are described below: "Obtaining User Throughputs for All the Subscribers of a Subscriber List" on page 1353. "Working With User Densities Instead of User Profiles" on page 1354. "Limiting the Coverage Range of Transmitters in Order to Avoid Uplink-to-Downlink Interference in TDD Networks" on page 1354. "Bearer Selection Thresholds" on page 1354. "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1355. "Relation Between Bearer Efficiency And Spectral Efficiency" on page 1355. "Modelling VoIP Codecs" on page 1356. "Working with EARFCNs instead of Channel Numbers" on page 1356. "Modelling the Co-existence of Networks" on page 1357.

Obtaining User Throughputs for All the Subscribers of a Subscriber List

Important: This procedure is only recommended if you have a correct subscriber list and have complete knowledge of the services they use. Atoll generates a realistic user distribution containing active users only during Monte Carlo simulations. The status of these users is determined through the users service usage parameters defined in the user profile. In Atoll, all the subscribers have a user profile assigned to them. During Monte Carlo simulations based on subscriber lists, Atoll determines active users from all the users in the subscriber list. If you perform calculations on subscriber lists, Atoll calculates the channel throughputs and not the user throughputs as resource allocation is not performed in these calculations. However in the simulations, RRM and resource allocation is carried out user throughputs can be determined. If you want to determine user level throughputs for all the subscribers in a subscriber list, you can run a simulation on this subscriber list after modifying the user profiles assigned to all the subscribers such that all the subscribers have an activity probability of 100 %. 1. Create a subscriber list with subscribers having an activity probability of 100 %: a. Create as many user profiles as there are services used by the subscribers in the list. b. Assign only one service to each user profile. c. Assign the following service usage parameters to the user profiles that you create: i. For Voice services, set: Calls/Hour = 1. Duration (sec.) = 3600.

ii. For Data services: Calls/Hour = 1. UL Volume (KBytes) = UL Average Throughput x 3600/8. DL Volume (KBytes) = DL Average Throughput x 3600/8. Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average requested throughputs, respectively, of the service mentioned in the user profile. Forsk 2010 Unauthorized reproduction or distribution of this document is prohibited

1353

Atoll User Manual d. Assign these user profiles to subscribers in the subscriber list. 2. Create a simulation based on this subscriber list only. The simulation results will contain all the subscribers in the subscriber list with their respective user throughputs determined by Atoll after the scheduling process.

Working With User Densities Instead of User Profiles

If you do not currently have reliable LTE multi-service traffic, you can provide Atoll with user density information per service, for example, traffic data from adapted GSM Erlang maps. In this case, you do not have to create user profiles. As well, Atoll does not have to determine the user activity probabilities to create traffic scenarios during simulations. The distribution of traffic during simulations will only depend on the user densities per service. If you know the user densities for each service, you can set user activity probabilities to 100 % in your LTE document, as shown below: 1. For Voice services, set: Calls/Hour = 1. Duration (sec.) = 3600.

2. For Data services: Calls/Hour = 1. UL Volume (KBytes) = UL Average Throughput x 3600/8. DL Volume (KBytes) = DL Average Throughput x 3600/8. Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average requested throughputs, respectively, of the service defined in the user profile. The above settings will set the user activity probabilities to 100 %. If you create a traffic map based on user profile environments, 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. This way, you can know the exact number of active users and their services generated during the simulations beforehand. This procedure should only be used when appropriate traffic data is not available.

Limiting the Coverage Range of Transmitters in Order to Avoid Uplink-to-Downlink Interference in TDD Networks
You can define a maximum coverage range for all the transmitters in your network by entering a valid range as the Max Range parameter. To define the Max Range parameter: 1. Right-click the Predictions folder. The context menu appears. 2. Select Properties from the context menu. The Predictions folders properties dialogue appears. 3. Select the System tab. 4. Select the Max Range check box. The Max Range field in enabled. 5. Enter the Max Range of the network. 6. Click OK. For TDD networks, you can determine the maximum coverage range that the sectors of your LTE network should have from the cyclic prefix duration and use this range as the Max Range parameter. You can calculate the maximum system range from the cyclic prefix as follows: Max Range (m) = Cyclic Prefix (in ms) x 300000/2

Bearer Selection Thresholds

The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll have been extracted from the 3GPP TR 36.942 V8.0.0 (see Figure 11.766). These values correspond to to an ideal (AWGN) radio channel, and are too optimistic compared to real radio channels. It is recommended to use more realistic values when available.

1354

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.766: Link Adaptation in LTE The spectral efficiency is the number of useful data bits that can be transmitted using any modulation and coding scheme per Hz, the transition points between any two modulation and coding schemes give the default bearer selection thresholds in Atoll, and the normalised values from the slopes of the graphs, that represent the reduction in the spectral efficiency, give the block error rate. You can replace the bearer selection threshold values provided by default with other values, such as selection thresholds for 10 % BLER:

Bearer Selection Threshold

1 -6.8

2 -4.4

3 -4

4 -2

5 0

6 1.6

7 5.6

8 8

9 10.4

10 11

11 11.4

12 12

13 13.2

14 15.6

15 16.2

Calculating Bearer Selection Thresholds From Receiver Sensitivity Values

You can convert the receiver sensitivity values, that are listed in the specifications of your equipment, into bearer selection thresholds using the following conversion method: SF N Used CNR = RS + 114 NF 10 Log ----------------------------- N
Total

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.

Relation Between Bearer Efficiency And Spectral Efficiency

Spectral efficiency of a modulation and coding scheme is defined as the number of useful bits that can be transmitted each second over a channel of 1 Hz bandwidth. Spectral efficiency is hence given in terms of bps/Hz. In Atoll, the efficiency of bearers (modulation and coding schemes) are defined in the Bearers table. The bearer efficiency is given in terms of bits/symbol. Remember that in Atoll a symbol refers to one resource element, which is 1 symbol duration long and 1 subcarrier width wide, as shown in Figure 11.767.

Figure 11.767: Symbol The concept of bearer efficiency is similar to spectral efficiency. The only difference is in the units used to define the two entities. Here is a simple example that compares spectral efficiency and bearer efficiency, and shows that the two are the same. Spectral efficiency is given by: SE = ( 1 BLER ) r Log 2 ( M ) bps Hz

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1355

Atoll User Manual 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 LTE is 1 F = 15 kHz , from which we can calculate the useful symbol duration as well: T U = ------- = 66.67 sec . In one second, F there can be 1 sec 66.67 sec = 15000 symbol durations. If 15000 symbols are transmitted using QPSK1/2, this gives us a data rate of 15000 Symbols/sec 1 bits/Symbol = 15000 bps , which is the data rate achievable using one subcarrier of 15 kHz. We can find the spectral efficiency by normalizing the data rate 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.

Modelling VoIP Codecs

VoIP codecs are application-layer elements in the OSI system model. Atoll models application throughputs using a throughput offset and a scaling factor with respect to the RLC layer throughputs. You can model different VoIP codecs by creating a new service for each VoIP codec, and setting the target throughput to the Application Throughput for the scheduler used. Here are two examples of the most common VoIP codecs, and how they can be modelled in Atoll: G.711 VoIP Codec The actual voice data rate needed by the G.711 codec is 64 kbps, but with the lower layer headers and other added bits, the needed RLC data rate could be between 66.4 and 107.2 kbps. In this example, we show how to model the codec with header bits that lead to 85.6 kbps RLC data rate. a. Create a new service with the following parameters: Name: VoIP (G.711) Type: Voice Min Throughput Demand (DL) and Min Throughput Demand (UL): 64 kbps Max Throughput Demand (DL) and Max Throughput Demand (UL): 64 kbps Average Requested Throughput (DL) and Average Requested Throughput (UL): 64 kbps Scaling Factor: 74.77 % Offset: 0 kbps

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. G.729 VoIP Codec The actual voice data rate needed by the G.729 codec is 8 kbps, but with the lower layer headers and other added bits, the needed RLC data rate could be between 9.6 and 29.6 kbps. In this example, we show how to model the codec with header bits that lead to 29.6 kbps required data rate. a. Create a new service with the following parameters: Name: VoIP (G.729) Type: Voice Min Throughput Demand (DL) and Min Throughput Demand (UL): 8 kbps Max Throughput Demand (DL) and Max Throughput Demand (UL): 8 kbps Average Requested Throughput (DL) and Average Requested Throughput (UL): 8 kbps Scaling Factor: 27.03 % Offset: 0 kbps

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.

Working with EARFCNs instead of Channel Numbers

In Atoll, carriers are assigned channel numbers in the frequency bands table. These channel numbers do not necessarily have to be unique, i.e., a channel number can be reused in different bands. The 3GPP defines unique EARFCNs (Evolved Absolute Radio Frequency Channel Numbers) for all the frequency bands. Each EARFCN has a fixed width of 100 kHz, whereas channels (or carriers) in Atoll can have different widths. If you want to work with EARFCNs instead of channel numbers, you can set EARFCNs as channel numbers in the frequency bands table similar to as shown in the example below: Frequency Band: 2110 FDD - 5 MHz (E-UTRA Band 1) Downlink EARFCN Range: 0 - 599 Uplink EARFCN Range: 18000 - 18599 First Channel (EARFCN): 0 Last Channel (EARFCN): 550

1356

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks Excluded Channels (EARFCNs): 1-49, 51-99, 101-149, 151-199, 201-249, 251-299, 301-349,351-399,401-449, 451-499, 501-549, 551-599

For FDD frequency bands, the downlink and uplink EARFCNs are always offset by 18000, so you can use either the downlink or the uplink EARFCNs as channel numbers in Atoll.

Modelling the Co-existence of Networks

In Atoll, you can study the effect of interference received by your network from other LTE networks. The interfering LTE network can be a different part of your own network, or a network belonging to another operator. To study interference from co-existing networks: 1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a Group of Base Stations" on page 1185. 2. For the interfering networks transmitters, set the Transmitter Type to Extra-Network (Interferer Only) as explained in "Transmitter Description" on page 1174. During calculations, Atoll will consider the transmitters of type Extra-Network (Interferer Only) when calculating interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interference. Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network. If the interfering network is a part of your own network, this information would be readily available. However, if the interfering network belongs to another operator, the information available might not be accurate. Moreover, for other operators networks, and if the interfering networks use OFDM but are not LTE networks, their modelling will not be accurate using LTE transmitters and cells. The number of subcarriers used in the interfering networks might be very different.

11.9

Glossary of LTE Terms

Understanding the following terms and there use in Atoll is very helpful in understanding the LTE module: User: A general term that can also designate a subscriber, mobile, and receiver. Subscriber: Users with fixed geographical coordinates. 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. 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 data rate 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). 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. 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 UL instead of the uplink noise rise is the uplink load factor: L UL = ------------------------ . Usually, the uplink load factor is kept I UL + N UL as a linear value (in %) 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 I+N 1 N I ----------- = --------------------- => ----------- = ----------- ----------- => ----------- = 1 ----------- => ----------- = 1 ----------- => ----------- = --------------------I+N I+N I+N I+N I+N I+N I+N N I I+N I+N 1 ----------I+N 1 => NR = ----------1L

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1357

Atoll User Manual The following table shows the relation between interference, load factor, and noise rise.

Interference (I)
0 =N =9xN = 99 x N

Load Factor (%)

0 50 90 99

Noise Rise
1 2 10 100

Noise Rise (dB)

0 3.01 10 20

The reason why uplink interference is expressed in terms of noise rise (in dB) in Atoll instead of load factor (in %) is that the load factor varies somewhat exponentially with the increase in interference. Resources: In Atoll, the term "resource" is used to refer to the average number of resource units, expressed in % (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. Frame: An LTE frame is 10 ms long. The duration of a frame is a system-level constant. Each frame comprises 10 1 ms-long 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 systems as shown in Figure 11.768. 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.768: 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.767. 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.769). 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.769) 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.769). 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.

1358

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Chapter 11: LTE Networks

Figure 11.769: LTE resource blocks LTE Logical Channels: LTE logical channels include (see Figure 11.770): - Broadcast Control Channel (BCCH) (DL): Carries broadcast control information. - Paging Contol 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.770): - Broadcast Channel (BCH) (DL): Carries broadcast information. - Paging Channel (PCH) (DL): Carries paging information. - 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.770): - 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.770: LTE logical, transport, and physical layer channels (DL: blue, UL: orange, DL or UL: green) Inter-Cell Interference Coordination: It is a means to improve the signal quality at cell edges by using different frequencies or resource blocks for resource allocation in potentially mutually interfering cells. There are two categories of interference coordination techniques used in OFDMA systems: - Static ICIC using Fractional Frequency Reuse (FFR): Static interference coordination is a fractional frequency allocation problem. Fractions of a channel bandwidth are allocated to different sectors to be used at cell edges. The allocation does not change over time and the same fractions of the channel bandwidth are used by the sectors. - Dynamic ICIC using Interference-aware scheduling: Dynamic interference coordination is a scheduler problem. There is no fixed fractional frequency allocation per sector. The resource blocks allocated to users located at cell edges are determined by the schedulers of each eNode-B dynamically for each subframe. The aim is to not use the same resource blocks at cell edges of potentially mutually interfering cells (i.e., coordinate the allocation of resources) thus avoiding interference.

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1359

Atoll User Manual

1360

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Index

Index

Symbols
+MRC in Softer/Soft (CDMA) 799 +MRC in Softer/Soft (UMTS) 653

definition 346, 579, 1068, 1270 electrical tilt, reconfiguration 347, 362, 579, 596, 1068, 1085,
1270, 1286

Numerics
2G network traffic, converting (CDMA) 755 2G network traffic, converting (GSM) 261 2G network traffic, converting (LTE) 1252 2G network traffic, converting (TD-SCDMA) 913 2G network traffic, converting (UMTS) 558 2G network traffic, converting (WiMAX) 1050 3-D antenna pattern defining attenuation 145 defining azimuth 145 defining tilt angle 145 importing 145

filtering zone, using 347, 580, 1069, 1271 global configuration 352, 585, 1074, 1276 hot spot zones, using 347, 580, 1069, 1270 HotSpots, importing 356, 589, 1078, 1279 indoor coverage 348, 581, 1070, 1271 iterations, defining number of 355, 588, 1077, 1278 iterations, defining resolution 355, 588, 1077, 1278 maps, comparing 386, 622, 1111, 1312 maps, display properties 387, 623, 1112, 1313 mechanical tilt, reconfiguration 347, 362, 580, 596, 1069,
1085, 1270, 1286

multi-band antennas, defining 370, 606, 1095, 1296 multi-layer networks, linking transmitters 363, 597, 1086,
1287

A
acceptable noise rise margin, defining for EV-DO cells (CDMA)
673

optimisation process, creating 353, 586, 1075, 1276, 1277 optimisation process, creating in co-planning 650, 1137,
1339

ACP advanced optimisation parameters, setting 372, 608, 1097,

1298

antenna azimuth, reconfiguration 347, 362, 580, 596, 1069,

1085, 1270, 1286

antenna height, reconfiguration 347, 362, 580, 596, 1069,

1085, 1270, 1286

antenna masking 348, 581, 1070, 1271 antenna type, reconfiguration 347, 362, 580, 596, 1069, 1085,
1270, 1286

antennas, AEDT 369, 605, 1094, 1295 antennas, creating by pattern 369, 605, 1094, 1295 antennas, grouping automatically 370, 371, 606, 607, 1095,
1096, 1296, 1297

optimisation process, running 354, 587, 1076, 1277 optimisation properties, changing 375, 611, 1100, 1301 optimisation, deleting 375, 611, 1100, 1301 optimisation, running 375, 611, 1100, 1301 optimisation, running saved 373, 609, 1098, 1299 pilot power, reconfiguration 361, 579, 594, 1084, 1285 preamble power, reconfiguration 1068 propagation model, default 349, 582, 1071, 1272 propagation models 348, 581, 1070, 1271 propagation models, defining 351, 584, 598, 1073, 1087,
1275, 1288

propagation models, natively supported 348, 581, 1070,

1272

best server analysis maps 386, 622, 1111, 1312 candidates, creating 366, 602, 1091, 1292 change analysis maps 385, 621, 1110, 1311 comments, adding to optimisation 372, 608, 1097, 1298 computation zone, using 347, 580, 1069, 1270 configuration, loading 375, 611, 1100, 1301 configuration, saving 375, 611, 1100, 1301 configuring 350, 583, 1072, 1273 configuring default settings 350, 583, 1072, 1273 co-planning optimisation process, creating 651, 1138, 1340 co-planning optimisation process, importing second technology 651, 1138, 1340 coverage analysis maps 384, 620, 1109, 1310 coverage, defining for Ec/Io 358 defining optimisation (GSM) 354 defining optimisation (LTE) 1277 defining optimisation (UMTS) 587 defining optimisation (WiMAX) 1076

propagation models, precalculated path loss matrices 351,

584, 598, 1073, 1087, 1275, 1288

propagation models, precalculated pathlooss matrices 349,

582, 1071, 1272

quality analysis maps 383, 619, 1108, 1309 reconfiguration options 347, 579, 1068, 1270 reconfiguration options (GSM) 360 reconfiguration options (LTE) 1284 reconfiguration options (UMTS) 594 reconfiguration options (WiMAX) 1083 reconfiguration, importing parameters 361, 364, 595, 599,
1088, 1289

results, viewing in histogram 388, 624, 1113, 1314 results, viewing in map window 382, 618, 1107, 1308 results, viewing in Properties dialogue 376, 612, 1101, 1302 shadowing margin 348, 581, 1070, 1271 site selection 347, 580, 1069, 1270 site selection, defining 365, 600, 1089, 1290 total power, reconfiguration 1270

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1361

Atoll User Manual

traffic maps, using (GSM) 348 traffic maps, using (LTE) 1271 traffic maps, using (UMTS) 580 traffic maps, using (WiMAX) 1069 traffic, defining for optimisation 359, 593, 1082, 1283 transmission power (BCCH), reconfiguration 347 user configuration file 352, 585, 1074, 1275 weighting (LTE) 1282 weighting, GSM 358 weighting, UMTS 592 weighting, WiMAX 1081 zones, using 347, 580, 1069, 1270 ACP coverage maps exporting (GSM) 388 exporting (LTE) 1314 exporting (UMTS) 624 exporting (WiMAX) 1113 active set conditions for entering (CDMA) 803 conditions for entering (UMTS) 661 defining size in terminals (CDMA) 715 defining size in terminals (UMTS) 514 displaying per simulation user (CDMA) 762 displaying per simulation user (UMTS) 566 size, used in predictions (CDMA) 714 size, used in predictions (UMTS) 513 threshold, defining in cells (UMTS) 471 active set analysis (CDMA) 725 active set analysis (UMTS) 523 activity status displaying traffic distribution by (LTE) 1260 displaying traffic distribution by (WiMAX) 1058 adaptive beam smart antenna modelling (TD-SCDMA) 958 adaptive modulation and coding, see "fast link adaptation" adjacent channels definition (GSM) 271 antenna azimuth, reconfiguring with ACP 347, 362, 580, 596, 1069,
1085, 1270, 1286

antenna patterns printing 68, 147 archiving all modifications to the database 102 only site data to the database 102 attenuation 3-D antenna pattern 145 audit of frequency allocation (TD-SCDMA) 881 audit of inter-technology neighbour plan (CDMA) 796 audit of inter-technology neighbour plan (LTE) 1338 audit of inter-technology neighbour plan (TD-SCDMA) 951 audit of inter-technology neighbour plan (UMTS) 649 audit of inter-technology neighbour plan (WiMAX) 1136 audit of neighbour allocation plan (CDMA) 738 audit of neighbour allocation plan (GSM) 251 audit of neighbour allocation plan (LTE) 1234 audit of neighbour allocation plan (TD-SCDMA) 891 audit of neighbour allocation plan (UMTS) 540 audit of neighbour allocation plan (WiMAX) 1032 audit of physical cell ID plan (LTE) 1241 audit of PN offset plan (CDMA) 742 audit of preamble index plan (WiMAX) 1039 audit of scrambling code plan (TD-SCDMA) 897 audit of scrambling code plan (UMTS) 545 automatic backup 105 configuring 105 recovering a backup 106 Automatic Cell Planning, see "ACP" azimuth 3-D antenna pattern 145 antenna, changing on the map 31

B
backup 105 configuring 105 recovering a backup 106 base station assigning equipment (CDMA) 670 assigning equipment (GSM) 195 assigning equipment (TD-SCDMA) 814 assigning equipment (UMTS) 469 components of subsystem 147 copying into document (CDMA) 680 copying into document (GSM) 208 copying into document (LTE) 1185 copying into document (TD-SCDMA) 827 copying into document (UMTS) 481 copying into document (WiMAX) 982 creating (LTE) 1173 creating (WiMAX) 969 creating with template (CDMA) 674 creating with template (GSM) 203 creating with template (LTE) 1180 creating with template (TD-SCDMA) 820 creating with template (UMTS) 475 creating with template (WiMAX) 976 definition (CDMA) 667, 668 definition (GSM) 192, 193
Forsk 2010

beamwidth, defining 144 changing azimuth on the map 31 changing relative position on the map 32 creating 143 electrical tilt, reconfiguring with ACP 347, 362, 579, 596,
1068, 1085, 1270, 1286

gain 143 height, reconfiguring with ACP 347, 362, 580, 596, 1069,
1085, 1270, 1286

importing 3-D patterns 145 importing Planet-format 144 mechanical tilt, reconfiguring with ACP 347, 362, 580, 596,
1069, 1085, 1270, 1286

model, reconfiguring with ACP 347, 362, 580, 596, 1069,

1085, 1270, 1286

pasting antenna pattern 143 pattern electrical tilt 143 smart, creating (WiMAX) 1152 smoothing vertical pattern 146

1362

Unauthorized reproduction or distribution of this document is prohibited

Index

definition (LTE) 1173 definition (TD-SCDMA) 812, 813 definition (UMTS) 466, 467 definition (WiMAX) 969 displaying information (CDMA) 681 displaying information (GSM) 209 displaying information (LTE) 1186 displaying information (TD-SCDMA) 828 displaying information (UMTS) 482 displaying information (WiMAX) 983 duplicating (GSM) 207 duplicating (LTE) 1184 duplicating (TD-SCDMA) 826 duplicating (UMTS) 481 duplicating (WiMAX) 981 equipment, assigning (LTE) 1175 equipment, assigning (WiMAX) 971 importing (CDMA) 680 importing (GSM) 208 importing (LTE) 1185 importing (TD-SCDMA) 827 importing (UMTS) 481 importing (WiMAX) 982 base station ID, see "BSID" baton handover coverage prediction (TD-SCDMA) 876 BCCH displaying on transmitter (GSM) 342 BCMCS (CDMA) 673 BCMCS throughput (CDMA) 673 beamwidth defining antenna 144 bearer selection, HSDPA, explanation 560, 916 bearer, 1xEV-DO, see "1xEV-DO Rev. A radio bearer" bearer, downgrading (UMTS) 563 bearer, HSDPA, see "HSDPA radio bearer" bearer, R99, see "R99 radio bearer" BER coverage prediction (CDMA) 721 BER coverage prediction (UMTS) 519 best bearer coverage prediction (LTE) 1216 best bearer coverage prediction (WiMAX) 1014 BLER coverage prediction (GSM) 333 BLER coverage prediction (UMTS) 519 BLER_DCH coverage prediction (CDMA) 721 Broadcast/Multicast Services, see "BCMS" BSIC displaying on transmitter (GSM) 342 domains, defining (GSM) 273 format, defining (GSM) 272 groups, defining (GSM) 273 BSID (WiMAX) 973 BTS defining 148 noise figure 149 noise figure, updating 148 Rho factor 148 BTS equipment assigning (CDMA) 670 assigning (GSM) 195
Forsk 2010

assigning (TD-SCDMA) 814 assigning (UMTS) 469 BTS noise figure (TD-SCDMA) 815 BTS noise figure (UMTS) 470 BTS, assigning (LTE) 1175 BTS, assigning (WiMAX) 971 BWA, definition (WiMAX) 967

C
C/(I+N) level coverage prediction (LTE) 1214 C/(I+N) level coverage prediction (WiMAX) 1012 C/I levels coverage prediction (GSM) 320 calculation process, explanation (CDMA) 695 calculation process, explanation (GSM) 223 calculation process, explanation (LTE) 1195 calculation process, explanation (TD-SCDMA) 842 calculation process, explanation (UMTS) 496 calculation process, explanation (WiMAX) 992 calculations 153 subscriber list (LTE) 1256 subscriber list (WiMAX) 1054 carrier types (TD-SCDMA) allocating per cell 881 audit of allocation 881 displaying coverage 881 displaying master carrier on the map 881 master carrier 879 slave carrier 879 standalone carrier 879 CDMA2000 1xRTT 1xEV-DO template 94 cell creating (LTE) 1179 creating (TD-SCDMA) 820 creating (UMTS) 474 creating (WiMAX) 976 creating 1xEV-DO (CDMA) 674 creating 1xRTT (CDMA) 674 definition (LTE) 1176 definition (WiMAX) 972 EV-DO parameters (CDMA) 671 modifying (LTE) 1179 modifying (TD-SCDMA) 820 modifying (UMTS) 474 modifying (WiMAX) 976 modifying 1xEV-DO (CDMA) 674 modifying 1xRTT (CDMA) 674 parameters (TD-SCDMA) 816 parameters (UMTS) 470 RTT parameters (CDMA) 671 setting as active (CDMA) 696 setting as active (TD-SCDMA) 842 setting as active (UMTS) 497 updating load values with simulation (LTE) 1268 updating load values with simulation (WiMAX) 1067 updating values with simulation (CDMA) 768 updating values with simulation (TD-SCDMA) 926 updating values with simulation (UMTS) 575

Unauthorized reproduction or distribution of this document is prohibited

1363

Atoll User Manual

cell to cell interference coverage prediction (TD-SCDMA) 873 cell type applying new (GSM) 202 cell types creating (GSM) 404 examples (GSM) 406 cell types (GSM) 404 channel element calculation of consumption (UMTS) 560 defining consumption per site equipment-HSUPA radio bearer (UMTS) 657 defining consumption per site equipment-R99 radio bearer (UMTS) 657 defining consumption per site equipment-terminal (CDMA)
802

defining on downlink (UMTS) 468 defining on forward link (CDMA) 669 defining on reverse link (CDMA) 669 defining on uplink (UMTS) 468 simulations (CDMA) 759 simulations (UMTS) 564 uplink and downlink consumption (CDMA) 802 uplink and downlink consumption (UMTS) 656 channels Search Tool, using with (GSM) 341 codec equipment codec mode adaptation thresholds, setting (GSM) 409 codec mode quality thresholds, setting (GSM) 410 creating (GSM) 409 modifying (GSM) 409 terminals, assigning to (GSM) 411 transmitters, assigning to (GSM) 410 codec equipment (GSM) 408 codec mode table, opening (GSM) 408 coding scheme table, opening 411 coding scheme throughput graphs displaying (GSM) 413 column headers formatting 57 columns changing width 57 displaying 58 freezing 58 hiding 58 moving 58 unfreezing 58 compressed mode (UMTS) 513, 514, 568, 653 computation zone ACP 347, 580, 1069, 1270 drawing 42 drawing (CDMA) 696 drawing (GSM) 223 drawing (LTE) 1195 drawing (TD-SCDMA) 842 drawing (UMTS) 496 drawing (WiMAX) 992

editing 46 explanation (CDMA) 691 explanation (GSM) 218 explanation (LTE) 1190 explanation (TD-SCDMA) 837 explanation (UMTS) 492 explanation (WiMAX) 987 Fit to Map Window 42 Fit to Map Window (CDMA) 696 Fit to Map Window (GSM) 224 Fit to Map Window (LTE) 1195 Fit to Map Window (TD-SCDMA) 842 Fit to Map Window (UMTS) 497 Fit to Map Window (WiMAX) 992 importing 42 importing (CDMA) 696 importing (GSM) 224 importing (LTE) 1195 importing (TD-SCDMA) 842 importing (UMTS) 497 importing (WiMAX) 992 polygon, creating from 42 polygon, creating from (CDMA) 696 polygon, creating from (GSM) 224 polygon, creating from (LTE) 1195 polygon, creating from (TD-SCDMA) 842 polygon, creating from (UMTS) 497 polygon, creating from (WiMAX) 992 configuration loading ACP 375, 611, 1100, 1301 saving ACP 375, 611, 1100, 1301 Connection Properties 100 connection status displaying traffic distribution by (CDMA) 761 displaying traffic distribution by (LTE) 1260 displaying traffic distribution by (TD-SCDMA) 919 displaying traffic distribution by (UMTS) 565 displaying traffic distribution by (WiMAX) 1058 constraint costs, defining PN offsets (CDMA) 740 constraint costs, defining scrambling code (TD-SCDMA) 894 constraint costs, defining scrambling code (UMTS) 543 context menu 29 renaming objects 29 conventional beamformer modelling (TD-SCDMA) 957 conventional beamformer modelling (WiMAX) 1151 coordinate system 96 setting 96 coordinates, searching by 86 co-planning CDMA 782 co-planning mode, ending (CDMA) 797 co-planning mode, ending (LTE) 1341 co-planning mode, ending (TD-SCDMA) 952 co-planning mode, ending (UMTS) 652 co-planning mode, ending (WiMAX) 1139 co-planning mode, switching to (CDMA) 782 co-planning mode, switching to (LTE) 1324 co-planning mode, switching to (TD-SCDMA) 937
Forsk 2010

1364

Unauthorized reproduction or distribution of this document is prohibited

Index

co-planning mode, switching to (UMTS) 635 co-planning mode, switching to (WiMAX) 1123 inter-technology exceptional pairs, displaying (CDMA) 788 inter-technology exceptional pairs, displaying (LTE) 1329 inter-technology exceptional pairs, displaying (TD-SCDMA) 943 inter-technology exceptional pairs, displaying (UMTS) 640 inter-technology exceptional pairs, displaying (WiMAX)
1128

inter-technology neighbours, displaying (TD-SCDMA) 946 inter-technology neighbours, displaying (UMTS) 644 inter-technology neighbours, displaying (WiMAX) 1131 inter-technology neighbours, setting on the map (CDMA)
794

inter-technology neighbours, setting on the map (LTE)

1335

inter-technology exceptional pairs, setting (CDMA) 787 inter-technology exceptional pairs, setting (LTE) 1328 inter-technology exceptional pairs, setting (TD-SCDMA)
942

inter-technology neighbours, setting on the map (TD-SCDMA) 949 inter-technology neighbours, setting on the map (UMTS)
647

inter-technology neighbours, setting on the map (WiMAX)

1134

inter-technology exceptional pairs, setting (UMTS) 640 inter-technology exceptional pairs, setting (WiMAX) 1128 inter-technology exceptional pairs, setting on the map (CDMA) 788 inter-technology exceptional pairs, setting on the map (LTE) 1329 inter-technology exceptional pairs, setting on the map (TD-SCDMA) 943 inter-technology exceptional pairs, setting on the map (UMTS) 641 inter-technology exceptional pairs, setting on the map (WiMAX) 1129 inter-technology neighbour allocation (CDMA) 787 inter-technology neighbour allocation (LTE) 1328 inter-technology neighbour allocation (TD-SCDMA) 942 inter-technology neighbour allocation (UMTS) 640 inter-technology neighbour allocation (WiMAX) 1128 inter-technology neighbours, allocating automatically (CDMA) 789 inter-technology neighbours, allocating automatically (LTE) 1330 inter-technology neighbours, allocating automatically (TD-SCDMA) 944 inter-technology neighbours, allocating automatically (UMTS) 642 inter-technology neighbours, allocating automatically (WiMAX) 1130 inter-technology neighbours, allocating per cell (CDMA)
792

legend window, displaying (CDMA) 785 legend window, displaying (LTE) 1327 legend window, displaying (TD-SCDMA) 941 legend window, displaying (UMTS) 638 legend window, displaying (WiMAX) 1126 LTE 1323 neighbours, configuring importance of (CDMA) 789 neighbours, configuring importance of (LTE) 1330 neighbours, configuring importance of (TD-SCDMA) 944 neighbours, configuring importance of (UMTS) 642 neighbours, configuring importance of (WiMAX) 1130 networks, coverage areas, comparing (CDMA) 786 networks, coverage areas, comparing (LTE) 1327 networks, coverage areas, comparing (TD-SCDMA) 941 networks, coverage areas, comparing (UMTS) 638 networks, coverage areas, comparing (WiMAX) 1127 networks, coverage areas, studying differences (CDMA)
786

networks, coverage areas, studying differences (LTE) 1328 networks, coverage areas, studying differences (TD-SCDMA) 942 networks, coverage areas, studying differences (UMTS)
639

networks, coverage areas, studying differences (WiMAX)

1127

networks, coverage predictions, analysing (CDMA) 785 networks, coverage predictions, analysing (LTE) 1326 networks, coverage predictions, analysing (TD-SCDMA)
940

inter-technology neighbours, allocating per cell (LTE) 1333 inter-technology neighbours, allocating per cell (TD-SCDMA) 947 inter-technology neighbours, allocating per cell (UMTS)
645

inter-technology neighbours, allocating per cell (WiMAX)

1132

networks, coverage predictions, analysing (UMTS) 637 networks, coverage predictions, analysing (WiMAX) 1125 networks, coverage predictions, updating (CDMA) 784 networks, coverage predictions, updating (LTE) 1325 networks, coverage predictions, updating (TD-SCDMA)
939

inter-technology neighbours, allocating using Neighbours table (CDMA) 793 inter-technology neighbours, allocating using Neighbours table (LTE) 1334 inter-technology neighbours, allocating using Neighbours table (TD-SCDMA) 948 inter-technology neighbours, allocating using Neighbours table (UMTS) 646 inter-technology neighbours, allocating using Neighbours table (WiMAX) 1133 inter-technology neighbours, displaying (CDMA) 791 inter-technology neighbours, displaying (LTE) 1333
Forsk 2010

networks, coverage predictions, updating (UMTS) 636 networks, coverage predictions, updating (WiMAX) 1125 networks, displaying both in same document (CDMA) 783 networks, displaying both in same document (LTE) 1324 networks, displaying both in same document (TD-SCDMA)
938

networks, displaying both in same document (UMTS) 635 networks, displaying both in same document (WiMAX)
1124

TD-SCDMA 937 UMTS 634 unlinking documents (CDMA) 797

Unauthorized reproduction or distribution of this document is prohibited

1365

Atoll User Manual

unlinking documents (LTE) 1341 unlinking documents (TD-SCDMA) 952 unlinking documents (UMTS) 652 unlinking documents (WiMAX) 1139 WiMAX 1123 Cost-Hata propagation model 161 creating environment formula 162 defining default environment formula 162 modifying environment formula 162 taking diffraction into account 161 coverage by C/I based on test mobile data path (GSM) 394 coverage by signal level based on test mobile data path (GSM)
394

coverage of master carriers, displaying (TD-SCDMA) 881 coverage of neighbours, displaying (CDMA) 733 coverage of neighbours, displaying (GSM) 247 coverage of neighbours, displaying (LTE) 1230 coverage of neighbours, displaying (TD-SCDMA) 887 coverage of neighbours, displaying (UMTS) 535 coverage of neighbours, displaying (WiMAX) 1028 coverage prediction adding values to legend (CDMA) 701 adding values to legend (GSM) 233 adding values to legend (TD-SCDMA) 851 adding values to legend (UMTS) 502 analysing results (CDMA) 701 analysing results (LTE) 1200 analysing results (TD-SCDMA) 851 analysing results (UMTS) 501 analysing results (WiMAX) 997 assigning a default propagation model 170, 695 based on test mobile data path (LTE) 1320 based on test mobile data path (UMTS) 630, 777 based on test mobile data path (WiMAX) 1119 baton handover (TD-SCDMA) 876 best bearer (LTE) 1216 best bearer (WiMAX) 1014 BLER (GSM) 333 by packet throughput per timeslot (GSM) 331 by transmitter (CDMA) 699 by transmitter (GSM) 227, 228, 229, 230, 231 by transmitter (LTE) 1198 by transmitter (TD-SCDMA) 845 by transmitter (UMTS) 499 by transmitter (WiMAX) 995 C/(I+N) level (LTE) 1214 C/(I+N) level (WiMAX) 1012 C/I levels (GSM) 320 calculating 184, 185 calculating several 185 cell to cell interference (TD-SCDMA) 873 cloning 183 comparing (CDMA) 706 comparing (GSM) 237 comparing (LTE) 1205 comparing (TD-SCDMA) 855 comparing (UMTS) 506 comparing (WiMAX) 1002

coverage by C/I based on test mobile data path (GSM) 394 coverage by signal level based on test mobile data path (GSM) 394 creating 183 creating from existing 183 default propagation model, assigning (GSM) 223 displaying results with tooltips (CDMA) 702 displaying results with tooltips (LTE) 1201 displaying results with tooltips (TD-SCDMA) 851 displaying results with tooltips (UMTS) 502 displaying results with tooltips (WiMAX) 998 downlink and uplink traffic channel (TD-SCDMA) 865 downlink total noise (CDMA) 722 downlink total noise (TD-SCDMA) 872 downlink total noise (UMTS) 520 duplicating 183 DwPTS signal quality (TD-SCDMA) 864 effective service area (CDMA) 720 effective service area (TD-SCDMA) 869 effective service area (UMTS) 517 effective signal (LTE) 1212 effective signal (WiMAX) 1009 exporting in user configuration 187 exporting results 49 forcing calculation 185 forward link EV-DO throughput (CDMA) 718 geographic export zone, defining (CDMA) 727 geographic export zone, defining (GSM) 241 geographic export zone, defining (LTE) 1225 geographic export zone, defining (WiMAX) 1022 geographic exportt zone, defining (TD-SCDMA) 879 geographic exportt zone, defining (UMTS) 528 geogrphic export zone, defining 46 GPRS/EGPRS coding schemes (GSM) 328 handoff status (CDMA) 724 handover status (UMTS) 522 histogram, viewing (CDMA) 705 histogram, viewing (GSM) 236 histogram, viewing (LTE) 1204 histogram, viewing (TD-SCDMA) 854 histogram, viewing (UMTS) 505 histogram, viewing (WiMAX) 1001 HSDPA 525, 877 HSUPA 527 legend, adding values to (LTE) 1201 legend, adding values to (WiMAX) 998 locking coverage predictions 185, 186 network capacity (TD-SCDMA) 901, 903 network load (TD-SCDMA) 904 new 183 on interfered zones (GSM) 323 on overlapping zones (CDMA) 700 on overlapping zones (GSM) 232 on overlapping zones (LTE) 1199 on overlapping zones (UMTS) 500 on overlapping zones (WiMAX) 996 on P-CCPCH pollution (TD-SCDMA) 846 pilot pollution (CDMA) 723
Forsk 2010

1366

Unauthorized reproduction or distribution of this document is prohibited

Index

pilot pollution (UMTS) 521 pilot reception analysis (Ec/I0) based on test mobile data path (UMTS) 630, 778 pilot signal quality (CDMA) 716 pilot signal quality (TD-SCDMA) 863 pilot signal quality (UMTS) 515 PN offset interference zone (CDMA) 745 preamble analysis based on test mobile data path (WiMAX) 1119 printing results (CDMA) 727 printing results (GSM) 241 printing results (LTE) 1225 printing results (TD-SCDMA) 879 printing results (UMTS) 528 printing results (WiMAX) 1022 quality indicator (CDMA) 721 quality indicator (LTE) 1221 quality indicator (UMTS) 519 quality indicator (WiMAX) 1019 report, displaying (CDMA) 703 report, displaying (GSM) 235 report, displaying (LTE) 1203 report, displaying (TD-SCDMA) 853 report, displaying (UMTS) 504 report, displaying (WiMAX) 1000 report, displaying using focus zone 43 report, displaying using focus zone (CDMA) 703 report, displaying using focus zone (GSM) 234 report, displaying using focus zone (LTE) 1202 report, displaying using focus zone (TD-SCDMA) 852 report, displaying using focus zone (UMTS) 503 report, displaying using focus zone (WiMAX) 999 report, displaying using hot spot zone 43 report, displaying using hot spot zone (CDMA) 703 report, displaying using hot spot zone (GSM) 234 report, displaying using hot spot zone (LTE) 1202 report, displaying using hot spot zone (TD-SCDMA) 852 report, displaying using hot spot zone (UMTS) 503 report, displaying using hot spot zone (WiMAX) 999 restricting base stations studied by computation zone (CDMA) 687 restricting base stations studied by computation zone (GSM) 214 restricting base stations studied by computation zone (LTE) 1187 restricting base stations studied by computation zone (TD-SCDMA) 834 restricting base stations studied by computation zone (UMTS) 488 restricting base stations studied by computation zone (WiMAX) 984 restricting base stations studied by filter (CDMA) 687 restricting base stations studied by filter (GSM) 214 restricting base stations studied by filter (LTE) 1187 restricting base stations studied by filter (TD-SCDMA) 833 restricting base stations studied by filter (UMTS) 488 restricting base stations studied by filter (WiMAX) 983 restricting base stations studied by filtering (TD-SCDMA)
833

results, analysing (GSM) 233 results, displaying with tooltips (GSM) 233 results, exporting (CDMA) 727 results, exporting (GSM) 241 results, exporting (LTE) 1225 results, exporting (TD-SCDMA) 879 results, exporting (UMTS) 528 results, exporting (WiMAX) 1022 RSCP UpPCH (TD-SCDMA) 849 scrambling code interference zone (TD-SCDMA) 899 scrambling code interference zone (UMTS) 548 service area (C/I) (TD-SCDMA) 867 service area (Eb/Nt) (TD-SCDMA) 867 service area (Eb/Nt) downlink based on test mobile data path (UMTS) 630, 778 service area (Eb/Nt) downlink or uplink (CDMA) 717 service area (Eb/Nt) downlink or uplink (UMTS) 516 service area (Eb/Nt) MBMS (TD-SCDMA) 871 service area (Eb/Nt) MBMS (UMTS) 518 service area (Eb/Nt) reverse link for EV-DO (CDMA) 719 service area (Eb/Nt) uplink based on test mobile data path (UMTS) 630, 778 signal level - single station (CDMA) 689 signal level - single station (GSM) 216 signal level - single station (LTE) 1189 signal level - single station (TD-SCDMA) 835 signal level - single station (UMTS) 490 signal level - single station (WiMAX) 986 signal level (CDMA) 697 signal level (GSM) 225 signal level (LTE) 1197 signal level (TD-SCDMA) 844, 848 signal level (UMTS) 498 signal level (WiMAX) 994 simulation results, using (CDMA) 772 statistics, viewing (CDMA) 705 statistics, viewing (GSM) 236 statistics, viewing (LTE) 1204 statistics, viewing (TD-SCDMA) 854 statistics, viewing (UMTS) 505 statistics, viewing (WiMAX) 1001 stopping calculation 185 template, saving as 186 test mobile data path, based on (GSM) 394 throughput (LTE) 1218 throughput (WiMAX) 1016 tooltips, comparing coverage predictions with (CDMA) 786 tooltips, comparing coverage predictions with (LTE) 1327 tooltips, comparing coverage predictions with (TD-SCDMA) 941 tooltips, comparing coverage predictions with (UMTS) 638 tooltips, comparing coverage predictions with (WiMAX)
1126

UpPCH interference (TD-SCDMA) 874 using simulation results (LTE) 1269 using simulation results (TD-SCDMA) 928 using simulation results (UMTS) 578 using simulation results (WiMAX) 1068

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1367

Atoll User Manual

coverage predictions 182 cursors 52 CW Measurement Analysis Tool printing data 68 CW measurements test mobile data path, generating from (CDMA) 781 test mobile data path, generating from (GSM) 398, 399 test mobile data path, generating from (LTE) 1322 test mobile data path, generating from (TD-SCDMA) 936 test mobile data path, generating from (UMTS) 633 test mobile data path, generating from (WiMAX) 1122 cyclic prefix ratio (LTE) 1342 cyclic prefix ratio (WiMAX) 1140

D
Data Rate Control, see "DRC" Data tab 27 data tables adding a field 54 changing column width 57 changing row height 57 copying data 59 deleting a field 55 displaying columns 58 editing 55 exporting data 61 filtering 73 filtering by selection 74 filtering by several criteria 75 filtering, examples 76 formatting column headers 57 formatting table columns 57 freezing columns 58 hiding columns 58 importing data 63 moving columns 58 opening 54 opening record properties from table 56 pasting data 59 printing 64 restoring after filtering 76 sorting 73 sorting by one column 73 sorting by several columns 73 unfreezing columns 58 viewing properties 54 XML files, exporting to 64 XML files, importing from 64 database archiving all modifications 102 archiving only site data 102 connecting to MS Access 99 connecting to Oracle 99 Connection Properties 100 creating a document from 99 refreshing document 101 resolving data conflicts 103 working with 97

defining 181, 187 defraction smoothing vertical antenna pattern 146 display changing properties 32 defining display type 33 display type, automatic 34 display type, discrete values 34 display type, unique 34 display type, value intervals 34 display coordinate system 96 display resolution (CDMA) 690 display resolution (GSM) 217 display resolution (TD-SCDMA) 836 display resolution (UMTS) 491 Distance Measurement tool 40 diversity reception (TD-SCDMA) 961 reception (UMTS) 477, 658 transmission (TD-SCDMA) 961 transmission (UMTS) 477, 658 document creating from database 93, 99 creating from template 93, 94 geographic data 93 information needed to create 93 radio data 93 radio equipment 93 refreshing from the database 101 setting basic parameters 95 document templates, see "templates" domains, creating scrambling code (TD-SCDMA) 893 domains, creating scrambling code (UMTS) 542 downgrading bearer (UMTS) 563 downlink total noise coverage prediction (CDMA) 722 downlink total noise coverage prediction (TD-SCDMA) 872 downlink total noise coverage prediction (UMTS) 520 downlink total power, setting (UMTS) 510 downlink traffic channel coverage prediction (TD-SCDMA) 865 downlink traffic power, setting (TD-SCDMA) 859 DRC error rate (CDMA) 673 DTM maps representing different areas 131 dual-band network, creating (CDMA) 682 dual-band network, creating (TD-SCDMA) 828 dual-band network, creating (UMTS) 483 DwPTS signal quality coverage prediction (TD-SCDMA) 864

E
Ec/I0 threshold (UMTS) 513 effective service area coverage prediction (CDMA) 720 effective service area coverage prediction (TD-SCDMA) 869 effective service area coverage prediction (UMTS) 517 effective signal coverage prediction (LTE) 1212 effective signal coverage prediction (WiMAX) 1009 environment creating (CDMA) 749 creating (GSM) 256 creating (LTE) 1246
Forsk 2010

1368

Unauthorized reproduction or distribution of this document is prohibited

Index

creating (TD-SCDMA) 908 creating (UMTS) 552 creating (WiMAX) 1044 modifying (CDMA) 749 modifying (GSM) 256 modifying (LTE) 1246 modifying (TD-SCDMA) 908 modifying (UMTS) 552 modifying (WiMAX) 1044 equipment creating (LTE) 1345 creating (WiMAX) 1146 modifying (LTE) 1345 modifying (WiMAX) 1146 Equipment Specifications dialogue (CDMA) 670 Equipment Specifications dialogue (GSM) 195 Equipment Specifications dialogue (LTE) 1175 Equipment Specifications dialogue (TD-SCDMA) 814 Equipment Specifications dialogue (UMTS) 469 Equipment Specifications dialogue (WiMAX) 971 equipment, repeater, see "repeater equipment" Erceg-Greenstein (SUI) propagation model 164 assigning environment formulas 165 creating environment formula 165 defining default environment formula 165 modifying environment formula 165 taking diffraction into account 164 EV-DO acceptable noise rise margin, defining (CDMA) 673 active set size on reverse link on terminal (CDMA) 715 application throughput, defining for EV-DO Rev. 0 (CDMA)
712

point analysis 688 power control simulation algorithm 757 preferred carrier, defining for EV-DO Rev. 0 (CDMA) 712 preferred carrier, defining for EV-DO Rev. A (CDMA) 713 priority, defining for EV-DO Rev. 0 (CDMA) 712 priority, defining for EV-DO Rev. A (CDMA) 713 rate control, using to study capacity (CDMA) 746 rate probabilities UL, defining for EV-DO Rev. 0 (CDMA)
712

rate probabilities UL, defining for EV-DO Rev. A (CDMA)

713

Rev.0 reverse link data rates 711 reverse link power control 756 reverse link radio bearer index 801 reverse link radio bearer, defining 801 service area (Eb/Nt) reverse link, studying (CDMA) 719 service parameters, EV-DO Rev. 0-specific (CDMA) 712 service parameters, EV-DO Rev. A-specific (CDMA) 713 service parameters, EV-DO-specific (CDMA) 711 simulation results, cells (CDMA) 764 simulation results, maximum number of channel elements per carrier (CDMA) 762 simulation results, mobiles (CDMA) 765 simulation results, number of channel elements (CDMA)
763

application throughput, defining for EV-DO Rev. A (CDMA)

713

BCMCS throughput, defining (CDMA) 673 body loss, defining for EV-DO Rev. 0 (CDMA) 713 body loss, defining for EV-DO Rev. A (CDMA) 713 carrier type, defining globally (CDMA) 799 carrier type, defining in cell (CDMA) 671 carriers, parameters for (CDMA) 672 data rates, available (CDMA) 800 DRC error rate, defining (CDMA) 673 FCH active set size on terminal (CDMA) 715 forward link radio bearer index 801 forward link radio bearer, defining 801 forward link throughput, studying (CDMA) 718 handoff status coverage prediction (CDMA) 724 idle power gain, defining (CDMA) 672 max channel elements per carrier, equipment (CDMA) 669 max rate = f/C/1), defining for mobility (CDMA) 714 maximum number of users per cell, defining (CDMA) 673 maximum power transmitted, defining (CDMA) 672 maximum UL load factor, defining (CDMA) 673 min. Ec/Nt (UL), defining for mobility (CDMA) 714 mobility type parameters 714 MUG table, defining (CDMA) 672 noise rise threshold, defining (CDMA) 672 pilot pollution, calculating (CDMA) 723
Forsk 2010

simulation results, number of channel elements due to SHO overhead (CDMA) 763 simulation results, rejected users due to EV-DO resources saturation (CDMA) 764, 768 terminal options, EV-DO Rev. 0-specific (CDMA) 716 terminal options, EV-DO Rev. A-specific (CDMA) 716 terminal parameters, EV-DO Rev. 0-specific (CDMA) 714 terminal parameters, EV-DO Rev. A-specific (CDMA) 715 timeslots dedicated to BCMCS (CDMA) 673 timeslots dedicated to control channels (CDMA) 673 total transmitted power on DL, defining (CDMA) 673 transition flag in traffic simulations, assigned 756 UL load factor, defining (CDMA) 673 UL throughput due to TCP acknowledgement, defining for EV-DO Rev. 0 (CDMA) 713 EV-DO Rev. A forward link radio bearer defining (CDMA) 801 EV-DO Rev. A reverse link radio bearer defining (CDMA) 801 exceptional pairs inter-technology, displaying (CDMA) 788 inter-technology, displaying (LTE) 1329 inter-technology, displaying (TD-SCDMA) 943 inter-technology, displaying (UMTS) 640 inter-technology, displaying (WiMAX) 1128 inter-technology, setting (CDMA) 787 inter-technology, setting (LTE) 1328 inter-technology, setting (TD-SCDMA) 942 inter-technology, setting (UMTS) 640 inter-technology, setting (WiMAX) 1128 inter-technology, setting on the map (CDMA) 788 inter-technology, setting on the map (LTE) 1329 inter-technology, setting on the map (TD-SCDMA) 943 inter-technology, setting on the map (UMTS) 641

Unauthorized reproduction or distribution of this document is prohibited

1369

Atoll User Manual

inter-technology, setting on the map (WiMAX) 1129 neighbour, defining (CDMA) 728 PN offsets, defining (CDMA) 739 exceptional pairs, defining neighbour (GSM) 242 exceptional pairs, defining neighbour (LTE) 1225 exceptional pairs, defining neighbour (TD-SCDMA) 882 exceptional pairs, defining neighbour (UMTS) 529 exceptional pairs, defining neighbour (WiMAX) 1023 exceptional pairs, defining scrambling code (TD-SCDMA) 893 exceptional pairs, defining scrambling code (UMTS) 542 experience matrix, see "separation rules" Explorer window 27 Data tab 27 Geo tab 27 layers 28 Modules tab 27 using tabs 27 extended cell defining (GSM) 415

F
fast link adaptation (TD-SCDMA) 916 fast link adaptation (UMTS) 560 feeder assigning (CDMA) 670 assigning (GSM) 195 assigning (TD-SCDMA) 814 assigning (UMTS) 469 defining cables 147 defining length (CDMA) 670 defining length (TD-SCDMA) 814 defining length (UMTS) 469 length, defining (GSM) 195 length, defining (LTE) 1175 length, defining (WiMAX) 971 feeder, assigning (LTE) 1175 feeder, assigning (WiMAX) 971 FER coverage prediction (CDMA) 721 FER coverage prediction (UMTS) 519 field adding to a table 54 deleting from a table 55 filitering zone importing 42 filter site list, using for 81 transmitter list, using for 81 filtering data tables by selection 74 data tables by several criteria 75 examples 76 restoring after filtering 76 using a polygon 41, 84 with subfolders 83 filtering zone deleting 45 drawing 41 Fit to Map Window 42

polygon, creating from 42 Find toolbar 85 focus zone creating 43 creating (CDMA) 703 creating (GSM) 234 creating (LTE) 1202 creating (TD-SCDMA) 852 creating (UMTS) 503 creating (WiMAX) 999 editing 46 explanation 43 explanation (CDMA) 703 explanation (GSM) 234 explanation (TD-SCDMA) 852 explanation (UMTS) 503 Fit to Map Window 43 Fit to Map Window (CDMA) 703 Fit to Map Window (GSM) 234 Fit to Map Window (LTE) 1203 Fit to Map Window (TD-SCDMA) 853 Fit to Map Window (UMTS) 503 Fit to Map Window (WiMAX) 1000 importing 43 importing (CDMA) 703 importing (GSM) 234 importing (LTE) 1203 importing (TD-SCDMA) 852 importing (UMTS) 503 importing (WiMAX) 1000 polygon, creating from 43 polygon, creating from (CDMA) 703 polygon, creating from (GSM) 234 polygon, creating from (LTE) 1203 polygon, creating from (TD-SCDMA) 852 polygon, creating from (UMTS) 503 polygon, creating from (WiMAX) 1000 population statistics (CDMA) 704 population statistics (GSM) 236 population statistics (LTE) 1204 population statistics (TD-SCDMA) 854 population statistics (UMTS) 505 population statistics (WiMAX) 1001 using to display coverage prediction report 43 using to display coverage prediction report (CDMA) 703 using to display coverage prediction report (GSM) 234 using to display coverage prediction report (TD-SCDMA)
852

using to display coverage prediction report (UMTS) 503 folder configuration 82 applying a saved configuration 82 creating 82 deleting 83 exporting 83 importing 83 reapplying current configuration 82 forward link radio bearer index, EV-DO 801 forward link radio bearer, EV-DO, defining 801
Unauthorized reproduction or distribution of this document is prohibited Forsk 2010

1370

Index

forward link total power, setting (CDMA) 710 frame configuration creating (WiMAX) 1143 frame configuration (WiMAX) 974, 1143 Frame details (LTE) 1352 frame duration (LTE) 1343 frame duration (WiMAX) 1140 frequencies allocating manually (LTE) 1237 allocating manually (WiMAX) 1035 automatically allocating (LTE) 1236 automatically allocating (WiMAX) 1034 displaying allocation (LTE) 1237 displaying allocation (WiMAX) 1035 displaying on transmitter (LTE) 1238 displaying on transmitter (WiMAX) 1036 grouping transmitters by (GSM) 343 grouping transmitters by (LTE) 1238 grouping transmitters by (WiMAX) 1036 using Search Tool with (LTE) 1237 using Search Tool with (WiMAX) 1035 frequencies (TD-SCDMA) allocating automatically 880 displaying on the map 881 frequency allocation displaying on transmitter (GSM) 342 frequency bands defining (CDMA) 798 defining (GSM) 271 defining (LTE) 1341 defining (TD-SCDMA) 814, 953 defining (UMTS) 468, 652 defining (WiMAX) 1139 frequency domains defining (GSM) 271 frequency groups defining (GSM) 271 frequency, planning (TD-SCDMA) 879

global scaling factor (UMTS) 577 global scaling factor (WiMAX) 1068 global transmitter parameters modifying (CDMA) 799 modifying (LTE) 1343 modifying (TD-SCDMA) 955 modifying (UMTS) 654 modifying (WiMAX) 1142 global transmitter parameters (CDMA) 799 global transmitter parameters (LTE) 1342 global transmitter parameters (TD-SCDMA) 953 global transmitter parameters (UMTS) 653 global transmitter parameters (WiMAX) 1140 GPRS/EGPRS coding schemes coverage prediction (GSM)
328

GPRS/EGPRS equipment coding scheme thresholds, adapting (GSM) 413 coding scheme throughput graphs, displaying (GSM) 413 terminals, assigning to (GSM) 413 transmitters, assigning to (GSM) 413 grid of beams (GOB) smart antenna model (TD-SCDMA) 955 grid of beams (GOB), creating (TD-SCDMA) 956 grid of beams (GOB), import format (TD-SCDMA) 957 grid of beams (GOB), importing (TD-SCDMA) 956 grouping 69 by a property 69 by several properties 70 examples 71 with subfolders 83 groups, creating scrambling code (TD-SCDMA) 893 groups, creating scrambling code (UMTS) 542 GSM/GPRS/EGPRS template 93

H
handoff status coverage prediction (CDMA) 724 displaying traffic distribution by (CDMA) 760 handover status displaying traffic distribution by (TD-SCDMA) 918 displaying traffic distribution by (UMTS) 565 handover status coverage prediction (UMTS) 522 happy bit (UMTS) 562 HCS layers defining (GSM) 400 selecting (GSM) 194 hexagonal design definition (CDMA) 675 definition (GSM) 204 definition (LTE) 1180 definition (TD-SCDMA) 821 definition (UMTS) 475 definition (WiMAX) 977 hiding (CDMA) 675 histogram PN offsets (CDMA) 744 results, viewing ACP 388, 624, 1113, 1314 viewing coverage prediction (CDMA) 705 histogram, physical cell ID 1243

G
gain defining antenna 143 Geo tab 27 geographic export zone creating 46 creating (CDMA) 727 creating (GSM) 241 creating (LTE) 1225 creating (TD-SCDMA) 879 creating (UMTS) 528 creating (WiMAX) 1022 Fit to Map Window 46 importing 46 polygon, creating from 46 global scaling factor (CDMA) 771 global scaling factor (GSM) 265 global scaling factor (LTE) 1269 global scaling factor (TD-SCDMA) 928
Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1371

Atoll User Manual

histogram, preamble index 1041 histogram, scrambling code 547, 899 histogram, viewing coverage prediction (GSM) 236 histogram, viewing coverage prediction (LTE) 1204 histogram, viewing coverage prediction (TD-SCDMA) 854 histogram, viewing coverage prediction (UMTS) 505 histogram, viewing coverage prediction (WiMAX) 1001 hopping gain advanced modelling (GSM) 421 hot spot zone creating 43 creating (CDMA) 703 creating (GSM) 234 creating (LTE) 1202 creating (TD-SCDMA) 852 creating (UMTS) 503 creating (WiMAX) 999 editing 46 explanation 43 explanation (CDMA) 703 explanation (GSM) 234 explanation (TD-SCDMA) 852 explanation (UMTS) 503 Fit to Map Window 43 Fit to Map Window (CDMA) 703 Fit to Map Window (GSM) 234 Fit to Map Window (LTE) 1203 Fit to Map Window (TD-SCDMA) 853 Fit to Map Window (UMTS) 503 Fit to Map Window (WiMAX) 1000 importing 43 importing (CDMA) 703 importing (GSM) 234 importing (LTE) 1203 importing (TD-SCDMA) 852 importing (UMTS) 503 importing (WiMAX) 1000 population statistics (CDMA) 704 population statistics (GSM) 236 population statistics (LTE) 1204 population statistics (TD-SCDMA) 854 population statistics (UMTS) 505 population statistics (WiMAX) 1001 using to display coverage prediction report 43 using to display coverage prediction report (CDMA) 703 using to display coverage prediction report (GSM) 234 using to display coverage prediction report (TD-SCDMA)
852

template 94 terminal, enabling 513, 862 user equipment category 514, 515, 862 HSDPA radio bearer defining (TD-SCDMA) 961 defining (UMTS) 655 HSN domains, defining (GSM) 273 groups, defining (GSM) 273 HSPA+ activating 472, 479 HSUPA activating 472, 479 configuring 473 coverage prediction 527 editing user equipment category 659 service, enabling 511, 859 template 94 terminal, enabling 513, 862 HSUPA radio bearer defining (UMTS) 655

I
idle power gain, defining for EV-DO cells (CDMA) 672 indoor coverage ACP 348, 581, 1070, 1271 activating in AS analysis (CDMA) 726, 746 activating in AS analysis (UMTS) 524, 549 activating in coverage prediction (CDMA) 690 activating in coverage prediction (TD-SCDMA) 837, 844,
846, 847, 848, 850, 899

activating in coverage prediction (UMTS) 491 activating in point analysis (CDMA) 688, 702 activating in point analysis (TD-SCDMA) 835, 852 activating in point analysis (UMTS) 489, 503 activating in simulation (CDMA) 720, 722 activating in simulation (UMTS) 518, 520 calculating 181, 187 coverage prediction, activating in (GSM) 217 coverage prediction, activating in (LTE) 1190 coverage prediction, activating in (WiMAX) 987 defining when modelling environment (CDMA) 750 defining when modelling environment (LTE) 1247 defining when modelling environment (TD-SCDMA) 908 defining when modelling environment (UMTS) 553 defining when modelling environment (WiMAX) 1045 defining when modelling user profile traffic map (CDMA)
751

using to display coverage prediction report (UMTS) 503 HSDPA activating 472, 817 bearer selection, explanation 560, 916 configuring 472, 817 coverage prediction 525, 877 editing user equipment category 659, 963 scheduler algorithm 472 scheduler algorithm (TD-SCDMA) 818 service, enabling 511, 859

defining when modelling user profile traffic map (LTE) 1248 defining when modelling user profile traffic map (TD-SCDMA) 910 defining when modelling user profile traffic map (UMTS)
554

defining when modelling user profile traffic map (WiMAX)

1046

in traffic map (CDMA) 748 in traffic map (TD-SCDMA) 906 in traffic map (UMTS) 551 point analysis, activating in (GSM) 216, 234, 326
Forsk 2010

1372

Unauthorized reproduction or distribution of this document is prohibited

Index

point analysis, activating in (LTE) 1224 point analysis, activating in (WiMAX) 1021 simulation results (CDMA) 765, 766 simulation results (LTE) 1265 simulation results (TD-SCDMA) 922 simulation results (UMTS) 570 simulation results (WiMAX) 1063 indoor losses 181, 187 Interactive Frequency Allocation (GSM) 314 inter-carrier interference defining (CDMA) 798 inter-carrier interference, defining (TD-SCDMA) 953 inter-carrier interference, defining (UMTS) 652 interfered zones coverage prediction (GSM) 323 interference inter-carrier, defining (CDMA) 798 inter-carrier, defining (TD-SCDMA) 953 inter-carrier, defining (UMTS) 652 intermodulation See "intermodulation interference" Sector-to-Sector Interference Tool, using with (GSM) 337 interference reduction factor using assistant (MW) 149 interference zone coverage prediction, PN offset (CDMA) 745 interference zone coverage prediction, scrambling code (TD-SCDMA) 899 interference zone coverage prediction, scrambling code (UMTS) 548 interferer reception threshold defining (GSM) 421 intermodulation interference in calculations 422 Inter-technology DL Noise Rise (CDMA) 672 Inter-technology DL Noise Rise (GSM) 201 Inter-technology DL Noise Rise (LTE) 1178 Inter-technology DL Noise Rise (UMTS) 472 Inter-technology DL Noise Rise (WiMAX) 974 Inter-technology UL Noise Rise (CDMA) 671 Inter-technology UL Noise Rise (LTE) 1178 Inter-technology UL Noise Rise (UMTS) 471 Inter-technology UL Noise Rise (WiMAX) 974 ITU 1546 propagation model 166 ITU 370-7 propagation model (Vienna 93) 162, 164 ITU 526-5 propagation model 165 ITU 529-3 propagation model assigning environment formulas 163 creating environment formula 163 defining default environment formula 163 modifying environment formula 163 taking diffraction into account 163 Iub backhaul throughput defining consumption per site equipment-HSUPA radio bearer (UMTS) 657 defining consumption per site equipment-R99 radio bearer (UMTS) 657

joint detection factor defining in site equipment (TD-SCDMA) 962

L
label 35 Lambert Conformal-Conic projection 96 layers 28 legend adding object type 36 displaying 37 displaying Legend window 41 displaying window in co-planning (CDMA) 785 displaying window in co-planning (LTE) 1327 displaying window in co-planning (TD-SCDMA) 941 displaying window in co-planning (UMTS) 638 displaying window in co-planning (WiMAX) 1126 printing Legend window 68 legend, displaying (CDMA) 701 legend, displaying (GSM) 233 legend, displaying (LTE) 1201 legend, displaying (TD-SCDMA) 851 legend, displaying (UMTS) 502 legend, displaying (WiMAX) 998 lines editing 46 Location Finder searching by coordinates 86 searching by text property 85 Longley-Rice propagation model 166 LTE 1171 cyclic prefix ratio 1342 frame duration 1343 glossary 1357 template 94 LTE radio bearer defining 1344 definition 1243 LTE schedulers defining 1348 scheduling methods 1347 LTE, definition 1171

M
macro-diversity gain clutter class, displaying per (CDMA) 804 clutter class, displaying per (UMTS) 661 map centring on a selected object 40 exporting as image 52 measuring distances 40 moving 39 printing 65 refreshing display 85 saving as image 51 Map toolbar 87 master carrier (TD-SCDMA) 879 masthead amplifier, see "TMA" matrix, see "path loss matrix"

J
JD, see "joint detection"

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1373

Atoll User Manual

max number of inter-carrier neighbours (CDMA) 672 max number of inter-technology neighbours (CDMA) 672 max number of intra-carrier neighbours (CDMA) 672 maximum UL load factor (CDMA) 673 measurement units, setting 97 measuring distances on the map 40 MIMO adaptive MIMO switch (LTE) 1349 adaptive MIMO switch (WiMAX) 1153 collaborative MIMO (LTE) 1350 collaborative MIMO (WiMAX) 1154 maximum ratio combining (WiMAX) 1153 MU-MIMO (LTE) 1350 MU-MIMO (WiMAX) 1154 number of antenna ports, defining (LTE) 1176 number of antennas, defining (WiMAX) 972 receive diversity (LTE) 1349 receive diversity (UMTS HSPA) 660 space-time transmit diversity (WiMAX) 1153 space-time transmit diversity gains (WiMAX) 1147 spatial multiplexing (LTE) 1349 Spatial multiplexing (UMTS HSPA) 660 spatial multiplexing (WiMAX) 1153 spatial multiplexing gains (LTE) 1346 spatial multiplexing gains (WiMAX) 1147 SU-MIMO (LTE) 1349 SU-MIMO (WiMAX) 1153 transmit diversity (LTE) 1349 transmit diversity (UMTS HSPA) 660 transmit diversity gains (LTE) 1346 Min Ec/Nt (UL) (CDMA) 714 mobility type creating (CDMA) 714 creating (GSM) 419 creating (LTE) 1211 creating (TD-SCDMA) 861 creating (UMTS) 513 creating (WiMAX) 1008 definition (CDMA) 746 definition (GSM) 254 definition (LTE) 1244 definition (TD-SCDMA) 905 definition (UMTS) 550 definition (WiMAX) 1042 EV-DO Rev. 0 parameters (CDMA) 714 modelling (GSM) 419 modifying (CDMA) 714 modifying (GSM) 419 modifying (LTE) 1211 modifying (TD-SCDMA) 861 modifying (UMTS) 513 modifying (WiMAX) 1008 parameters used in predictions (CDMA) 714 parameters used in predictions (TD-SCDMA) 860 parameters used in predictions (UMTS) 513 mobility types table displaying (GSM) 419 Modules tab 27

Monte-Carlo-based user distribution (CDMA) 756 Monte-Carlo-based user distribution (TD-SCDMA) 914 Monte-Carlo-based user distribution (UMTS) 559 MS Access, connecting to 99 MUD, see "multi-user detection" MUG table defining for EV-DO cells (CDMA) 672 multi-band network, creating (LTE) 1186 multi-band network, creating (WiMAX) 983 multi-band transmitters modelling (GSM) 415 multi-carrier network (CDMA) 671 multi-carrier network (TD-SCDMA) 816 multi-carrier network (UMTS) 470 multi-service traffic data (GSM) 418 multi-user detection factor defining in site equipment (CDMA) 802 defining in site equipment (UMTS) 656 defining in terminals (TD-SCDMA) 862 defining in terminals (UMTS) 514 mult-user environment 97

N
neighbours allocating automatically (CDMA) 728 allocating automatically (GSM) 243 allocating automatically (LTE) 1226 allocating automatically (TD-SCDMA) 883 allocating automatically (UMTS) 530 allocating automatically (WiMAX) 1023 allocating on the map (CDMA) 736 allocating on the map (GSM) 249 allocating on the map (LTE) 1232 allocating on the map (TD-SCDMA) 889 allocating on the map (UMTS) 538 allocating on the map (WiMAX) 1030 allocating per cell (CDMA) 734 allocating per cell (LTE) 1231 allocating per cell (TD-SCDMA) 887 allocating per cell (UMTS) 536 allocating per cell (WiMAX) 1029 allocating per transmitter (GSM) 248 allocating using Cells tab of Transmitter Properties (CDMA) 734 allocating using Cells tab of Transmitter Properties (LTE)
1231

allocating using Cells tab of Transmitter Properties (TD-SCDMA) 888 allocating using Cells tab of Transmitter Properties (UMTS) 536 allocating using Cells tab of Transmitter Properties (WiMAX) 1029 allocating using Intra-Technology Neighbours tab of Transmitter Properties (GSM) 248 allocating using Neighbours table (CDMA) 735 allocating using Neighbours table (GSM) 249 allocating using Neighbours table (LTE) 1232 allocating using Neighbours table (TD-SCDMA) 888 allocating using Neighbours table (UMTS) 537
Forsk 2010

1374

Unauthorized reproduction or distribution of this document is prohibited

Index

allocating using Neighbours table (WiMAX) 1029 audit of allocation (CDMA) 738 audit of allocation (GSM) 251 audit of allocation (LTE) 1234 audit of allocation (TD-SCDMA) 891 audit of allocation (UMTS) 540 audit of allocation (WiMAX) 1032 audit of inter-technology (CDMA) 796 audit of inter-technology (LTE) 1338 audit of inter-technology (TD-SCDMA) 951 audit of inter-technology (UMTS) 649 audit of inter-technology (WiMAX) 1136 comparing existing and allocated (CDMA) 730, 731 comparing existing and allocated (GSM) 244 comparing existing and allocated (LTE) 1228 comparing existing and allocated (TD-SCDMA) 884 comparing existing and allocated (UMTS) 531, 533 comparing existing and allocated (WiMAX) 1025 configuring importance (CDMA) 529, 728 configuring importance (GSM) 242 configuring importance (LTE) 1226 configuring importance (TD-SCDMA) 883 configuring importance (WiMAX) 1023 configuring importance in co-planning (CDMA) 789 configuring importance in co-planning (LTE) 1330 configuring importance in co-planning (TD-SCDMA) 944 configuring importance in co-planning (UMTS) 642 configuring importance in co-planning (WiMAX) 1130 defining exceptional pairs of (LTE) 1225 defining exceptional pairs of (TD-SCDMA) 882 defining exceptional pairs of (UMTS) 529 defining exceptional pairs of (WiMAX) 1023 deleting on the map (CDMA) 736 deleting on the map (GSM) 249 deleting on the map (LTE) 1232 deleting on the map (TD-SCDMA) 889 deleting on the map (UMTS) 538 deleting on the map (WiMAX) 1030 deleting per cell (CDMA) 734 deleting per cell (LTE) 1231 deleting per cell (TD-SCDMA) 887 deleting per cell (UMTS) 536 deleting per cell (WiMAX) 1029 deleting per transmitter (GSM) 248 deleting using Cells tab of Transmitter Properties (CDMA)
734

deleting using Neighbours table (TD-SCDMA) 888 deleting using Neighbours table (UMTS) 537 deleting using Neighbours table (WiMAX) 1029 displaying (CDMA) 732 displaying (GSM) 245 displaying (LTE) 1229 displaying (TD-SCDMA) 885 displaying (UMTS) 534 displaying (WiMAX) 1026 displaying coverage (CDMA) 733 displaying coverage (LTE) 1230 displaying coverage (TD-SCDMA) 887 displaying coverage (UMTS) 535 displaying coverage (WiMAX) 1028 displaying coverage of (GSM) 247 exceptional pairs of, defining (CDMA) 728 exceptional pairs of, defining (GSM) 242 exporting (CDMA) 739 exporting (GSM) 252 exporting (LTE) 1235 exporting (TD-SCDMA) 892 exporting (UMTS) 541 exporting (WiMAX) 1033 importing (CDMA) 727 importing (GSM) 242 importing (LTE) 1225 importing (TD-SCDMA) 887 importing (UMTS) 529 importing (WiMAX) 1022 intertechnology, allocating (CDMA) 787 intertechnology, allocating (LTE) 1328 intertechnology, allocating (TD-SCDMA) 942 intertechnology, allocating (UMTS) 640 intertechnology, allocating (WiMAX) 1128 inter-technology, allocating automatically (CDMA) 789 inter-technology, allocating automatically (LTE) 1330 inter-technology, allocating automatically (TD-SCDMA)
944

deleting using Cells tab of Transmitter Properties (LTE)

1231

inter-technology, allocating automatically (UMTS) 642 inter-technology, allocating automatically (WiMAX) 1130 inter-technology, allocating per cell (CDMA) 792 inter-technology, allocating per cell (LTE) 1333 inter-technology, allocating per cell (TD-SCDMA) 947 inter-technology, allocating per cell (UMTS) 645 inter-technology, allocating per cell (WiMAX) 1132 inter-technology, allocating using Neighbours table (CDMA) 793 inter-technology, allocating using Neighbours table (LTE)
1334

deleting using Cells tab of Transmitter Properties (TD-SCDMA) 888 deleting using Cells tab of Transmitter Properties (UMTS)
536

deleting using Cells tab of Transmitter Properties (WiMAX)

1029

deleting using Intra-Technology Neighbours tab of Transmitter Properties (GSM) 248 deleting using Neighbours table (CDMA) 735 deleting using Neighbours table (GSM) 249 deleting using Neighbours table (LTE) 1232
Forsk 2010

inter-technology, allocating using Neighbours table (TD-SCDMA) 948 inter-technology, allocating using Neighbours table (UMTS) 646 inter-technology, allocating using Neighbours table (WiMAX) 1133 inter-technology, comparing existing and allocated (CDMA) 791 inter-technology, comparing existing and allocated (LTE)
1332

Unauthorized reproduction or distribution of this document is prohibited

1375

Atoll User Manual

inter-technology, comparing existing and allocated (TD-SCDMA) 946 inter-technology, comparing existing and allocated (UMTS) 644 inter-technology, comparing existing and allocated (WiMAX) 1131 inter-technology, displaying (CDMA) 791 inter-technology, displaying (LTE) 1333 inter-technology, displaying (TD-SCDMA) 946 inter-technology, displaying (UMTS) 644 inter-technology, displaying (WiMAX) 1131 inter-technology, setting on the map (CDMA) 794 inter-technology, setting on the map (LTE) 1335 inter-technology, setting on the map (TD-SCDMA) 949 inter-technology, setting on the map (UMTS) 647 inter-technology, setting on the map (WiMAX) 1134 possible (CDMA) 727 possible (GSM) 241 possible (LTE) 1225 possible (TD-SCDMA) 882 possible (UMTS) 528 possible (WiMAX) 1022 network capacity calculating (TD-SCDMA) 901 dimensioning (TD-SCDMA) 902 displaying network load on the map (TD-SCDMA) 904 displaying on the map (TD-SCDMA) 901, 903 network, creating dual-band (CDMA) 682 network, creating dual-band (TD-SCDMA) 828 network, creating dual-band (UMTS) 483 network, creating multi-band (LTE) 1186 network, creating multi-band (WiMAX) 983 N-frequency mode (TD-SCDMA) carrier types 879 definition 879 setting up 880 noise rise threshold, defining for EV-DO cells (CDMA) 672 non-symmetric neighbours, displaying (CDMA) 732 non-symmetric neighbours, displaying (GSM) 245 non-symmetric neighbours, displaying (LTE) 1229 non-symmetric neighbours, displaying (TD-SCDMA) 885 non-symmetric neighbours, displaying (UMTS) 534 non-symmetric neighbours, displaying (WiMAX) 1026

OFDM, definition (WiMAX) 967 Okumura-Hata model 160, 161 Okumura-Hata propagation model 160, 161 assigning environment formulas 160 creating environment formula 161 defining default environment formula 160 modifying environment formula 161 taking diffraction into account 160 optimisation creating new ACP process 353, 586, 1075, 1277 creating new co-planning ACP process 651, 1138, 1340 defining ACP optimisation (GSM) 354 defining ACP optimisation (LTE) 1277 defining ACP optimisation (UMTS) 587 defining ACP optimisation (WiMAX) 1076 deleting 375, 611, 1100, 1301 importing second technology 651, 1138, 1340 properties, changing 375, 611, 1100, 1301 running 375, 611, 1100, 1301 running ACP process 354, 587, 1076, 1277 running saved ACP 373, 609, 1098, 1299 optimum beamformer modelling (TD-SCDMA) 957 optimum beamformer modelling (WiMAX) 1151 Oracle, connecting to 99 overlapping zones coverage prediction (CDMA) 700 overlapping zones coverage prediction (GSM) 232 overlapping zones coverage prediction (LTE) 1199 overlapping zones coverage prediction (UMTS) 500 overlapping zones coverage prediction (WiMAX) 996 OVSF codes calculation of consumption (TD-SCDMA) 915 calculation of consumption (UMTS) 560 default orthogonality factor (UMTS) 653 maximum number of codes available for HS-PDSCH (TD-SCDMA) 818 maximum number of codes available for HS-PDSCH (UMTS) 472 minimum number of codes available for HS-PDSCH (TD-SCDMA) 818 minimum number of codes available for HS-PDSCH (UMTS) 472 simulations (UMTS) 564

P
packet throughput per timeslot coverage prediction (GSM) 331 Page Setup, see "printing" Panoramic window 26, 39 Path loss calculation 158, 159 Radial 158, 159 Systematic 158, 159 path loss matrices adjusting using CW measurements 174, 175 defining area to be adjusted with measurement data 173 tuning using measurement data 173 path loss matrix calculation process (CDMA) 695 calculation process (GSM) 223 calculation process (LTE) 1195

O
objects changing transparency 35 deleting 29 displaying 28 displaying properties 30 grouping 69 grouping by a property 69 grouping by several properties 70 grouping, examples 71 hiding 28 label 35 tip text 36 visibility scale 35

1376

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Index

calculation process (WiMAX) 992 checking validity (CDMA) 693 checking validity (GSM) 220 checking validity (LTE) 1192 checking validity (TD-SCDMA) 839 checking validity (UMTS) 494 checking validity (WiMAX) 989 exporting 179 resolution (CDMA) 676 resolution (GSM) 205, 417 resolution (LTE) 1181 resolution (TD-SCDMA) 822 resolution (UMTS) 477 resolution (WiMAX) 978 storing 171 storing (CDMA) 692 storing (GSM) 219 storing (LTE) 1191 storing (TD-SCDMA) 838 storing (UMTS) 493 storing (WiMAX) 988 validity, checking 172 path lost matrix calculation process (TD-SCDMA) 842 calculation process (UMTS) 496 pattern electrical tilt 143 P-CCPCH pollution coverage prediction (TD-SCDMA) 846 permutation zone creating (WiMAX) 1143 permutation zone (WiMAX) 1143 physical cell IDs allocating manually (LTE) 1240 audit of plan (LTE) 1241 automatically allocating (LTE) 1239 displaying allocation (LTE) 1241 displaying on transmitter (LTE) 1242 grouping transmitters by (LTE) 1242 histogram (LTE) 1243 using Search Tool with (LTE) 1241 physical cell IDs (LTE) 1239 pilot minimum RSCP threshold, defining (CDMA) 716 minimum RSCP threshold, defining (TD-SCDMA) 862 minimum RSCP threshold, defining (UMTS) 515 pilot channel, power control for EV-DO (CDMA) 756 pilot pollution coverage prediction (CDMA) 723 pilot pollution coverage prediction (UMTS) 521 pilot power reconfiguration with ACP 361, 579, 594, 1084, 1285 pilot reception analysis (Ec/I0) based on test mobile data path (UMTS) 630, 778 pilot signal quality coverage prediction (CDMA) 716 pilot signal quality coverage prediction (TD-SCDMA) 863 pilot signal quality coverage prediction (UMTS) 515 Planet importing antennas 144 PN offsets audit of plan (CDMA) 742
Forsk 2010

automatically allocating (CDMA) 740 defining constraint costs (CDMA) 740 defining per cell (CDMA) 671 displaying allocation (CDMA) 743 displaying on transmitter (CDMA) 744 domain, defining per cell (CDMA) 671 exceptional pairs, defining (CDMA) 739 grouping transmitters by (CDMA) 744 histogram (CDMA) 744 interference zone coverage prediction (CDMA) 745 manually allocating (CDMA) 742 reuse distance, defining per cell (CDMA) 671 using Search Tool with (CDMA) 743 PN offsets (CDMA) 739 point analysis EV-DO (CDMA) 688 opening Point Analysis Tool window 180 shadowing, calculating 182 starting 180 Point Analysis window active set analysis of simulation (CDMA) 771 active set analysis of simulation (UMTS) 578 AS Analysis tab (CDMA) 725 AS Analysis tab (UMTS) 523 Interference tab (GSM) 325 Interference tab (LTE) 1223 Interference tab (WiMAX) 1021 printing 68 Profile tab (CDMA) 688 Profile tab (GSM) 215 Profile tab (LTE) 1187 Profile tab (TD-SCDMA) 834 Profile tab (UMTS) 489 Profile tab (WiMAX) 984 Reception tab (CDMA) 702 Reception tab (GSM) 233 Reception tab (LTE) 1201 Reception tab (TD-SCDMA) 852 Reception tab (UMTS) 502 Reception tab (WiMAX) 998 Results tab (LTE) 1224 Results tab (WiMAX) 1021 points editing 46 polygon computation zone, using as (GSM) 224 deleting polygon filter 45 drawing a polygon filter 41 editing 46 focus zone, using as 43 focus zone, using as (CDMA) 703 focus zone, using as (GSM) 234 focus zone, using as (LTE) 1203 focus zone, using as (TD-SCDMA) 852 focus zone, using as (UMTS) 503 focus zone, using as (WiMAX) 1000 geographic export zone, using as 46 printing zone, using as 66

Unauthorized reproduction or distribution of this document is prohibited

1377

Atoll User Manual

using as computation zone 42 using as computation zone (CDMA) 696 using as computation zone (LTE) 1195 using as computation zone (TD-SCDMA) 842 using as computation zone (UMTS) 497 using as computation zone (WiMAX) 992 using as filter 41, 84 using as filtering zone 42 population statistics including in report (CDMA) 704 including in report (TD-SCDMA) 854 including in report (UMTS) 505 integrable data (CDMA) 704 integrable data (GSM) 236 integrable data (TD-SCDMA) 854 integrable data (UMTS) 505 report, including in (GSM) 236 possible neighbours, definition (CDMA) 727 possible neighbours, definition (GSM) 241 possible neighbours, definition (LTE) 1225 possible neighbours, definition (TD-SCDMA) 882 possible neighbours, definition (UMTS) 528 possible neighbours, definition (WiMAX) 1022 power maximum power in cells, defining (CDMA) 672 maximum power transmitted by EV-DO cells, defining (CDMA) 672 paging power in cells, defining (CDMA) 672 pilot power in cells, defining (CDMA) 672 synchro power in cells, defining (CDMA) 672 power control simulation algorithm EV-DO 757 power control simulation algorithm (CDMA) 756 power control simulation algorithm (TD-SCDMA) 914 power control simulation algorithm (UMTS) 559 power, defining defining DwPTS power in cells (TD-SCDMA) 817 defining maximum power in cells (TD-SCDMA) 816 defining maximum power in cells (UMTS) 471 defining other CCH power in cells (TD-SCDMA) 816 defining other CCH power in cells (UMTS) 471 defining P-CCPCH power in cells (TD-SCDMA) 816 defining pilot power in cells (UMTS) 471 defining SCH power in cells (UMTS) 471 defining UpPTS power (TD-SCDMA) 862 preamble analysis based on test mobile data path (WiMAX)
1119

preamble index (WiMAX) 974 preamble indexes allocating manually (WiMAX) 1038 audit of plan (WiMAX) 1039 automatically allocating (WiMAX) 1037 displaying allocation (WiMAX) 1039 displaying on transmitter (WiMAX) 1040 grouping transmitters by (WiMAX) 1040 histogram (WiMAX) 1041 using Search Tool with (WiMAX) 1039 preamble indexes (WiMAX) 1037

preamble power reconfiguration with ACP 1068 predictions overview 182 printing antenna patterns 68, 147 coverage prediction results (CDMA) 727 coverage prediction results (GSM) 241 coverage prediction results (LTE) 1225 coverage prediction results (TD-SCDMA) 879 coverage prediction results (UMTS) 528 coverage prediction results (WiMAX) 1022 CW Measurement Analysis Tool 68 data tables and reports 64 defining print layout 66 docking windows 68 Legend window 68 map 65 Point Analysis window 68 print preview 68 recommendations 65 Test Mobile Data Analysis Tool 68 printing zone drawing 65 Fit to Map Window 66 importing 66 polygon, creating from 66 Profile 158, 159 Radial extraction 158, 159 Systematic extraction 158, 159 projection coordinate system 96 Lambert Conformal-Conic projection 96 Universal Transverse Mercator projection 96 propagation model all transmitters, assigning to (GSM) 221 all transmitters, assigning to (LTE) 1193 all transmitters, assigning to (WiMAX) 990 assigning a default model for predictions 170, 695 assigning to a transmitter 695 assigning to a transmitter (TD-SCDMA) 841 assigning to a transmitter (UMTS) 496 assigning to all transmitters 169, 694 assigning to all transmitters (TD-SCDMA) 840 assigning to all transmitters (UMTS) 495 assigning to group of transmitters 169, 694 assigning to group of transmitters (TD-SCDMA) 841 assigning to group of transmitters (UMTS) 495 Cost-Hata 161 Cost-Hata, diffraction 161 default model for predictions, assigning (GSM) 223 Erceg-Greenstein (SUI) 164 Erceg-Greenstein (SUI), diffraction 164 group of transmitters, assigning to (GSM) 222 group of transmitters, assigning to (LTE) 1194 group of transmitters, assigning to (WiMAX) 991 ITU 1546 166 ITU 370-7 (Vienna 93) 162, 164 ITU 526-5 165
Forsk 2010

1378

Unauthorized reproduction or distribution of this document is prohibited

Index

ITU 529-3, diffraction 163 Longley-Rice 166 Okumura-Hata 160, 161 Okumura-Hata, diffraction 160 Sakagami extended 167 signature 168 Standard Propagation Model 154 Standard Propagation Model, correction factor for hilly regions 159 Standard Propagation Model, defining parameters 157 Standard Propagation Model, diffraction 155 Standard Propagation Model, recommendations 154 transmitter, assigning to (GSM) 222 transmitter, assigning to (LTE) 1194 transmitter, assigning to (WiMAX) 991 WLL 165 propagation models ACP, default 349, 582, 1071, 1272 ACP, natively supported 348, 581, 1070, 1272 ACP, using precalculated path loss matrices with 351, 584,
598, 1073, 1087, 1275, 1288

ACP, using precalculated pathlooss matrices with 349, 582,

1071, 1272

ACP, using with 348, 581, 1070, 1271 properties changing display 32 grouping objects by 69 switching between property dialogues 30 pseudo noise offset, see "PN offset" 671

Q
QoS Class, defining (WiMAX) 1007 quality indicator coverage prediction (CDMA) 721 quality indicator coverage prediction (LTE) 1221 quality indicator coverage prediction (UMTS) 519 quality indicator coverage prediction (WiMAX) 1019 quality indicators defining (LTE) 1344 defining (WiMAX) 1145

R
R99 radio bearer defining (TD-SCDMA) 960 defining (UMTS) 654 definition (TD-SCDMA) 905 definition (UMTS) 549 Radial 158, 159 radio configuration definition (CDMA) 746 radio resource management calculation of channel element consumption (UMTS) 560 calculation of OVSF code consumption (TD-SCDMA) 915 calculation of OVSF code consumption (UMTS) 560 calculation of resource unit consumption (TD-SCDMA) 915 channel element consumption per site equipmentterminal, defining (CDMA) 802 channel elements on forward link, defining (CDMA) 669 channel elements on reverse link, defining (CDMA) 669 channel elements, simulations (CDMA) 759
Forsk 2010

channel elements, simulations (UMTS) 564 default orthogonality factor (UMTS) 653 defining channel element consumption per site equipmentR99 radio bearer (UMTS) 657 defining channel elements on downlink (UMTS) 468 defining channel elements on uplink (UMTS) 468 maximum number of OVSF codes available for HSPDSCH (TD-SCDMA) 818 maximum number of OVSF codes available for HSPDSCH (UMTS) 472 minimum number of OVSF codes available for HS-PDSCH (TD-SCDMA) 818 minimum number of OVSF codes available for HS-PDSCH (UMTS) 472 orthogonality factor, default (CDMA) 799 OVSF codes, simulations (UMTS) 564 uplink and downlink channel element consumption (CDMA) 802 uplink and downlink channel element consumption (UMTS) 656 Walsh codes, simulations (CDMA) 759 radio reverse indicator channel gain (CDMA) 716 Radio toolbar 87 receiver defining height 657, 962 defining height (CDMA) 802 receiver antenna diversity gain, defining (CDMA) 670 receiver antenna diversity gain, defining (TD-SCDMA) 814 receiver antenna diversity gain, defining (UMTS) 469 reception equipment creating (CDMA) 803 creating (TD-SCDMA) 962 creating (UMTS) 658 modifying (CDMA) 803 modifying (TD-SCDMA) 962 modifying (UMTS) 658 reconfiguration importing ACP parameters 361, 364, 595, 599, 1088, 1289 redo 84 reflection smoothing vertical antenna pattern 146 refresh 85 from the database 101 Refresh Geo Data (GSM) 394 Refresh Geo Data (LTE) 1319 Refresh Geo Data (TD-SCDMA) 934 Refresh Geo Data (UMTS) 630 Refresh Geo Data (WiMAX) 1119 relativity clusters defining scrambling code (TD-SCDMA) 893 remote antenna copying into document (CDMA) 686 copying into document (GSM) 213 copying into document (TD-SCDMA) 832 copying into document (UMTS) 486 defining properties (CDMA) 686 defining properties (TD-SCDMA) 832 defining properties (UMTS) 487 importing (CDMA) 686

Unauthorized reproduction or distribution of this document is prohibited

1379

Atoll User Manual

importing (GSM) 213 importing (TD-SCDMA) 832 importing (UMTS) 486 placing on the map (CDMA) 685 placing on the map (GSM) 213 placing on the map (TD-SCDMA) 832 placing on the map (UMTS) 486 properties, defining (GSM) 213 renaming 29 default object names 29 repeater cascading (CDMA) 683 cascading (GSM) 210 cascading (TD-SCDMA) 829 cascading (UMTS) 484 copying into document (CDMA) 683 copying into document (GSM) 211 copying into document (TD-SCDMA) 830 copying into document (UMTS) 484 defining properties (CDMA) 683 defining properties (TD-SCDMA) 830 defining properties (UMTS) 484 definition (CDMA) 682 definition (GSM) 210 definition (TD-SCDMA) 828 definition (UMTS) 483 importing (CDMA) 683 importing (GSM) 211 importing (TD-SCDMA) 830 importing (UMTS) 484 placing on the map (CDMA) 683 placing on the map (GSM) 210 placing on the map (TD-SCDMA) 829 placing on the map (UMTS) 484 properties, defining (GSM) 211 repeater equipment creating (CDMA) 682 creating (GSM) 210 creating (TD-SCDMA) 829 creating (UMTS) 483 modifying (CDMA) 682 modifying (GSM) 210 modifying (TD-SCDMA) 829 modifying (UMTS) 483 report, displaying a coverage prediction (CDMA) 703 report, displaying a coverage prediction (GSM) 235 report, displaying a coverage prediction (LTE) 1203 report, displaying a coverage prediction (TD-SCDMA) 853 report, displaying a coverage prediction (UMTS) 504 report, displaying a coverage prediction (WiMAX) 1000 reports printing 64 resolution display (CDMA) 690 display (GSM) 217 display (TD-SCDMA) 836 display (UMTS) 491 path loss matrix (CDMA) 676

path loss matrix (GSM) 205, 417 path loss matrix (LTE) 1181 path loss matrix (TD-SCDMA) 822 path loss matrix (UMTS) 477 path loss matrix (WiMAX) 978 resource unit calculation of consumption (TD-SCDMA) 915 reverse link load factor, setting (CDMA) 710 reverse link radio bearer index, EV-DO 801 reverse link radio bearer, EV-DO, defining 801 Rho factor, BTS 148 row height changing 57 RRI, see "radio reverse indicator channel gain" RSCP threshold (CDMA) 716 RSCP threshold (TD-SCDMA) 862 RSCP threshold (UMTS) 515 RSCP UpPCH coverage prediction (TD-SCDMA) 849 RTT carrier type, defining globally (CDMA) 799 data rates, available (CDMA) 800 handoff status coverage prediction (CDMA) 724 power control based on, defining globally (CDMA) 799 power control simulation algorithm (CDMA) 756 service parameters, RTT-specific (CDMA) 711, 712 simulation results, cells (CDMA) 763 simulation results, mobiles (CDMA) 764 rulers displaying 40

S
Sakagami extended propagation model 167 scale level, choosing 39 SC-FDMA, definition (LTE) 1171 scheduler choosing the HSDPA scheduler algorithm 472 choosing the HSDPA scheduler algorithm (TD-SCDMA)
818

explanation of scheduling technique (TD-SCDMA) 916 explanation of scheduling technique (UMTS) 561 scrambling codes audit of plan (TD-SCDMA) 897 audit of plan (UMTS) 545 automatic allocation costs (TD-SCDMA) 895 automatically allocating (TD-SCDMA) 894 automatically allocating (UMTS) 543 creating domains and groups (TD-SCDMA) 893 creating domains and groups (UMTS) 542 defining available (TD-SCDMA) 893 defining available (UMTS) 542 defining constraint costs (TD-SCDMA) 894 defining constraint costs (UMTS) 543 defining exceptional pairs (TD-SCDMA) 893 defining exceptional pairs (UMTS) 542 defining format (TD-SCDMA) 892 defining format (UMTS) 542 defining relativity clusters (TD-SCDMA) 893 displaying allocation (TD-SCDMA) 897
Forsk 2010

1380

Unauthorized reproduction or distribution of this document is prohibited

Index

displaying allocation (UMTS) 546 displaying on transmitter (TD-SCDMA) 898 displaying on transmitter (UMTS) 546 grouping transmitters by (TD-SCDMA) 898 grouping transmitters by (UMTS) 547 histogram (TD-SCDMA) 899 histogram (UMTS) 547 interference zone coverage prediction (TD-SCDMA) 899 interference zone coverage prediction (UMTS) 548 manually allocating (TD-SCDMA) 896 manually allocating (UMTS) 545 using Search Tool with (TD-SCDMA) 897 using Search Tool with (UMTS) 546 scrambling codes (TD-SCDMA) 892 scrambling codes (UMTS) 541 Search Tool using to display channel reuse (GSM) 341 using to display frequencies (LTE) 1237 using to display frequencies (WiMAX) 1035 using to display physical cell IDs (LTE) 1241 using to display PN offsets (CDMA) 743 using to display preamble indexes (WiMAX) 1039 using to display scrambling codes (TD-SCDMA) 897 using to display scrambling codes (UMTS) 546 Search toolbar 88 searching for map objects 85 secondary antenna, assigning (CDMA) 671 secondary antenna, assigning (GSM) 195 secondary antenna, assigning (LTE) 1176 secondary antenna, assigning (TD-SCDMA) 816 secondary antenna, assigning (UMTS) 470 secondary antenna, assigning (WiMAX) 972 Sector-to-Sector Interference Tool using to study interference (GSM) 337 separation matrix, see "separation rules" service activating soft handover (UMTS) 512 creating (CDMA) 711 creating (LTE) 1210 creating (TD-SCDMA) 859 creating (UMTS) 511 creating (WiMAX) 1007 definition (CDMA) 746 definition (LTE) 1244 definition (TD-SCDMA) 905 definition (UMTS) 550 definition (WiMAX) 1042 displaying traffic distribution by (CDMA) 761 displaying traffic distribution by (LTE) 1261 displaying traffic distribution by (TD-SCDMA) 919 displaying traffic distribution by (UMTS) 566 displaying traffic distribution by (WiMAX) 1058 HSDPA, enabling 511, 859 HSUPA, enabling 511, 859 modifying (CDMA) 711 modifying (LTE) 1210 modifying (TD-SCDMA) 859 modifying (UMTS) 511
Forsk 2010

modifying (WiMAX) 1007 parameters used in predictions (CDMA) 711 parameters used in predictions (LTE) 1210 parameters used in predictions (TD-SCDMA) 859 parameters used in predictions (UMTS) 511 parameters used in predictions (WiMAX) 1007 setting priority (TD-SCDMA) 860 setting priority (UMTS) 512 service area (C/I) coverage prediction (TD-SCDMA) 867 service area (Eb/Nt) coverage prediction (TD-SCDMA) 867 service area (Eb/Nt) downlink based on test mobile data path (UMTS) 630, 778 service area (Eb/Nt) downlink or uplink coverage prediction (CDMA) 717 service area (Eb/Nt) downlink or uplink coverage prediction (UMTS) 516 service area (Eb/Nt) MBMS coverage prediction (TD-SCDMA)
871

service area (Eb/Nt) MBMS coverage prediction (UMTS) 518 service area (Eb/Nt) uplink based on test mobile data path (UMTS) 630, 778 services creating (GSM) 418 definition (GSM) 254 modelling (GSM) 418 modifying (GSM) 418 services table displaying (GSM) 419 shadowing 181, 187 point analysis, calculating in 182 shadowing (CDMA) 799, 804 shadowing (GSM) 422 shadowing (LTE) 1350 shadowing (TD-SCDMA) 963 shadowing (UMTS) 653, 661 shadowing (WiMAX) 1154 shadowing margin ACP 348, 581, 1070, 1271 clutter class, displaying per (CDMA) 804 clutter class, displaying per (GSM) 423 clutter class, displaying per (LTE) 1351 clutter class, displaying per (TD-SCDMA) 963 clutter class, displaying per (UMTS) 661 clutter class, displaying per (WiMAX) 1155 signal level coverage single station (CDMA) 689 single station (GSM) 216 single station (TD-SCDMA) 835 single station (UMTS) 490 signal level coverage prediction single station (LTE) 1189 single station (WiMAX) 986 signal level coverage prediction (CDMA) 697 signal level coverage prediction (GSM) 225 signal level coverage prediction (LTE) 1197 signal level coverage prediction (TD-SCDMA) 844, 848 signal level coverage prediction (UMTS) 498 signal level coverage prediction (WiMAX) 994

Unauthorized reproduction or distribution of this document is prohibited

1381

Atoll User Manual

simulation active set per user, displaying (CDMA) 762 adding to a group (CDMA) 769 adding to a group (TD-SCDMA) 926, 927 adding to a group (UMTS) 576 average results of group (CDMA) 767 average results of group (LTE) 1266 average results of group (TD-SCDMA) 924 average results of group (UMTS) 572 average results of group (WiMAX) 1065 cell load values, updating (LTE) 1268 cell load values, updating (WiMAX) 1067 coverage predictions, using results for (CDMA) 772 creating (CDMA) 758 creating (LTE) 1258 creating (TD-SCDMA) 917 creating (UMTS) 563 creating (WiMAX) 1056 displaying active set per user (UMTS) 566 displaying results with tooltips (LTE) 1262 displaying results with tooltips (WiMAX) 1061 duplicating (CDMA) 769, 770 duplicating (TD-SCDMA) 927, 928 duplicating (UMTS) 576, 577 estimating a traffic increase (LTE) 1269 estimating a traffic increase (TD-SCDMA) 928 estimating a traffic increase (UMTS) 577 estimating a traffic increase (WiMAX) 1068 generator initialisation number (CDMA) 769, 770 generator initialisation number (TD-SCDMA) 926, 928 generator initialisation number (UMTS) 576, 577 global scaling factor (CDMA) 771 global scaling factor (LTE) 1269 global scaling factor (TD-SCDMA) 928 global scaling factor (UMTS) 577 global scaling factor (WiMAX) 1068 maximum number of EV-DO channel elements per carrier (CDMA) 762 number of EV-DO channel elements (CDMA) 763 number of EV-DO channel elements due to SHO overhead (CDMA) 763 power control algorithm (CDMA) 756 power control algorithm (TD-SCDMA) 914 power control algorithm (UMTS) 559 rejected users due to EV-DO resources saturation (CDMA)
764, 768

replaying (CDMA) 770 replaying (TD-SCDMA) 926, 927 replaying (UMTS) 576 results of single (CDMA) 762 results of single (LTE) 1263 results of single (TD-SCDMA) 920 results of single (UMTS) 567 results of single (WiMAX) 1061 traffic increase, estimating (CDMA) 771 traffic simulation algorithm (LTE) 1257 traffic simulation algorithm (WiMAX) 1055 updating cell values with results (CDMA) 768

updating cell values with results (TD-SCDMA) 926 updating cell values with results (UMTS) 575 using results for coverage predictions (LTE) 1269 using results for coverage predictions (TD-SCDMA) 928 using results for coverage predictions (UMTS) 578 using results for coverage predictions (WiMAX) 1068 simulation results EV-DO cells (CDMA) 764 EV-DO mobiles (CDMA) 765 EV-DO, cells average and standard deviation (CDMA) 768 RTT cells (CDMA) 763 RTT mobiles (CDMA) 764 RTT, average and standard deviation cells (CDMA) 767 site creating (CDMA) 673 creating (GSM) 201 creating (LTE) 1178 creating (TD-SCDMA) 819 creating (UMTS) 473 creating (WiMAX) 975 definition (CDMA) 667 definition (GSM) 192 definition (LTE) 1172 definition (TD-SCDMA) 812 definition (UMTS) 466 definition (WiMAX) 968 modifying (CDMA) 673 modifying (GSM) 201 modifying (LTE) 1178 modifying (TD-SCDMA) 819 modifying (UMTS) 473 modifying (WiMAX) 975 moving on the map 31 moving to a higher location 31 parameters (CDMA) 668 parameters (GSM) 193 parameters (LTE) 1173 parameters (TD-SCDMA) 813 parameters (UMTS) 467 parameters (WiMAX) 969 properties, accessing from the Explorer window 30 properties, accessing from the map 30 site equipment creating (CDMA) 801 creating (TD-SCDMA) 961 creating (UMTS) 656 defining channel element consumption per R99 radio bearer (UMTS) 657 defining channel element consumption per terminal (CDMA) 802 defining Iub backhaul throughput 657 max EV-DO channel elements per carrier (CDMA) 669 site list 79 adding 80, 81 adding site 80 creating 80 editing 81 filter, using as 81
Forsk 2010

1382

Unauthorized reproduction or distribution of this document is prohibited

Index

slave carrier (TD-SCDMA) 879 slow fading, see "shadowing" smart antenna assigning (WiMAX) 972 creating (WiMAX) 1152 smart antennas adaptive beam modelling (TD-SCDMA) 958 conventional beamformer modelling (TD-SCDMA) 957 conventional beamformer modelling (WiMAX) 1151 creating grid of beams (GOB) (TD-SCDMA) 956 equipment (TD-SCDMA) 958 grid of beams (GOB) import format (TD-SCDMA) 957 grid of beams (GOB) modelling (TD-SCDMA) 955 importing grid of beams (GOB) (TD-SCDMA) 956 modelling (TD-SCDMA) 955 optimum beamformer modelling (TD-SCDMA) 957 optimum beamformer modelling (WiMAX) 1151 statistical modelling (TD-SCDMA) 957 third-party modelling (TD-SCDMA) 958 snapshot, definition (CDMA) 746 snapshot, definition (LTE) 1243 snapshot, definition (TD-SCDMA) 900 snapshot, definition (UMTS) 549 snapshot, definition (WiMAX) 1041 SOFDMA, definition (LTE) 1171 SOFDMA, definition (WiMAX) 967 soft handoff modelling on the uplink (CDMA) 799 soft handover activating per service (UMTS) 512 modelling on the downlink (UMTS) 573 modelling on the uplink (UMTS) 512, 573, 653 sorting sorting tables by one column 73 sorting tables by several columns 73 with subfolders 83 SPM Parameters tab window 158, 159 standalone carrier (TD-SCDMA) 879 Standard Propagation Model 154, 158, 159 calculating diffraction 155 correction factor for hilly regions 159 defining parameters 157 recommendations 154 sample values for constants 156 typical values for losses per clutter class 157 Standard toolbar 86 station duplicating (CDMA) 680 station template copying properties from another template (CDMA) 679 copying properties from another template (GSM) 206 copying properties from another template (LTE) 1184 copying properties from another template (TD-SCDMA)
825

copying properties from another template (UMTS) 480 copying properties from another template (WiMAX) 980 creating (CDMA) 676 creating (GSM) 204
Forsk 2010

creating (LTE) 1181 creating (TD-SCDMA) 822 creating (UMTS) 476 creating (WiMAX) 977 creating base station (CDMA) 674 creating base station (LTE) 1180 creating base station (TD-SCDMA) 820 creating base station (UMTS) 475 creating base station (WiMAX) 976 creating base station from (GSM) 203 deleting (CDMA) 680 deleting (GSM) 207 deleting (LTE) 1184 deleting (TD-SCDMA) 826 deleting (UMTS) 481 deleting (WiMAX) 981 modifying (CDMA) 676 modifying (GSM) 204 modifying (LTE) 1181 modifying (TD-SCDMA) 822 modifying (UMTS) 476 modifying (WiMAX) 977 modifying a field (CDMA) 679 modifying a field (GSM) 207 modifying a field (LTE) 1184 modifying a field (TD-SCDMA) 825 modifying a field (UMTS) 480 modifying a field (WiMAX) 980 multi-band, creating (GSM) 416 statistical smart antenna model (TD-SCDMA) 957 statistics, viewing coverage prediction (CDMA) 705 statistics, viewing coverage prediction (GSM) 236 statistics, viewing coverage prediction (LTE) 1204 statistics, viewing coverage prediction (TD-SCDMA) 854 statistics, viewing coverage prediction (UMTS) 505 statistics, viewing coverage prediction (WiMAX) 1001 study, see "coverage prediction" subcell definition (GSM) 196 modifying (GSM) 202 parameters (GSM) 196 subfolders creating 83 subscriber database (LTE) 1253 subscriber database (WiMAX) 1051 subscriber list adding subscribers with the mouse (LTE) 1255 adding subscribers with the mouse (WiMAX) 1053 calculations (LTE) 1256 calculations (WiMAX) 1054 creating (LTE) 1253 creating (WiMAX) 1051 importing (LTE) 1255 importing (WiMAX) 1053 symmetric neighbours, displaying (CDMA) 732 symmetric neighbours, displaying (GSM) 245 symmetric neighbours, displaying (LTE) 1229 symmetric neighbours, displaying (TD-SCDMA) 885

Unauthorized reproduction or distribution of this document is prohibited

1383

Atoll User Manual

symmetric neighbours, displaying (UMTS) 534 symmetric neighbours, displaying (WiMAX) 1026

T
T_Drop, defining per cell (CDMA) 671 table columns formatting 57 tables, see "data tables" TDD frame configuration (LTE) 1177 TD-SCDMA template 94 template coverage prediction, using as 186 templates 93 CDMA2000 1xRTT 1xEV-DO 94 GSM/GPRS/EGPRS 93 LTE 94 TD-SCDMA 94 UMTS HSDPA HSUPA 94 WiMAX 94 terminal creating (CDMA) 715 creating (GSM) 419 creating (LTE) 1211 creating (TD-SCDMA) 862 creating (UMTS) 513 creating (WiMAX) 1008 defining EV-DO Rev. 0-specific options (CDMA) 716 defining EV-DO Rev. A-specific options (CDMA) 716 definition (CDMA) 746 definition (GSM) 254 definition (LTE) 1244 definition (TD-SCDMA) 905 definition (UMTS) 550 definition (WiMAX) 1042 HSDPA, enabling 513, 862 HSUPA, terminal 513, 862 modelling (GSM) 419 modifying (CDMA) 715 modifying (GSM) 419 modifying (LTE) 1211 modifying (TD-SCDMA) 862 modifying (UMTS) 513 modifying (WiMAX) 1008 parameters used in predictions (CDMA) 714 parameters used in predictions (LTE) 1211 parameters used in predictions (TD-SCDMA) 861 parameters used in predictions (UMTS) 513 parameters used in predictions (WiMAX) 1008 terminals table displaying (GSM) 420 Test Mobile Data Analysis Tool printing 68 Test Mobile Data path exporting (LTE) 1322 test mobile data path analysing variations 632, 935 analysing variations (CDMA) 779

analysing variations (GSM) 396 analysing variations (LTE) 1321 analysing variations (WiMAX) 1120 coverage by C/I, using for (GSM) 394 coverage by signal level, using for (GSM) 394 coverage prediction, using in (GSM) 394 exporting (CDMA) 781 exporting (GSM) 398 exporting (TD-SCDMA) 936 exporting (UMTS) 633 exporting (WiMAX) 1122 exporting to CW measurements (CDMA) 781 exporting to CW measurements (GSM) 398, 399 exporting to CW measurements (LTE) 1322 exporting to CW measurements (TD-SCDMA) 936 exporting to CW measurements (UMTS) 633 exporting to CW measurements (WiMAX) 1122 extracting a field for a transmitter (GSM) 396 extracting a field for a transmitter (LTE) 1320 extracting a field for a transmitter (TD-SCDMA) 934 extracting a field for a transmitter (UMTS) 631 extracting a field for a transmitter (WiMAX) 779, 1120 filtering out points (CDMA) 776 filtering out points (GSM) 392 filtering out points (LTE) 1318 filtering out points (TD-SCDMA) 932 filtering out points (UMTS) 628 filtering out points (WiMAX) 1117 importing (CDMA) 773 importing (GSM) 389 importing (LTE) 1315 importing (TD-SCDMA) 929 importing (UMTS) 625 importing (WiMAX) 1114 Refresh Geo Data (GSM) 394 Refresh Geo Data (LTE) 1319 Refresh Geo Data (TD-SCDMA) 934 Refresh Geo Data (UMTS) 630 Refresh Geo Data (WiMAX) 1119 using for pilot reception analysis (Ec/I0) (UMTS) 630, 778 using for preamble analysis (WiMAX) 1119 using for service area (Eb/Nt) downlink (UMTS) 630, 778 using for service area (Eb/Nt) uplink (UMTS) 630, 778 using in coverage prediction (LTE) 1320 using in coverage prediction (UMTS) 630, 777 using in coverage prediction (WiMAX) 1119 Test Mobile Data window exporting (CDMA) 782 exporting (GSM) 399 exporting (LTE) 1323 exporting (TD-SCDMA) 937 exporting (UMTS) 634 exporting (WiMAX) 1122 printing (CDMA) 782 printing (GSM) 399 printing (LTE) 1323 printing (TD-SCDMA) 937 printing (UMTS) 634
Forsk 2010

1384

Unauthorized reproduction or distribution of this document is prohibited

Index

printing (WiMAX) 1122 third-party smart antenna modelling (TD-SCDMA) 958 throughput displaying traffic distribution by (LTE) 1261 displaying traffic distribution by (WiMAX) 1059 for all subscribers of a list (LTE) 1353 for all subscribers of a list (WiMAX) 1157 throughput coverage prediction (LTE) 1218 throughput coverage prediction (WiMAX) 1016 tilt angle 3-D antenna pattern 145 timeslot configurations creating (GSM) 414 modifying (GSM) 414 tip text 36 TMA defining 147 TMA, assigning (LTE) 1175 TMA, assigning (TD-SCDMA) 814 TMA, assigning (WiMAX) 971 TMS, assigning (CDMA) 670 TMS, assigning (GSM) 195 TMS, assigning (UMTS) 469 tool tips, see "tip text" toolbar icons 86 Map 87 Radio 87 Search 88 Standard 86 Vector Edition 88 tooltips comparing coverage predictions, co-planning (CDMA) 786 comparing coverage predictions, co-planning (LTE) 1327 comparing coverage predictions, co-planning (TD-SCDMA) 941 comparing coverage predictions, co-planning (UMTS) 638 comparing coverage predictions, co-planning (WiMAX)
1126

coverage prediction results, displaying (GSM) 233 displaying coverage prediction results (CDMA) 702 displaying coverage prediction results (LTE) 1201 displaying coverage prediction results (TD-SCDMA) 851 displaying coverage prediction results (UMTS) 502 displaying coverage prediction results (WiMAX) 998 displaying simulation results with (LTE) 1262 displaying simulation results with (WiMAX) 1061 total losses, updating 148 total noise on downlink, see "downlink total noise" total power reconfiguration with ACP 1270 total transmitted power on DL (CDMA) 673 traffic defining for ACP optimisation 359, 593, 1082, 1283 traffic capture global scaling factor (GSM) 265 traffic increase, estimating a (GSM) 265 traffic channel coverage prediction (TD-SCDMA) 865
Forsk 2010

traffic distribution creating, see "simulation" displaying by activity status (LTE) 1260 displaying by activity status (WiMAX) 1058 displaying by connection status (CDMA) 761 displaying by connection status (LTE) 1260 displaying by connection status (TD-SCDMA) 919 displaying by connection status (UMTS) 565 displaying by connection status (WiMAX) 1058 displaying by handoff status (CDMA) 760 displaying by handover status (TD-SCDMA) 918 displaying by handover status (UMTS) 565 displaying by number of used subchannels in uplink (WiMAX) 1060 displaying by service (CDMA) 761 displaying by service (LTE) 1261 displaying by service (TD-SCDMA) 919 displaying by service (UMTS) 566 displaying by service (WiMAX) 1058 displaying by throughput (LTE) 1261 displaying by throughput (WiMAX) 1059 displaying by uplink transmission power (LTE) 1262 displaying by uplink transmission power (WiMAX) 1060 traffic increase, estimating (CDMA) 771 traffic increase, estimating (GSM) 265 traffic increase, estimating (LTE) 1269 traffic increase, estimating (TD-SCDMA) 928 traffic increase, estimating (UMTS) 577 traffic increase, estimating (WiMAX) 1068 traffic load, setting (LTE) 1214 traffic load, setting (WiMAX) 1011 traffic map converting 2G (LTE) 1252 cumulated traffic, exporting (GSM) 261 cumulated traffic, exporting (LTE) 1252 cumulated traffic, exporting (WiMAX) 1050 data sources (CDMA) 747 data sources (GSM) 254 data sources (LTE) 1244 data sources (TD-SCDMA) 905 data sources (UMTS) 550 data sources (WiMAX) 1042 exporting cumulated traffic (CDMA) 755 exporting cumulated traffic (TD-SCDMA) 913 exporting cumulated traffic (UMTS) 558 importing traffic map based on user profile densities (CDMA) 750 importing traffic map based on user profile densities (GSM)
257

importing traffic map based on user profile densities (LTE)

1247

importing traffic map based on user profile densities (TD-SCDMA) 909 importing traffic map based on user profile densities (UMTS) 553 importing traffic map based on user profile densities (WiMAX) 1045 importing user density traffic map (WIMAX) 1048 live data, creating from (CDMA) 747

Unauthorized reproduction or distribution of this document is prohibited

1385

Atoll User Manual

live data, creating from (GSM) 254 live data, creating from (LTE) 1244 live data, creating from (TD-SCDMA) 906 live data, creating from (UMTS) 550 live data, creating from (WiMAX) 1042 marketing-based (CDMA) 748 marketing-based (LTE) 1245 marketing-based (TD-SCDMA) 907 marketing-based (WiMAX) 1043 sector (CDMA) 747 sector (GSM) 254 sector (LTE) 1244 sector (TD-SCDMA) 906 sector (UMTS) 550 sector (WiMAX) 1042 statistics on user profile environment based traffic map (CDMA) 752 statistics on user profile environment based traffic map (GSM) 259 statistics on user profile environment based traffic map (LTE) 1249 statistics on user profile environment based traffic map (TD-SCDMA) 911 statistics on user profile environment based traffic map (UMTS) 555 statistics on user profile environment based traffic map (WiMAX) 1047 user density (CDMA) 753 user density (GSM) 260 user density (LTE) 1250 user density (TD-SCDMA) 911 user density (UMTS) 556 user density (WiMAX) 1048 user density traffic map, importing (CDMA) 753 user density traffic map, importing (GSM) 260 user density traffic map, importing (LTE) 1250 user density traffic map, importing (TD-SCDMA) 911 user density traffic map, importing (UMTS) 556 user density, creating (CDMA) 754 user density, creating (GSM) 260 user density, creating (LTE) 1251 user density, creating (TD-SCDMA) 912 user density, creating (UMTS) 557 user density, creating (WiMAX) 1049 user density, creating from sector traffic maps (CDMA) 754 user density, creating from sector traffic maps (GSM) 261 user density, creating from sector traffic maps (LTE) 1251 user density, creating from sector traffic maps (TD-SCDMA) 913 user density, creating from sector traffic maps (UMTS) 557 user density, creating from sector traffic maps (WiMAX)
1049

user profile environment based, creating (WiMAX) 1047 user profile environment based, importing (CDMA) 751 user profile environment based, importing (GSM) 258 user profile environment based, importing (LTE) 1248 user profile environment based, importing (TD-SCDMA)
910

user profile environment based, importing (UMTS) 554 user profile environment based, importing (WiMAX) 1046 traffic maps ACP, using with (GSM) 348 ACP, using with (LTE) 1271 ACP, using with (UMTS) 580 ACP, using with (WiMAX) 1069 converting 2G (CDMA) 755 converting 2G (GSM) 261 converting 2G (TD-SCDMA) 913 converting 2G (UMTS) 558 converting 2G (WiMAX) 1050 traffic quality studies, see "quality studies" traffic simulation algorithm (LTE) 1257 traffic simulation algorithm (WiMAX) 1055 transmission power (GSM) reconfiguration with ACP 347 transmitter calculating network capacity (TD-SCDMA) 901 coverage prediction by transmitter (CDMA) 699 coverage prediction by transmitter (GSM) 227, 228, 229,
230, 231

user profile (GSM) 256 user profile (UMTS) 551 user profile environment based, creating (CDMA) 752 user profile environment based, creating (GSM) 259 user profile environment based, creating (LTE) 1249 user profile environment based, creating (TD-SCDMA) 910 user profile environment based, creating (UMTS) 555

coverage prediction by transmitter (LTE) 1198 coverage prediction by transmitter (TD-SCDMA) 845 coverage prediction by transmitter (UMTS) 499 coverage prediction by transmitter (WiMAX) 995 creating (CDMA) 673 creating (GSM) 201 creating (LTE) 1179 creating (TD-SCDMA) 820 creating (UMTS) 474 creating (WiMAX) 975 definition (CDMA) 667, 669 definition (GSM) 192, 193 definition (LTE) 1172 definition (TD-SCDMA) 812, 813 definition (UMTS) 466, 468 definition (WiMAX) 968 displaying frequencies (LTE) 1238 displaying frequencies (WiMAX) 1036 displaying physical cell IDs (LTE) 1242 displaying preamble indexes (WiMAX) 1040 displaying scrambling codes (TD-SCDMA) 898 displaying scrambling codes (UMTS) 546 extracting a field from a test mobile data path (GSM) 396 extracting a field from a test mobile data path (LTE) 1320 extracting a field from a test mobile data path (TD-SCDMA)
934

extracting a field from a test mobile data path (UMTS) 631 extracting a field from a test mobile data path (WiMAX) 779,
1120

frequency allocation, displaying (GSM) 342

1386

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Index

global parameters (CDMA) 799 global parameters (LTE) 1342 global parameters (TD-SCDMA) 953 global parameters (UMTS) 653 global parameters (WiMAX) 1140 global properties, modifying (CDMA) 799 grouping by frequencies (GSM) 343 grouping by frequencies (LTE) 1238 grouping by frequencies (WiMAX) 1036 grouping by physical cell IDs (LTE) 1242 grouping by preamble indexes (WiMAX) 1040 grouping by scrambling codes (TD-SCDMA) 898 grouping by scrambling codes (UMTS) 547 modifying (CDMA) 673 modifying (GSM) 201 modifying (LTE) 1179 modifying (TD-SCDMA) 820 modifying (UMTS) 474 modifying (WiMAX) 975 modifying global parameters (TD-SCDMA) 955 modifying global properties (LTE) 1343 modifying global properties (UMTS) 654 modifying global properties (WiMAX) 1142 network capacity dimensioning (TD-SCDMA) 902 PN offsets, displaying (CDMA) 744 PN offsets, grouping by (CDMA) 744 setting as active (CDMA) 696 setting as active (GSM) 224 setting as active (LTE) 1196 setting as active (TD-SCDMA) 842 setting as active (UMTS) 497 setting as active (WiMAX) 993 transmitter list 79 adding 80, 81 adding transmitter 80 creating 80 editing 81 editing filter 81 transmitters automatic display type 34 transparency, changing 35 TRX creating (GSM) 203 modifying (GSM) 203 TRX equipment creating (GSM) 408 importing (GSM) 408 TRX equipment (GSM) 407 TRX types (GSM) 404

U
UL load factor (CDMA) 673 UMTS HSDPA HSUPA template 94 undo 84 Universal Transverse Mercator projection 96 uplink load factor, setting (TD-SCDMA) 859 uplink load factor, setting (UMTS) 510
Forsk 2010

uplink noise rise, setting (LTE) 1214 uplink noise rise, setting (WiMAX) 1011 uplink power control displaying traffic distribution by (LTE) 1262 displaying traffic distribution by (WiMAX) 1060 uplink subchannelisation displaying traffic distribution by (WiMAX) 1060 uplink traffic channel coverage prediction (TD-SCDMA) 865 UpPCH interference coverage prediction (TD-SCDMA) 874 user configuration 78 ACP 352, 585, 1074, 1275, 1276 coverage prediction, exporting 187 creating 79 exporting 79 importing 79 user densities using instead of user profiles (LTE) 1354 using instead of user profiles (WiMAX) 1158 user density traffic map creating (CDMA) 754 creating (GSM) 260 creating (TD-SCDMA) 912 creating (UMTS) 557 creating (WiMAX) 1049 creating from sector traffic maps (CDMA) 754 creating from sector traffic maps (GSM) 261 creating from sector traffic maps (LTE) 1251 creating from sector traffic maps (TD-SCDMA) 913 creating from sector traffic maps (UMTS) 557 creating from sector traffic maps (WiMAX) 1049 user distribution (CDMA) 756 user distribution (TD-SCDMA) 914 user distribution (UMTS) 559 user equipment category, HSDPA 514, 515, 862 user equipment category, HSDPA, editing 659, 963 user equipment category, HSUPA, editing 659 user profile creating (CDMA) 749 creating (GSM) 256 creating (LTE) 1246 creating (TD-SCDMA) 907 creating (UMTS) 552 creating (WiMAX) 1044 modifying (CDMA) 749 modifying (GSM) 256 modifying (LTE) 1246 modifying (TD-SCDMA) 907 modifying (UMTS) 552 modifying (WiMAX) 1044 user profile densities importing traffic map based on (CDMA) 750 importing traffic map based on (GSM) 257 importing traffic map based on (LTE) 1247 importing traffic map based on (TD-SCDMA) 909 importing traffic map based on (UMTS) 553 importing traffic map based on (WiMAX) 1045 user profile environment based traffic map creating (CDMA) 752

Unauthorized reproduction or distribution of this document is prohibited

1387

Atoll User Manual

creating (GSM) 259 creating (LTE) 1249 creating (TD-SCDMA) 910 creating (UMTS) 555 creating (WiMAX) 1047 importing (CDMA) 751 importing (GSM) 258 importing (LTE) 1248 importing (TD-SCDMA) 910 importing (UMTS) 554 importing (WiMAX) 1046 statistics on (CDMA) 752 statistics on (GSM) 259 statistics on (LTE) 1249 statistics on (TD-SCDMA) 911 statistics on (UMTS) 555 statistics on (WiMAX) 1047 user profiles user densities, replacing with (LTE) 1354 user densities, replacing with (WiMAX) 1158

simulations (CDMA) 759 WiMAX 967 cyclic prefix ratio 1140 frame duration 1140 glossary 1166 template 94 WiMAX radio bearer defining 1145 definition 1041 WiMAX schedulers defining 1150 scheduling methods 1148 WiMAX, definition 967 windows cascading 26 docking 26 floating 26 wireless local loop propagation model 165 WLL (Wireless Local Loop) propagation model 165

X
XML exporting data tables to 64 importing data tables from 64

V
Vector Edition toolbar 88 Vienna 93 model 162, 164 visibility scale 35

Z
zooming choosing a scale 39 in on a specific area 39

W
Walsh codes orthogonality factor, default (CDMA) 799

1388

Unauthorized reproduction or distribution of this document is prohibited

Forsk 2010

Atoll User Manual

Forsk 2010

Unauthorized reproduction or distribution of this document is prohibited

1389

User Manual

version 2.8.2
AT282_UM_E0 March 2010

Head Office
7, rue des Briquetiers 31700 Blagnac - France Tel: +33 562 747 210 Fax: +33 562 747 211

US Office
200 South Wacker Drive - Suite 3100 Chicago, IL 60606 - USA Tel: +1 312 674 4846 Fax: +1 312 674 4847

China Office
Suite 302, 3/F, West Tower, Jiadu Commercial Building, No. 66 Jianzhong Road, Tianhe Hi-Tech Industrial Zone, Guangzhou, 510665, P. R. of China Tel: +86 20 8553 8938 Fax: +86 20 8553 8285

www.forsk.com