Escolar Documentos
Profissional Documentos
Cultura Documentos
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.
Forsk 2010
Forsk 2010
Table of Contents
Table of Contents
1
1.1
1.1.1 1.1.2
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
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
Forsk 2010
Table of Contents
1.8.7
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
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
3.4 3.5
3.5.1 3.5.2 3.5.3 3.5.4 3.5.5
3.6 3.7
3.7.1 3.7.2 3.7.3
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
3.12 3.13
3.13.1 3.13.2
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
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
Forsk 2010
Table of Contents
5.1.13
5.2
5.2.1 5.2.2 5.2.3 5.2.4 5.2.5
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
Forsk 2010
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
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
11
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
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
13
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
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
15
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
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
16
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
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
18
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
19
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
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
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
21
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
22
Forsk 2010
Chapter 1
The Working Environment
Atoll
1.1
Forsk 2010
25
Toolbar
1.1.1
1.1.2
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
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
1.2.1
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
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
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
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
28
Forsk 2010
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
1.3.1
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
29
1.3.1.3
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.
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
30
Forsk 2010
1.3.2.1
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
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
1.3.2.4
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
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
32
Forsk 2010
1.3.3.1
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
Forsk 2010
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.
34
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.
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
35
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.
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.
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
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
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.
Forsk 2010
37
Figure 1.10: Shading from -60 dBm to -105 dBm To change how the results of a signal level study are displayed:
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
1.4.1
1.4.1.1
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
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
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
).
Once you have returned to a previous zoom level, click the Next Zoom button ( level (or press ALT +
).
1.4.2
2. Move the pointer over the map and drag the map in the desired direction.
1.4.3
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
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
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
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
40
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
1.4.8
1.4.8.1
1.4.8.1.1
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
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
1.4.8.2.1
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
Forsk 2010
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
1.4.8.3.1
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
43
1.4.8.4
1.4.8.4.1
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.
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.
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
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.
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
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
Forsk 2010
45
1.4.8.6
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
46
Forsk 2010
1.4.9.1
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
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
Forsk 2010
47
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
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
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
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
Forsk 2010
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
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
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
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
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
Forsk 2010
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
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
Appearance
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.
52
Forsk 2010
Appearance
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
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
Forsk 2010
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
1.5.2
1.5.2.1
1.5.2.2
54
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.
1.5.2.3
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
Forsk 2010
55
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.
1.5.4
1.5.5
56
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
4. Click OK.
4. Click OK.
Forsk 2010
57
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.
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.
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
Forsk 2010
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).
Note:
1.5.6
1.5.6.1
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
Forsk 2010
59
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).
60
Forsk 2010
1.5.7
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
Forsk 2010
61
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
Forsk 2010
1.5.9
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
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
1.5.11
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
64
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).
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
Forsk 2010
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
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
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
67
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
1.6.4
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
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
Forsk 2010
1.7
1.7.1
For examples of grouping data objects, see "Examples of Grouping" on page 71.
1.7.1.1
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
Forsk 2010
69
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
Forsk 2010
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
71
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.
72
Forsk 2010
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
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
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.
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
74
Forsk 2010
1.7.3.2
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
Forsk 2010
75
Formula
>X <=X >=X *X* *X 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
1.7.3.4
1.7.3.4.1
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
Forsk 2010
1.7.3.4.2
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
The result of this advanced filter can be seen in the second pane of Figure 1.39.
Forsk 2010
77
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
Forsk 2010
1.7.4.1
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
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
Forsk 2010
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
1.7.5.2
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.
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.
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
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
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.
1.7.5.4
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
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
6. Select the check box of the list or lists that you want to display.
Forsk 2010
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
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
1.7.6.3
82
Forsk 2010
1.7.6.4
1.7.6.5
1.7.6.6
1.7.7
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
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
For more information on creating and editing a filtering zone, see "Using a Filtering Zone" on page 41.
1.8
1.8.1
To redo an action that you have undone: Select Edit > Redo.
84
Forsk 2010
1.8.2
1.8.3
1.8.3.1
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
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
Note:
1.8.4
X-Y coordinates
Clutter class
1.8.5
1.8.6
86
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
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
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
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 )
: 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 ) )
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
89
90
Forsk 2010
Chapter 2
Starting an Atoll Project
Atoll
92
Forsk 2010
2.1
Once the necessary data have been assembled, you can create the Atoll document.
2.2
2.2.1
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
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
94
Forsk 2010
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.
2.2.1.3
Forsk 2010
95
2.2.1.3.1
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
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
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
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
3. Click OK.
2.2.2
Forsk 2010
97
2.2.2.1
Figure 2.50: Components of Multi-user Environments Note: For information on creating and maintaining the database, see the Administrator Manual.
98
Forsk 2010
2.2.2.2
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
2.2.2.2.2
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
Forsk 2010
99
2.2.2.3
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
Forsk 2010
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.
2.2.2.4
Forsk 2010
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
2.2.2.5.1
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
102
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
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
103
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
Forsk 2010
2.3
2.3.1
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
105
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
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
Forsk 2010
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
107
108
Forsk 2010
Chapter 3
Managing Geographic Data
Atoll
110
Forsk 2010
3.1
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
111
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.
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.
3.2
112
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
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
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.
3.3.2
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
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.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
Forsk 2010
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
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
116
Forsk 2010
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
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
117
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
118
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
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
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
119
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
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
120
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
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: -
Forsk 2010
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.
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
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
Forsk 2010
3.5.4
3.5.5
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
Forsk 2010
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
3.7.2
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
Forsk 2010
3.7.3
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
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
Forsk 2010
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.
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
3.9.2
126
Forsk 2010
3.10
3.10.1
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
127
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.
3.10.2
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
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
3.10.5
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
3.11.1
Forsk 2010
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.
3.11.2
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
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
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
Case 2 DTM
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
131
3.11.2.3
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
Figure 3.78: Multi-layer management in calculations two clutter maps representing the same area
3.12
Note:
Tool tips only appear when the Display Tips button ( selected.
3.13
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
Forsk 2010
3.13.1
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
3.14
Forsk 2010
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
3.14.1.1
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.
).
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
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
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
3.14.1.4
3.14.2
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:
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.
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
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
3.15.1.1
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.
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.
3.15.1.2
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
3.15.3
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
138
Forsk 2010
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
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
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
Forsk 2010
Chapter 4
Antennas and Equipment
Atoll
4.1
4.1.1
Creating an Antenna
Each Atoll project template has antennas specific to the technology supported by the template. As well, Atoll allows you to create antennas and set the parameters such as manufacturer, gain, horizontal pattern, and vertical pattern.
When you create a new antenna, you can copy the horizontal and vertical antenna patterns from a spreadsheet or word processor.
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.
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
143
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
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
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
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).
Forsk 2010
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
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
Forsk 2010
4.1.5
4.2
4.2.1
4.2.2
Forsk 2010
147
4.2.3
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
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)
Forsk 2010
149
150
Forsk 2010
Chapter 5
Managing Calculations in Atoll
Atoll
152
Forsk 2010
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
5.1.1
Model
Frequency Range
100 400 MHz
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
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
Terrain profile Terrain profile Deterministic clutter Terrain profile Statistical clutter (at the receiver)
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
Forsk 2010
153
Model
Standard Propagation Model
Frequency Range
Recommended Use
150 3500 MHz (Automatic calibration available) Erceg-Greenstein (SUI) Sakagami Extended (Automatic calibration available) 3000 8000 MHz 1900 6000 MHz
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
5.1.2
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
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
154
Forsk 2010
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
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
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
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
Its value is heavily influenced by the values given to losses per clutter class.
5.1.2.4
i=1
Li wi
156
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
5.1.2.6
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
157
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
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.
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
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
5.1.3.1
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
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
Forsk 2010
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
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
5.1.4.1
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
5.1.4.2
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
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
162
Forsk 2010
5.1.5.1
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
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
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
163
5.1.6
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
5.1.7.1
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
Forsk 2010
5.1.7.2
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
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
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
Forsk 2010
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
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
166
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
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
Forsk 2010
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
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
168
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
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
Forsk 2010
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
5.2.5
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
170
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
5.3.2
5.3.3
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
171
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
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
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
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.
5.3.6
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
Forsk 2010
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
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
Forsk 2010
5.3.6.3
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
175
5.3.6.4
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
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
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
177
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
Forsk 2010
5.3.7
Figure 5.95: Exporting path loss matrices 8. Click OK to export the path loss matrices.
5.4
In this section, the following are explained: "Making Point Predictions" on page 179 "Making Coverage Predictions" on page 182.
5.4.1
Forsk 2010
179
5.4.1.1
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
180
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
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
5.4.1.5
Forsk 2010
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
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
Forsk 2010
5.4.2.1
5.4.2.1.1
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
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
3. Right-click the coverage prediction you want to clone. The context menu appears.
Forsk 2010
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
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
184
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
5.4.2.3.2
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
Forsk 2010
185
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
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
5.4.2.4.1
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
Forsk 2010
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
5.4.2.5
5.4.2.6
Forsk 2010
187
188
Forsk 2010
Chapter 6
GSM/GPRS/EDGE Networks
Atoll
190
Forsk 2010
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
Traffic Maps
Dimensioning
User-defined values
5c
6a List of Frequencies 6
GSM/GPRS/EDGE Predictions 8
7a
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
Forsk 2010
191
Atoll User Manual "Studying Signal Level Coverage" on page 216 and "Signal Level Coverage Predictions" on page 225
4
).
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
).
).
"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
6.2.1
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
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
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.
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
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
195
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
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
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
Forsk 2010
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.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
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
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
6.2.1.2.1
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
c. Right-click the transmitter you want to modify. The context menu appears.
Forsk 2010
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
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
Forsk 2010
6.2.1.2.5
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
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.
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
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.
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
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
204
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
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
206
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
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
6.2.1.5
Forsk 2010
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.
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
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
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
6.2.4
6.2.5
Forsk 2010
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
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
210
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
6.2.6.4
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
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
6.2.7
212
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
2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Remote Antenna from the menu.
4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its 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
6.2.7.3
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
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
6.2.8
214
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
6.2.9.1
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.
6.2.9.2
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
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:
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
217
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
218
Forsk 2010
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
Forsk 2010
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.
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
Forsk 2010
6.2.10.2
Forsk 2010
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.
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.
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
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.
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
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
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
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
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
6.2.10.6.1
Forsk 2010
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).
226
Forsk 2010
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
Forsk 2010
227
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.
Forsk 2010
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.
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
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
231
6.2.10.6.3
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
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
6.2.10.7.1
6.2.10.7.2
6.2.10.7.3
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
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
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
Forsk 2010
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
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
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
236
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.
6.2.10.7.7
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.
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
Forsk 2010
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.
Forsk 2010
239
[ 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
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.
6.2.10.8
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
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
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
242
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
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
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
6.2.11.4.2
6.2.11.5
6.2.11.5.1
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
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
Forsk 2010
[ 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
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
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 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
Forsk 2010
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.
Forsk 2010
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
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
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
Forsk 2010
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
Forsk 2010
6.3
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
The table can be populated as any other table as explained in "Working with Data Tables" on page 53.
6.3.2
Forsk 2010
253
6.3.3
6.3.4
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
254
Forsk 2010
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
255
6.3.4.2
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
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
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
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 = = =
6.3.4.2.2
258
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
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
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
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
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
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
260
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
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
6.3.4.5
Forsk 2010
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
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
262
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
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
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
263
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
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
Forsk 2010
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
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
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
265
Atoll User Manual Rename: Select Rename to rename the current traffic capture.
6.3.7
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
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
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
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
267
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
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
269
6.4
6.4.1
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
Forsk 2010
6.4.2
6.4.2.1
6.4.2.1.1
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
Forsk 2010
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
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
272
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
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
Forsk 2010
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
6.4.3.1
274
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
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
Forsk 2010
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
6.4.3.4.1
276
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
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
6.4.3.4.4
Forsk 2010
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
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.
278
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.
6.4.4
Forsk 2010
279
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
280
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.
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
281
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
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
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
Forsk 2010
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
6.4.4.1.5
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.
284
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).
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.
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
Forsk 2010
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
Forsk 2010
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
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.
288
Forsk 2010
6.4.4.1.8
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.
6.4.4.1.9
3. Right-click the interference matrix you want to use in an automatic frequency allocation. The context menu appears.
Forsk 2010
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
6.4.4.2.1
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
6.4.4.2.3
290
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
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.
Forsk 2010
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
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
Tip:
Take a look your neighbour allocation before running the AFP. Often poorly defined neighbour relations cause poor defined frequency plan.
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
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.
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.
Forsk 2010
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.
294
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.
Forsk 2010
295
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
Forsk 2010
Figure 6.147: Setting the option for the optimisation of the numbers of TRXs
Figure 6.148: Selecting the default traffic capture results as the source of traffic
Forsk 2010
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).
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
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
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
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
299
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.
300
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
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
0 - 77 62
1 2 - 25 12
Forsk 2010
301
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
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
3. Select Frequency Plan > Automatic Allocation from the context menu. The AFP dialogue appears with the AFP Selection tab (see Figure 6.152).
302
Forsk 2010
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
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.
304
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.
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
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
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
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
6.4.5.6.1
6.4.5.6.2
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
Forsk 2010
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.
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
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
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
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.
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
311
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
312
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
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
314
Forsk 2010
6.4.5.8
Forsk 2010
315
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
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
6.5.1
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
317
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
Forsk 2010
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
319
6.5.2
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
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
Forsk 2010
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:
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:
Forsk 2010
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
Forsk 2010
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
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
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:
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
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
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
326
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
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
6.5.3.1
328
Forsk 2010
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
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
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
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
331
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
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
Forsk 2010
333
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
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
Forsk 2010
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.
336
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
Forsk 2010
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
338
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
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.
6.5.7
340
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
6.5.8.1
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
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.
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
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
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
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.
6.5.8.4
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.
Forsk 2010
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
344
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
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
346
Forsk 2010
6.6.1
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
6.6.1.1.1
6.6.1.1.2
6.6.1.1.3
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
347
6.6.1.2
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
6.6.1.4
6.6.1.4.1
348
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.)
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
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
Forsk 2010
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
6.6.2.1
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
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
Forsk 2010
351
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
352
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
6.6.3.1
Forsk 2010
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.
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.
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
6.6.3.2.1
354
Forsk 2010
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
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
Forsk 2010
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
Forsk 2010
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
Forsk 2010
359
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
360
Forsk 2010
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.
Forsk 2010
361
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
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.
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.
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
364
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.
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
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:
366
Forsk 2010
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.
Forsk 2010
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
368
Forsk 2010
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
369
Tip:
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.
370
Forsk 2010
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.
Forsk 2010
371
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
6.6.3.2.8
372
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
Forsk 2010
373
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
4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 6.208).
374
Forsk 2010
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
Forsk 2010
375
6.6.6.1
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
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
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
Forsk 2010
377
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.
378
Forsk 2010
6.6.6.1.3
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
379
6.6.6.1.4
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
Forsk 2010
6.6.6.1.5
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
381
6.6.6.1.6
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
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
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
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
383
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
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
Forsk 2010
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
Figure 6.224: Example of antenna type change (left) and electrical tilt change (right)
Forsk 2010
385
6.6.6.2.4
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.
386
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
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
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).
6.6.6.2.7
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
Depending on the type of optimisation results you want to view, you might need to expand additional folders.
388
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
6.7.1
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
389
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
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
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
391
6.7.3
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
392
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*
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
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
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
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
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
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
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
Forsk 2010
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
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
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
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
Forsk 2010
6.7.7
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
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
399
6.8.1
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
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.
400
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
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
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
401
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
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
Forsk 2010
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
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
403
[TMP] ExtraServZone = 1
Composite 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
404
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
The following table describes the parameters to be specified for each hopping mode.
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
Forsk 2010
Non hopping
x x x
BBH
x x x
SFH
x x x
The following table describes the parameters to be specified for each hopping mode.
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
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
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
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
408
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
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
Forsk 2010
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
6.8.5.5
410
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
6.8.6.1
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
411
6.8.6.2
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
Forsk 2010
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
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
6.8.6.5
Forsk 2010
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
414
Forsk 2010
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
6.8.8.1
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
6.8.8.2.1
This settings are taken into account in: Coverage predictions Traffic capture Dimensioning Interference matrices.
Forsk 2010
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
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
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
417
6.8.8.2.3
6.8.9
6.8.9.1
6.8.9.1.1
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
Forsk 2010
6.8.9.1.2
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
6.8.9.2.1
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
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
6.8.9.3.1
Forsk 2010
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
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
Forsk 2010
6.8.10
6.8.11
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
421
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
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
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
5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.
6.8.14
Forsk 2010
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
6.8.15.1
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
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
6.9.1
6.9.1.1
Forsk 2010
425
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
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
Forsk 2010
6.9.1.3
6.9.2
6.9.2.1
6.9.2.1.1
6.9.2.1.2
Case 1
Case 2
Forsk 2010
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
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
6.9.2.1.5
428
Forsk 2010
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
429
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
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
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
Forsk 2010
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
6.9.2.1.10
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
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
432
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
6.9.2.2.2
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
433
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
434
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
Forsk 2010
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
436
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
Forsk 2010
437
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
438
Forsk 2010
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
Forsk 2010
439
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
440
Forsk 2010
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.
Forsk 2010
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 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
Forsk 2010
6.9.2.3
6.9.2.3.1
6.9.2.3.2
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
Forsk 2010
443
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
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
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
6.9.3.1
Forsk 2010
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
6.9.3.1.2
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
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
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
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
6.9.3.1.5
Or, the AFP can use the traffic loads in order to calculate the demands. (In order to maintain compatibility with old documents).
Forsk 2010
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.
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
Forsk 2010
6.9.3.1.6
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
449
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
Forsk 2010
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
451
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:
The splitting point stays global, yet the number of TRXs is adapted.
452
Forsk 2010
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
6.9.3.2.1
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
453
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
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
Forsk 2010
6.9.3.2.2
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
455
Atoll User Manual This implementation is simple, compact, and sufficient for the most interference matrices.
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.
6.9.3.2.3
6.9.3.2.4
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
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
6.9.3.3.1
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
Forsk 2010
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
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
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.
6.9.3.3.5
458
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
6.9.3.4
6.9.3.4.1
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
Forsk 2010
459
460
Forsk 2010
6.9.3.4.4
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
Forsk 2010
461
462
Forsk 2010
Chapter 7
UMTS HSPA Networks
Atoll
7.1
Network Configuration - Add Network Elements - Change Parameters Basic Predictions (Best Server, Signal Level) Neighbour Allocation 4
Traffic Maps
5a
Monte-Carlo Simulations
5b 5
5c
UMTS/HSPA Predictions 7
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
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.2
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
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
7.2.1.1
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.
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
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
469
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
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
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
7.2.1.2.1
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
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
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
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
Forsk 2010
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
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.
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
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.
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
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
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
Forsk 2010
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
477
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
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
479
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
7.2.1.4.3
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
Forsk 2010
7.2.1.4.4
7.2.1.5
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.
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
Forsk 2010
481
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
7.2.4
482
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
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
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
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
7.2.6.3
7.2.6.4
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
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
Forsk 2010
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
7.2.7.1
2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Remote Antenna from the menu.
4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its 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
486
Forsk 2010
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
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
Forsk 2010
487
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
7.2.9
7.2.9.1
488
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
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
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
7.2.9.2
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
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:
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
491
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
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
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
493
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.
7.2.10.2
494
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.
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.
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
495
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
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
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
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
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
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
7.2.10.6.1
498
Forsk 2010
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).
7.2.10.6.2
Forsk 2010
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
500
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
Forsk 2010
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
7.2.10.7.2
7.2.10.7.3
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
Forsk 2010
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
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
503
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
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
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
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
505
7.2.10.7.7
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.
506
Forsk 2010
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
507
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.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
Forsk 2010
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.
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
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
7.2.10.8.2
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
Forsk 2010
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
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.
512
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.
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
513
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
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
7.2.10.8.4
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
515
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.
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
Forsk 2010
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.
Forsk 2010
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.
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
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.
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
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.
520
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.
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
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.
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
522
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
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
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
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 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
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
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
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
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
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
Forsk 2010
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
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
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
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
7.2.11.4.2
7.2.11.5
Forsk 2010
533
7.2.11.5.1
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
Forsk 2010
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
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
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 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
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.
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
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.
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
538
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
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
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
Forsk 2010
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
"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
541
7.2.12.1
7.2.12.2
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
542
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
4. Click OK. The constraint violation costs are stored and will be used in the automatic allocation.
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
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.
7.2.12.5
Forsk 2010
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
546
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.
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.
Forsk 2010
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.
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.
548
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
7.3.1
Forsk 2010
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
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
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
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
Forsk 2010
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.
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
Forsk 2010
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
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
553
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
554
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
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
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
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
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
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
Forsk 2010
Chapter 7: UMTS HSPA Networks 16. Click OK. Atoll creates the traffic map in the Traffic folder.
7.3.2.3.2
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
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
557
7.3.2.4
7.3.2.5
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
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
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
7.3.4.1
Forsk 2010
559
R99 part
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)
UL Power Control
DL Power Control
Congestion and Radio Resource Control HSDPA part For each HSDPA and HSUPA mobile, Mi
Mobile Scheduling
Radio Resource Control HSUPA part Admission Control For each HSUPA mobile, Mi Noise Rise Scheduling
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.
560
Forsk 2010
[ 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
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"
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
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
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
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
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
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
7.3.4.3.2
Forsk 2010
565
7.3.4.3.3
7.3.4.4
566
Forsk 2010
7.3.4.5
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.
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
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
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
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
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.
Iextra AS1, AS2, AS3, AS4 (DL) (dBm): The extra-cell interference for each cell (I) of the active set.
I extra =
DL
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
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 parameters related to the clutter classes, including the default values.
7.3.4.6
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
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
573
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
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 parameters related to the clutter classes, including the default values.
7.3.4.7
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
575
7.3.4.8
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.
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
Forsk 2010
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.
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.
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
Forsk 2010
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
7.3.5.1
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
578
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.
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
7.4.1
Forsk 2010
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
7.4.1.1.1
7.4.1.1.2
7.4.1.1.3
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
580
Forsk 2010
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
7.4.1.4
7.4.1.4.1
Forsk 2010
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.)
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
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
582
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
7.4.2.1
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
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
584
Forsk 2010
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
Forsk 2010
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
7.4.3.1
586
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.
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.
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
7.4.3.2.1
Forsk 2010
587
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
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
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
590
Forsk 2010
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
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
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
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
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
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
Forsk 2010
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.
Forsk 2010
595
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
Forsk 2010
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.
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).
Forsk 2010
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.
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
Forsk 2010
Forsk 2010
599
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
600
Forsk 2010
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
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.
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
Forsk 2010
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.
Forsk 2010
603
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
604
Forsk 2010
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
605
Tip:
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.
606
Forsk 2010
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.
Forsk 2010
607
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
7.4.3.3.3
608
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
Forsk 2010
609
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
4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 7.339).
610
Forsk 2010
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
Forsk 2010
611
7.4.6.1
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
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
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
Forsk 2010
613
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.
614
Forsk 2010
7.4.6.1.3
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
615
7.4.6.1.4
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
Forsk 2010
7.4.6.1.5
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
617
7.4.6.1.6
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.
7.4.6.2
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
Forsk 2010
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
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
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
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
Forsk 2010
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
Figure 7.355: Example of antenna type change (left) and electrical tilt change (right)
Forsk 2010
621
7.4.6.2.4
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.
622
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
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).
7.4.6.2.7
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
Depending on the type of optimisation results you want to view, you might need to expand additional folders.
624
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
7.5.1
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
625
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
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
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
627
7.5.3
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
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
Forsk 2010
629
Formula
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
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.
630
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
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
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
631
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
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
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
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
3. Right-click the drive test data path you want to export. The context menu appears.
Forsk 2010
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
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
634
Forsk 2010
7.6.1
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.
Forsk 2010
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.
7.6.2
7.6.2.1
636
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
7.6.2.2.1
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
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
7.6.2.2.3
7.6.2.2.4
638
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
Forsk 2010
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
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
640
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.
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.
Forsk 2010
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
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
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
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
643
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
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.
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
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 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
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.
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
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).
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
Forsk 2010
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
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
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
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
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
650
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
7.6.5.2
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
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
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
7.7.2
652
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
7.7.3.1
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
653
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
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
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
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
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
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
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
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
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.
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
7.7.6.2
Forsk 2010
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
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:
TX
RX
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
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
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
Forsk 2010
7.7.8
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.
7.7.10
662
Forsk 2010
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.
7.7.10.1
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
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
Forsk 2010
Chapter 8
CDMA2000 Networks
Atoll
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.
CDMA
handoff radio configuration reverse link forward link
8.1
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
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
8.1.1.1
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):
668
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.
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
669
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
Forsk 2010
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
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
672
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
8.1.1.2.1
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
Forsk 2010
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
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
674
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.
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.
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
675
8.1.1.4
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
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
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
677
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.
678
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
8.1.1.4.3
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
679
8.1.1.4.4
8.1.1.5
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.
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
680
Forsk 2010
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
8.1.4
Forsk 2010
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
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
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
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
8.1.6.3
8.1.6.4
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
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
Forsk 2010
8.1.6.5
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
8.1.7.1
2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Remote Antenna from the menu.
4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its 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
685
8.1.7.2
8.1.7.3
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
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
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
8.1.9
Forsk 2010
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
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
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
8.1.9.2
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
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:
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
Forsk 2010
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
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
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
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
Forsk 2010
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.
8.1.10.2
Forsk 2010
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.
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.
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
Forsk 2010
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.
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.
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
Forsk 2010
695
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
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
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
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
8.1.10.6.1
Forsk 2010
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
Forsk 2010
8.1.10.6.2
Forsk 2010
699
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
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
8.1.10.7.1
Forsk 2010
701
8.1.10.7.2
8.1.10.7.3
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.
702
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
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
Forsk 2010
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
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
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
705
8.1.10.7.7
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.
706
Forsk 2010
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
707
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.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
Forsk 2010
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.
8.1.10.8
Forsk 2010
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
710
Forsk 2010
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
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.
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
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
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.
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.
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
714
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
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
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
8.1.10.8.4
716
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.
Forsk 2010
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.
718
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.
Forsk 2010
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.
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
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.
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
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.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 710.
722
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.
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
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.
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
724
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
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.
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
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
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
727
8.1.11.2
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
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
728
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
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
8.1.11.4.2
Forsk 2010
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
8.1.11.5.1
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
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
3. Select Display Options from the context menu. The Visual Management dialogue appears.
Forsk 2010
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 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
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.
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
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.
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
736
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
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
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
Forsk 2010
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
Forsk 2010
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.
4. Click OK. The allocation constraint costs are stored and will be used in the automatic allocation.
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
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
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.
8.1.12.3
742
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
Forsk 2010
743
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.
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.
744
Forsk 2010
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.
Forsk 2010
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
8.2.1
746
Forsk 2010
8.2.2
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
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
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
748
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.
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
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
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
Forsk 2010
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
Forsk 2010
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
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
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
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
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
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
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
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
754
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
8.2.2.5
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
755
8.2.3
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
8.2.4.1
756
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."
Forsk 2010
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."
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
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
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
760
Forsk 2010
8.2.4.3.2
8.2.4.3.3
Forsk 2010
761
8.2.4.4
8.2.4.5
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
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
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
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
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
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
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 parameters related to the clutter classes, including the default values.
8.2.4.7
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
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
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.
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.
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.
3. Right-click the group of simulations you want to duplicate. The context menu appears.
770
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
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
8.2.5.1
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
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
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
772
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
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
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
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
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
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
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
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
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*
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.3.4.2
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
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.
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
778
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
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
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
Forsk 2010
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
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
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
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
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
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
8.4.1
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.
Forsk 2010
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.
8.4.2
8.4.2.1
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
Forsk 2010
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
8.4.2.2.1
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
Forsk 2010
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
8.4.2.2.4
8.4.2.2.5
786
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
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
Forsk 2010
787
Atoll User Manual In GSM, the Inter-technology Neighbours tab is found on the transmitters Properties dialogue.
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.
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.
788
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
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
Forsk 2010
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
Forsk 2010
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
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.
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
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 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
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.
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
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).
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
794
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
795
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
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
Forsk 2010
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
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
Forsk 2010
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
8.5.2
798
Forsk 2010
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
8.5.3.1
8.5.3.2
Forsk 2010
799
8.5.4
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
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
800
Forsk 2010
8.5.5
8.5.5.1
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
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
Forsk 2010
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.
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
802
Forsk 2010
8.5.7.2
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
Forsk 2010
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
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.
8.5.10
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
805
8.5.11
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.
806
Forsk 2010
8.5.11.1
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
807
808
Forsk 2010
Chapter 9
TD-SCDMA Networks
Atoll
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
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
).
Forsk 2010
811
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
).
).
9.2
9.2.1
812
Forsk 2010
9.2.1.1
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
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.
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
Forsk 2010
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
815
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
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
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
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
9.2.1.2.1
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
9.2.1.2.2
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
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
820
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.
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.
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.
Forsk 2010
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
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
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
Forsk 2010
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
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
Forsk 2010
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
9.2.1.4.3
Forsk 2010
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
9.2.1.5
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
Forsk 2010
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
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
827
9.2.3
9.2.4
9.2.5
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
Forsk 2010
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
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
Forsk 2010
829
9.2.6.3
9.2.6.4
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
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
Forsk 2010
831
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
2. Click the arrow next to New Repeater or Remote Antenna button ( 3. Select Remote Antenna from the menu.
4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its 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
9.2.7.3
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
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
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
Forsk 2010
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
9.2.9.1
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
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
9.2.9.2
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
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:
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
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
Forsk 2010
837
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
838
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.
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
839
9.2.10.2
For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.
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
Forsk 2010
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.
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.
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
841
9.2.10.3
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
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
842
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
Forsk 2010
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
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
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).
9.2.10.6.2
Forsk 2010
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).
9.2.10.6.3
846
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
847
9.2.10.6.4
848
Forsk 2010
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).
9.2.10.6.5
Forsk 2010
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
Forsk 2010
9.2.10.7
9.2.10.7.1
9.2.10.7.2
Forsk 2010
851
9.2.10.7.3
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
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
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
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
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
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
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.
9.2.10.7.7
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.
Forsk 2010
855
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
Forsk 2010
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
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.
9.2.10.8
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
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
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
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
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.
860
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
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
9.2.10.8.4
862
Forsk 2010
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
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).
864
Forsk 2010
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).
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
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
Forsk 2010
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
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
Forsk 2010
Forsk 2010
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
Forsk 2010
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
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
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
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).
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.
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.
874
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
875
9.2.10.8.7
876
Forsk 2010
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).
9.2.10.9
Forsk 2010
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
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
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
For more information on automatic frequency allocation, see "Allocating Frequencies Automatically" on page 880.
9.2.11.2
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
880
9.2.11.3.1
9.2.11.3.2
9.2.11.4
9.2.11.5
Forsk 2010
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
882
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
5. Click OK.
9.2.12.3
Forsk 2010
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
Forsk 2010
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.
9.2.12.4
9.2.12.4.1
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
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.
886
Forsk 2010
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
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
Forsk 2010
887
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.
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
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.
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
889
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
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
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
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
891
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
"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
892
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
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
9.2.13.4
Forsk 2010
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
4. Click OK. The constraint violation costs are stored and will be used in the automatic allocation.
894
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
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.
896
Forsk 2010
9.2.13.6
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
Forsk 2010
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.
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.
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
Forsk 2010
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.
Forsk 2010
899
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
900
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
Timeslot Configuration
UDDDDD UUDDDD UUUDDD UUUUDD UUUUUD UpUDDDD UpUUDDD
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
Forsk 2010
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).
9.3.1.2
902
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.
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
903
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
Forsk 2010
Figure 9.487: Resource unit usage coverage prediction A high percentage of cell usage can indicates dimensioning problems.
9.3.2
9.3.3
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
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
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
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
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
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
Forsk 2010
9.3.3.2.1
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
909
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
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
910
Forsk 2010
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
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
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
Forsk 2010
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
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
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
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
9.3.3.5
7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1.
Forsk 2010
913
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
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
9.3.5.1
914
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.
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
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.
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:
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
Forsk 2010
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
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
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
918
Forsk 2010
9.3.5.3.2
9.3.5.3.3
Forsk 2010
919
9.3.5.4
9.3.5.5
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
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
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
Forsk 2010
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
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
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
Forsk 2010
925
Atoll User Manual The parameters related to the clutter classes, including the default values.
9.3.5.7
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
926
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.
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.
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
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.
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
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
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
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.
An HSDPA coverage prediction to analyse HS-PDSCH quality and HSDPA data rate: -
9.4
9.4.1
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
929
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
Forsk 2010
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
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
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
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
932
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*
Forsk 2010
933
Formula
*X X*
7. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. For more information on 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
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
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
Forsk 2010
9.4.4.4
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
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
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
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
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
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
9.5.1
Forsk 2010
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.
938
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.
9.5.2
9.5.2.1
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
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
9.5.2.2.1
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
Forsk 2010
9.5.2.2.2
9.5.2.2.3
9.5.2.2.4
Forsk 2010
941
9.5.2.2.5
9.5.3
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
942
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.
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.
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.
Forsk 2010
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
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
944
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
945
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
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.
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
Forsk 2010
9.5.3.5
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
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.
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
Forsk 2010
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
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
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
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
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
951
9.5.4
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
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
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
9.6.2
9.6.3
9.6.3.1
Forsk 2010
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.
954
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
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
9.6.4
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
9.6.4.1.1
Forsk 2010
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.
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.
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.
956
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.
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
9.6.4.1.2
9.6.4.1.3
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
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
9.6.4.1.6
9.6.4.2
ii. Click the Combined button to display the combined patterns of all the beams in the Grid of Beams Properties dialogue.
958
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
959
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
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
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.
9.6.5.2
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
Forsk 2010
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.
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
9.6.7.2
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
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.
9.6.7.3
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
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.
9.6.9
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
Forsk 2010
Chapter 10
WiMAX BWA Networks
Atoll
10
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
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.
Forsk 2010
967
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
10.2
968
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
10.2.1.1
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
969
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
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
971
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
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
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
Forsk 2010
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
10.2.1.2.1
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
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
975
10.2.1.2.3
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
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.
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
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.
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
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
Forsk 2010
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
Forsk 2010
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
979
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
10.2.1.4.3
980
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
10.2.1.5
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
981
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
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
Forsk 2010
10.2.3
10.2.4
10.2.5
10.2.6
Forsk 2010
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
10.2.7.1
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
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
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.
Fresnel ellipsoid
Line of sight
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
Forsk 2010
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:
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
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
Forsk 2010
987
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
988
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.
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
989
10.2.8.2
For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.
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
Forsk 2010
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.
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.
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
991
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
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
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
Forsk 2010
10.2.8.5
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
Forsk 2010
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
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
Forsk 2010
10.2.8.6.2
Forsk 2010
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).
10.2.8.6.3
996
Forsk 2010
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).
10.2.8.7
Forsk 2010
997
10.2.8.7.1
10.2.8.7.2
10.2.8.7.3
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
998
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
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
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
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
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
Forsk 2010
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.
10.2.8.7.7
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
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.
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
1003
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
Forsk 2010
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
1005
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.
10.2.8.8
1006
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
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
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.
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
Forsk 2010
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
Forsk 2010
1009
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).
1010
Forsk 2010
10.2.8.8.3
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.
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
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.
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
Forsk 2010
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).
Forsk 2010
1013
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
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).
Forsk 2010
1015
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
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
1017
1018
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.
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.
Forsk 2010
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).
10.2.8.8.4
1020
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
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
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
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
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
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
5. Click OK.
10.2.9.4
Forsk 2010
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
Forsk 2010
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
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
10.2.9.5
10.2.9.5.1
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
Forsk 2010
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
1027
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
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
Forsk 2010
10.2.9.6
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.
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
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.
1030
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
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
1031
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
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.
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
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
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.
1034
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
10.2.10.2
Forsk 2010
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.
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
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.
10.2.11
"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
Forsk 2010
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.
1038
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
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
Forsk 2010
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.
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
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.
10.3
10.3.1
Forsk 2010
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
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
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
Forsk 2010
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
Forsk 2010
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.
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
Forsk 2010
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
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
1045
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
1046
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
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
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
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
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
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
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
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
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
1049
10.3.2.4
10.3.2.5
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
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
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
10.3.4.1
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
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
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
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
Forsk 2010
1053
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
10.3.4.2
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
1054
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
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
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
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
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
1057
10.3.5.3.1
10.3.5.3.2
10.3.5.3.3
1058
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).
10.3.5.3.4
5. Click OK. The traffic distribution is now displayed by throughput (see Figure 10.558).
Forsk 2010
1059
10.3.5.3.5
10.3.5.3.6
1060
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
Figure 10.561: Displaying the traffic simulation results using tool tips
10.3.5.4
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
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.
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
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
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
Forsk 2010
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 parameters related to the clutter classes, including the default values.
10.3.5.5
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.
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
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
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 parameters related to the clutter classes, including the default values.
10.3.5.6
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
10.3.6
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
10.4.1
1068
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
10.4.1.1.1
10.4.1.1.2
10.4.1.1.3
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
Forsk 2010
1069
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
10.4.1.4
10.4.1.4.1
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
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.)
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
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
Forsk 2010
1071
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
10.4.2.1
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
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
Forsk 2010
1073
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
1074
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
10.4.3.1
Forsk 2010
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.
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.
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
10.4.3.2.1
1076
Forsk 2010
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
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
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
Forsk 2010
1079
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
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).
Forsk 2010
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
1082
Forsk 2010
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
Forsk 2010
1083
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
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.
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
1085
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.
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
Forsk 2010
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.
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
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).
1088
Forsk 2010
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
Forsk 2010
1089
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
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:
Forsk 2010
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.
1092
Forsk 2010
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
Forsk 2010
1093
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
Forsk 2010
Tip:
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.
Forsk 2010
1095
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.
1096
Forsk 2010
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
10.4.3.2.8
Forsk 2010
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
1098
Forsk 2010
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
4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 10.589).
Forsk 2010
1099
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
1100
Forsk 2010
10.4.6.1
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
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
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
1102
Forsk 2010
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.
Forsk 2010
1103
10.4.6.1.3
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
Forsk 2010
10.4.6.1.4
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
1105
10.4.6.1.5
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
Forsk 2010
10.4.6.1.6
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.
10.4.6.2
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
1107
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
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
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
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
1109
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
Figure 10.605: Example of antenna type change (left) and electrical tilt change (right)
1110
Forsk 2010
10.4.6.2.4
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.
Forsk 2010
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
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
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).
10.4.6.2.7
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
Depending on the type of optimisation results you want to view, you might need to expand additional folders.
Forsk 2010
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
10.5.1
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
Forsk 2010
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.
Forsk 2010
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
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
Forsk 2010
10.5.3
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
Forsk 2010
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
1118
Forsk 2010
Formula
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
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.
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
3. Right-click the drive test data from which you want to display comparative statistics. The context menu appears.
Forsk 2010
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
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
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).
1120
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
1121
10.5.5
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
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
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
Forsk 2010
10.6
10.6.1
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
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.
10.6.2
1124
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
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
10.6.2.2.1
Forsk 2010
1125
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
10.6.2.2.3
1126
Forsk 2010
10.6.2.2.4
10.6.2.2.5
Forsk 2010
1127
10.6.3
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
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
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.
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.
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
1129
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
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
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
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
Forsk 2010
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.
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 or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter
1132
Forsk 2010
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.
Forsk 2010
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).
1134
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
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
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
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
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
Figure 10.616: New sector Before and after applying the configuration
10.6.5
Forsk 2010
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
10.6.5.2
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
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
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
Forsk 2010
1139
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
10.7.2.1
1140
Forsk 2010
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
1141
Note:
Figure 10.617 depicts a WiMAX frame with the described parameters marked.
10.7.2.2
1142
Forsk 2010
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
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
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
Forsk 2010
10.7.4
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
Forsk 2010
1145
10.7.6
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).
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
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).
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:
TX
RX
Forsk 2010
1147
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
1148
Forsk 2010
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
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
Forsk 2010
Chapter 10: WiMAX BWA Networks 5. Click the Close button ( ) to close the Schedulers table.
10.7.8
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
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
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
Forsk 2010
10.7.9
Forsk 2010
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.
10.7.10
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
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
5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.
10.7.12
Forsk 2010
1155
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.
10.7.12.1
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
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
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
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.
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.
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.
1158
Forsk 2010
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.
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
1159
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.
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.
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
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
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
Forsk 2010
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
1163
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.
1164
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.
Type
1 2 3 4
Name
6x1 (Default) 3x2 2x3 1x6
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
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.
10.9
1166
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
Noise Rise
1 2 10 100
The reason why uplink interference is expressed in terms of noise rise (in dB) in Atoll instead of load factor (in %) 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:
Subchannel Group
0 1 2
Subchannel Range
0 N/A 1
Subchannel Group
0 1 2
Subchannel Range
0-5 6-9 10-15 16-19 20-25 26-29
1024 3 4 5
Forsk 2010
1167
Subchannel Group
0 1 2
Subchannel Range
0-4 N/A 5-9
Subchannel Group
0 1 2
Subchannel Range
0-11 12-19 20-31 32-39 40-51 52-59
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
Forsk 2010
Chapter 11
LTE Networks
Atoll
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
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.
Forsk 2010
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
11.2
1172
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
11.2.1.1
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
1173
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.
1174
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
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
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
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
11.2.1.2.1
c. Right-click the site you want to modify. The context menu appears.
1178
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
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
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
1179
11.2.1.3
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.
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.
1180
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
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
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
1181
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
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
1183
11.2.1.4.2
11.2.1.4.3
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
11.2.1.5
1184
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.
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
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
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
11.2.4
11.2.5
1186
Forsk 2010
11.2.6
11.2.7
11.2.7.1
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
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following:
Forsk 2010
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.
Fresnel ellipsoid
Line of sight
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
Forsk 2010
11.2.7.2
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:
Display Resolution
5m 20 m 50 m 100 m According to the size of the country
Forsk 2010
1189
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
1190
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
Forsk 2010
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.
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
Forsk 2010
11.2.8.2
For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.
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
1193
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.
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.
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
Forsk 2010
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
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
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
1195
11.2.8.5
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
1196
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
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
11.2.8.6.2
Figure 11.657: Condition settings for a coverage prediction by transmitter 7. Click the Display tab.
1198
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).
11.2.8.6.3
Forsk 2010
1199
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).
11.2.8.7
1200
Forsk 2010
Chapter 11: LTE Networks "Comparing Coverage Predictions: Examples" on page 1205.
11.2.8.7.1
11.2.8.7.2
11.2.8.7.3
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
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
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
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
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
1204
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.
11.2.8.7.7
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
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.
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
Forsk 2010
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
1207
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
Forsk 2010
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.
11.2.8.8
Forsk 2010
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
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
Forsk 2010
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
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
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
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).
11.2.8.8.3
Forsk 2010
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.
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.
1214
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
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).
1216
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
1217
1218
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
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.
1220
Forsk 2010
Forsk 2010
1221
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
Forsk 2010
11.2.8.8.4
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
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
Forsk 2010
11.2.8.9
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
Forsk 2010
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
5. Click OK.
11.2.9.4
1226
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
11.2.9.5
1228
Forsk 2010
Chapter 11: LTE Networks "Displaying the Coverage of Each Neighbour of a Cell" on page 1230.
11.2.9.5.1
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
1229
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
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
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 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
1231
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.
1232
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
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
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
1234
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
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.
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
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.
To take the calculated interference matrices into account: Select the Take into account check box.
11.2.10.1.2
11.2.10.2
Forsk 2010
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.
1238
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.
11.2.11
"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
Forsk 2010
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.
1240
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
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
Forsk 2010
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.
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
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.
11.3
11.3.1
Forsk 2010
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
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
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
Forsk 2010
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
Forsk 2010
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.
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
Forsk 2010
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
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
1247
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
1248
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
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
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
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
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
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
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
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
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
1251
11.3.2.4
11.3.2.5
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
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
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
11.3.4.1
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
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
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
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
Forsk 2010
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
11.3.4.2
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
1256
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
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
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
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
Forsk 2010
1259
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
11.3.5.3.2
1260
Forsk 2010
11.3.5.3.3
11.3.5.3.4
5. Click OK. The traffic distribution is now displayed by throughput (see Figure 11.696).
Forsk 2010
1261
11.3.5.3.5
11.3.5.3.6
1262
Forsk 2010
Figure 11.698: Displaying the traffic simulation results using tool tips
11.3.5.4
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.
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
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
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
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 parameters related to the clutter classes, including the default values.
11.3.5.5
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
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.
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
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 parameters related to the clutter classes, including the default values.
11.3.5.6
1268
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
11.3.6
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
1269
11.4
11.4.1
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
11.4.1.1.1
11.4.1.1.2
1270
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
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
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
11.4.1.4
Forsk 2010
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
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.)
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
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
1272
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
11.4.2.1
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
1273
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
Forsk 2010
11.4.2.2
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
Forsk 2010
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
11.4.3.1
1276
Forsk 2010
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.
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
11.4.3.2.1
Forsk 2010
1277
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
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
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
1280
Forsk 2010
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).
1282
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
Forsk 2010
1283
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
1284
Forsk 2010
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
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.
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
Forsk 2010
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.
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
1287
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.
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
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).
Forsk 2010
1289
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
1290
Forsk 2010
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
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:
1292
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.
Forsk 2010
1293
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
1294
Forsk 2010
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
1295
Tip:
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.
1296
Forsk 2010
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.
Forsk 2010
1297
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
11.4.3.2.8
1298
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
Forsk 2010
1299
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
4. Right-click the setup folder of the optimisation you want to work with. The context menu appears (see Figure 11.726).
1300
Forsk 2010
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
Forsk 2010
1301
11.4.6.1
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
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
Forsk 2010
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
Forsk 2010
1303
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.
1304
Forsk 2010
11.4.6.1.3
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
1305
11.4.6.1.4
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
Forsk 2010
11.4.6.1.5
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
1307
11.4.6.1.6
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.
11.4.6.2
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
Forsk 2010
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
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
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
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
Forsk 2010
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
Figure 11.742: Example of electrical tilt change (left) and electrical tilt change (right)
Forsk 2010
1311
11.4.6.2.4
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.
1312
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
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
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).
11.4.6.2.7
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
1314
Forsk 2010
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
11.5.1
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
1315
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
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
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
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
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
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
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*
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
1319
11.5.4.2
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
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
3. Right-click the drive test data from which you want to extract a field. The context menu appears.
1320
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
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
1321
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
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
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
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
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
Forsk 2010
1323
11.6.1
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.
1324
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.
11.6.2
11.6.2.1
Forsk 2010
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
11.6.2.2.1
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
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
11.6.2.2.3
11.6.2.2.4
Forsk 2010
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
11.6.3
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
1328
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.
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.
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.
Forsk 2010
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
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
1330
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
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
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
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.
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
Forsk 2010
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.
1334
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).
Forsk 2010
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
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
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
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
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
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
Figure 11.753: New sector Before and after applying the configuration
11.6.5
11.6.5.1
Forsk 2010
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
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
Forsk 2010
11.6.6
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
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
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
11.7.2.1
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
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.
11.7.2.2
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
1343
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
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
1344
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.
11.7.5
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).
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
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).
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:
TX
RX
1346
Forsk 2010
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
Forsk 2010
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
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
Forsk 2010
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.
11.7.8
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
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
5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.
11.7.10
Forsk 2010
1351
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.
11.7.11
1352
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
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.
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
1354
Forsk 2010
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:
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
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.
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
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.
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.
1356
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.
11.9
Forsk 2010
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
Noise Rise
1 2 10 100
The reason why uplink interference is expressed in terms of noise rise (in dB) in Atoll instead of load factor (in %) 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
Forsk 2010
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
1359
1360
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
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
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
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
1361
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
pasting antenna pattern 143 pattern electrical tilt 143 smart, creating (WiMAX) 1152 smoothing vertical pattern 146
1362
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
1363
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
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 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 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 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
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
1365
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
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
1367
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
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
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
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
1369
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
1371
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
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
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
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
1373
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
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
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 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
1375
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
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
1377
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
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 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
1379
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
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
1381
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
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
1383
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
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 (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
1385
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
1386
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
1387
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
Forsk 2010
Forsk 2010
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